Database Users

Help my gt-i9505 stocked on samsung logo..

i will tell all the information here..i have my samsung gt-i9505 carrier locked to globe telecom here in the philippines..
i tried to factory unlock here http://forum.xda-developers.com/showthread.php?t=2282683 but i have no luck on it..i have change my baseband several time via odin but still i pin request always shows after i reboot..i have android version 4.2.2, stock firmware DXUBMF8.
so i stopped from there..i moved on to try to root my s4,before having this phone i had owned a s4 factory unlock and i have had rooted it but i already forgot how to do it again..so started anew by looking again at forum threads,i have tried omega custom rom but if i goes to recovery mode my screen only shows the following options: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update cache..my question here was,is this the default recovery mode of s4 now?because i can still recall that my last s4's default recovery menu shows with advance option with wipe dalvik cache etc..and my recovery menu now shows no apply update from internal storage..when i tried flashing the custom rom save on my sd card: apply update>omega*something*.zip..it all well done but after rebooting my phone didn't any stuff from that custom rom nor rooted at all..can you help me solving this?
and lastly this is my main problem now,i searched again the thread and went down to this thread http://forum.xda-developers.com/showthread.php?t=2250824 i downloaded the pre-rooted rom XXUBMF8..flashed it with odin PDA..passed and from then my phone was stocked every time i reboot to samsung logo..
i have tried to flash again on a stocked rom. odin>PHONE>(the stock rom)>start>passed then reboot it still stocked to samsung logo..
sorry this was too long to read but i have to tell what all i have been done resulting to this..can someone help me..i will be very thanful for your help..

can anyone help me with this?i have been searching the forum for hours..i have done flashing through odin with stock rom and pit file but it ended up failed..done factory reset with default recovery mode but nothing happens still stucked on boot logo..

still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.

voidjov said:
still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.
Click to expand...
Click to collapse
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info

did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom

TingTingin said:
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info
Click to expand...
Click to collapse
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
daibaron said:
did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom
Click to expand...
Click to collapse
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..

voidjov said:
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..
Click to expand...
Click to collapse
In the Thread you point out... read AGAIN about PIT
http://forum.xda-developers.com/showthread.php?t=2265477
Download the PIT and follow the exact procedure... it's not like flashing a new firmware so read which boxes you check
Try the PIT file with / without the firmware
check also this thread... in case you have a pit related error.
http://forum.xda-developers.com/showthread.php?t=2283919
I'm sure you have all you need to recover your phone.
When you will have recovered your phone, update this thread saying you solved your problem.
check also this thread... in case you have a pit related error.
OH, don't forget to update my thanks counter

Hello,
I saw an answer to this problem in another thread. You have to swipe the phone by starting it with VOLUME UP + HOME + POWER, and then whatever options you have to swipe everything.

