Related
Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?
humphrey74 said:
Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?
Click to expand...
Click to collapse
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.
keke7442 said:
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.
Click to expand...
Click to collapse
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...
humphrey74 said:
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...
Click to expand...
Click to collapse
Does it boot? and which kernel/recovery do you have installed? which software were you running before you tried to flash to litening?
I had this problem going from villian to litening. I had to install official genertic samsung firmware to sort it out. After I did that I have had no problems with flashing roms.
Sent from my GT-I9100 using XDA Premium App
Yes, it boots. But always into one same state.
I flashed it with XWKDD_insecure.tar (without repart and without PIT file) and then rooted it with "SuperOneKlick".
My Phoneinfo says:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
After it, cause I was very happy to have a rooted device, I installed AndroidWall, AdFree, AutoKillerMemory, NoLED and AutorunManager
that´s all I did. additionaly I tried to set up the UAString for the stock browser with commands like about:debug, about:config and about:useragent.
That´s all I can remember.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from .... .
humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse
I had the same issue, but solved after flashing the GT-I9100_KE7_insecure.tar.md5 kernel.
I believe there's a link to the kernel in this thread
JJEgan said:
humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
Result:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> zImage
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Phone Details after this:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
Click to expand...
Click to collapse
You need to flash a full firmware not a kernel .
jje
humphrey74 said:
JJEgan said:
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Click to expand...
Click to collapse
Download the full KF3 ROM and flash that using ODIN. Then re-do your root. I recommend using CF-Root instead of Superoneclick. It takes the guesswork out.
Click to expand...
Click to collapse
OK, I downloaded the full KF3 ROM and flashed it with Odin.
Finished with PASS.
No change anfter reboot.
As I said in my first post, I can flash what I want .... device boots up into the same state, as I did flash nothing!
I flashed FULL firmwares, rooted kernels ... etc..
Nothing happens
Download XXKG2 from here
http://forum.xda-developers.com/showthread.php?t=1174161
and flash the 3 file version (wipe version)
OK i did flash the 3-parted KG2 exactly like the instructions say.
Odin says:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKG2_CL375027_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG2_REV_02_CL1037208.tar.md5 is valid.
<OSM> GT-I9100-CSC-HOME-MULTI-OXAKG2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> Sbl.bin
<ID:0/011> param.lfs
<ID:0/011> zImage
<ID:0/011> factoryfs.img
<ID:0/011> data.img
<ID:0/011> hidden.img
<ID:0/011> cache.img
<ID:0/011> modem.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response form LOKE
<ID:0/011> cache.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/003> Added!!
As I said .... after reboot thy phone is in same state!!
And now you professionals it´s your turn...
Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?
omrij said:
Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?
Click to expand...
Click to collapse
It boots straight to OS after flash. EVERYTIME
hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help
drreality said:
hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help
Click to expand...
Click to collapse
hey
- I changed the USB port
- I restarted the computer very often
- I tried with other computer
- I tried update with KIES
No other result than it boots into same state
Factory reset after flash?
Yes, I did this too. And not only once ...
No change happens
Hi, i have a big problem. Everytime when i flash something in odin i have FAIL.
Today i want to flash stock MGA. After a few seconds... fail.
Here log from odin 3.07:
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
I can't go into recovery.
I can go into download mode.
I think i tried everything..
PLEASE HELP BECAUSE I NEED MY PHONE ON TOMMOROW.
sorry for my bad english
Any help ??
kapiszon53 said:
Any help ??
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer.
After change computer everything works fine. THX
i've used a different PC, reinstalled the USB drivers and repeated the process many times but still it doesn't work
i've a GT-I9500
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
SageNightmare said:
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
Click to expand...
Click to collapse
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
sway8966 said:
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
Click to expand...
Click to collapse
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
SageNightmare said:
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
Click to expand...
Click to collapse
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
sway8966 said:
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
Click to expand...
Click to collapse
Yup I tried all of that except a different odin version,but long story short,I managed to go into town and a friend of mine used a different version of odin and got me nice and sorted out,thanks for help btw
Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<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> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?
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.