Problem SOLVED!!!
hey guys i have solved my greatest problem since i started rooting back on my N7100,my 1st s4 and now my new s4..
thank you for all who helped me,after more than 24hours of reading and waiting for you replies and doing some intervention on my s4,i have recover it..i will post here how i did it for reference for others who might encounter this problem same as mine:
first of all i have noticed this just after successfully revived my phone, you have to WIPE THE DATA/FACTORY REFORMAT via recovery mode before and after doing any firmware update,then i just removed my battery may be a minute and put it back again every time i do flashing..
i used odin version 1.85 not version 3.04..i first chose the pit file and flash it.(when i tried flashing the pit and stock rom together it always ended up to fail)..so i decided to chose to flash the pit file only using odin v1.85(it automatically ticked the "repartition option on this odin version" then it passed..after that as i have said remove battery,wipe data,then i removed again the battery,then put it back and do download/odin mode on my phone,then i flashed stock rom from www.sammoble.com, i searched for globe carrier since my phone was locked on that carrier, then after 2-3minutes(be patient and don't do anything while waiting) my phone backed to life!!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OLBBMF8_I9505DXUBMF8_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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
for those guys who helped me, i have pressed the thanks button for you guys 100x(i hope i can do that)..but truly i am very much thankful for you guys..i do not have to go to service provider technician or any cellphone repair stall just to repair my phone and pay,i have revived it with your help..THANK YOU!!!
i must add i would like to ask what is the best way to root my phone, i have read chainfire autoroot, is the best way to root my phone?as i can remember it is the same way i have rooted my first s4 two months ago because i saw my old folder here on my pc with that application..and best custom rom?
and the best way to factory unlock my phone, the working firmware..
you can post the link so i can read and do it myself..

Galaxy S4 flash help

Hello,
I was wondering if anyone could possibly help me with my phone. The story is that yesterday it randomly shut off and then wouldn't turn back on. Then I eventually got it to turn on but it popped up with the message in the first image.
Then I downloaded my stock rom and downloaded it onto my phone using odin with no problems. But then it would just load with the boot image and nothing more. It wouldn't go into recovery mode either so I decided to redo it. However, when I did it, odin froze and left the progress like in the second image for hours. I decided to unplug and do it again, but it keeps on freezing at the same point. Now whenever I reboot it says the same thing as the first image....
Does anyone have any suggestions on what I could do?
EDIT: Now I actually installed stock rom, but it will not boot. It stays on the logo and when I try to go into recovery mode, it says it is going into recovery mode at the top left, but it just infinitely reboots after that. Any suggestions?

Flash the ROM in the Bootloader slot in Odin.

You could try different combinations of USB cables, USB ports and Odin version.

Pwnycorn said:
You could try different combinations of USB cables, USB ports and Odin version.
Click to expand...
Click to collapse
I've tried that already but to no avail... I am trying to flash the rom in the bootloader icon right now like Strephon Alkhalikoi mentioned

Strephon Alkhalikoi said:
Flash the ROM in the Bootloader slot in Odin.
Click to expand...
Click to collapse
it's still doing the same thing.... How long should it take?

Strephon Alkhalikoi said:
Flash the ROM in the Bootloader slot in Odin.
Click to expand...
Click to collapse
This is what it said when I did it on bootloader
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Pwnycorn said:
You could try different combinations of USB cables, USB ports and Odin version.
Click to expand...
Click to collapse
I got it to finally work, but now it won't boot correctly. I try to go into recovery mode and it just keeps infinitely rebooting after that.

Confirm that the phone model # in download mode is the agh-i337m.
If this is correct, try Odin 3.19, uncheck everything excep f reset time, flash the phone. When successfully flashed, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery, and factory reset.

audit13 said:
Confirm that the phone model # in download mode is the agh-i337m.
If this is correct, try Odin 3.19, uncheck everything excep f reset time, flash the phone. When successfully flashed, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery, and factory reset.
Click to expand...
Click to collapse
Yeah its SGH-I337M and there is no odin 3.19. Which version did you actually mean?

Sorry, I meant Odin 3.1.

audit13 said:
Sorry, I meant Odin 3.1.
Click to expand...
Click to collapse
Thanks. It worked....but only temporarily. I got into recovery halfway, but then it rebooted again. I got into it again somehow and tried to press factory reset, but it restarted again... What should I do?
EDIT: I got it to factory reset, but it just keeps on doing the same thing.... It keeps on restarting over and over

Strange, the memory chip could be defective.
You could try flashing twrp and use twrp to do a factory reset.

audit13 said:
Strange, the memory chip could be defective.
You could try flashing twrp and use twrp to do a factory reset.
Click to expand...
Click to collapse
Sorry how do I do that? What is twrp?

robs247 said:
Sorry how do I do that? What is twrp?
Click to expand...
Click to collapse
It's a custom recovery. TWRP stands for Team Win Recovery Project.
I don't think there's a version specifically for your device, so then make sure that whatever you get is for the Qualcomm S4.

Twrp for the i9505 can be flashed to the i337m and can be found here: https://dl.twrp.me/jfltexx/
Download the tar version, flash it in the pda slot of Odin 3.1. Do the same thing where you uncheck auto reboot, flash remove cable etc. and boot into twrp, choose wipe, advanced wipe, wipe cache and data.

audit13 said:
Twrp for the i9505 can be flashed to the i337m and can be found here: https://dl.twrp.me/jfltexx/
Download the tar version, flash it in the pda slot of Odin 3.1. Do the same thing where you uncheck auto reboot, flash remove cable etc. and boot into twrp, choose wipe, advanced wipe, wipe cache and data.
Click to expand...
Click to collapse
I did it, but when I try to boot into recovery, it says "Recovery is not SEANDROID ENFORCING." Then it just reboots after like 20 seconds... What should I do?
EDIT: I got in and I did what you told me to do, but it still randomly reboots and keeps going in a boot loop for a while, then works correctly, then stops working...

I wonder if it is a batter problem. Try using the phone while it is connected to a power source.

audit13 said:
I wonder if it is a batter problem. Try using the phone while it is connected to a power source.
Click to expand...
Click to collapse
It does the same thing

Same problem
same problem please help me how to fix it (
imgur.com/a/UwhUe

SM-G930A Cannot boot. Attempting to flash offical firmware using odin fails

I get this error while attempting to flash official ROM using Odin. the phone currently cannot boot. Please assist in any way possible. I just would like to get my phone to function like normal again. I attempted to flash only AP
ON PC LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ON PHONE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Any way I can get the phone usable again? I really would like if anyone could assist in get it working again. It does not need to be rooted, it only needs to boot and function

Mine did same thing. I fixed mine by doing a factory reset from recovery mode. Reboot the phone and hold power+volume up+home key at same time until u see recovery mode in top left corner. It will say installing system update then go to a menu. Hit volume down till factory reset is highlighted. Hit the power button. After its complete go to wipe cache and wipe it also. Then click reboot system now and should now boot fine

Js7bla said:
Mine did same thing. I fixed mine by doing a factory reset from recovery mode. Reboot the phone and hold power+volume up+home key at same time until u see recovery mode in top left corner. It will say installing system update then go to a menu. Hit volume down till factory reset is highlighted. Hit the power button. After its complete go to wipe cache and wipe it also. Then click reboot system now and should now boot fine
Click to expand...
Click to collapse
I've had to do the same thing in a similar situation and it fixed it for me. Good fix!

Are you sure the stock version you are trying to flash is the same or newer than the version you had installed?

jpasher said:
Are you sure the stock version you are trying to flash is the same or newer than the version you had installed?
Click to expand...
Click to collapse
I think you have to Flash all 4 of the files, AP,BL, CP, CSC in Odin Latest version of stock is APK1

I flashed just this AP_G930AUCS4API2_CL8575098_QB10880146_REV02_user_low_ship_MULTI_CERT.tar in the AP section and my phone worked again. I don't know if that' might be bad thing or not though

I choose Phone Bootloader Update in Odin. It was the only thing that worked for me.

Soft Bricked S4

*****************Thread can be closed as issue has been resolved*****************
I think I have soft bricked my phone.
I tried this tutorial and everything went according to the instructions except that the wifi couldn't be turned on.
So I opened a thread asking for help regarding my wifi, I was advised to flash a custom ROM (Android 5.0.1 Lollipop SDK 21) thru TWRP but I must have done something wrong because the phone was stuck in Android System Recovery.
Then I was advised to flash the original firmware thru Odin (Android 4.2.2) and that's where I think the brick happened.
The phone can go into download mode but there is a gray line that says "Write protection: Enable" and everything I try to flash thru Odin gives the same fail error:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Urgent help is much appreciated as I have no other phone and I have been incommunicated for a week+ now
UPDATE:
I just tried to go into Android System Recovery just now it worked! I swear I wasn't able to. It says on top:
LRX22C.I337UCSGOK3 (I was on NB1, where could have this come from?)
And has a couple extra options I had never seen before (last 3 or 4 from the list:
reboot system now (tried it and gets stuck on Samsung logo)
apply update from ADB
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Enable cp logging
Disable cp logging
At the end of the recovery screen there are 2 lines in red:
failed to mount "/system" (Invalid Argument)
E: failed to mount /system (Invalid Argument)

What is the model # in download mode?

audit13 said:
What is the model # in download mode?
Click to expand...
Click to collapse
It says:
Product Name: SGH-I337
PS: Sorry I didn't specify because I thought this forum section was only that model.

The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​

audit13 said:
The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​
Click to expand...
Click to collapse
Mine is not the "M" version.
What am I supposed to get from those notes? Are you suggesting I follow the steps in that thread?
I'm not too technical, but I can follow steps.

If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)

What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
I am on NB1, will try this tru Odin and will report back.

StoneyJSG said:
What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.
Click to expand...
Click to collapse
Is the bootloader that one at the top of the Android System Recovery? If so, mine says:
LRX22C.I337UCSGOK3

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
It seems that I already had tried this because when I extracted the file it had to be replaced on my Desktop. Anyways I tried it again and it said the same thing:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

UPDATE:
Somehow I can go into recovery now and it says LRX22C.I337UCSGOK3 and unable to mount /system. Please refer to first post for complete info about this.

Publish the Odin log of possible.
You tried using different usb cables and usb ports?

audit13 said:
Publish the Odin log of possible.
You tried using different usb cables and usb ports?
Click to expand...
Click to collapse
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.

Holy_Purple said:
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.
Click to expand...
Click to collapse
OMG! I tried a new cable and it went thru!!! I cannot believe my eyes! and the wifi is working!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> non-hlos.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.

StoneyJSG said:
You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.
Click to expand...
Click to collapse
Thanks for the info! I won't be messing with my phone any more, haha :victory:

Glad you got it fixed
I always have a few Samsung cables on hand for flashing.

SM-T580, hopeless?

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.