Related
I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!
help
ofwise said:
I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!
Click to expand...
Click to collapse
I might not be able to help but you can, can you let us know what ROM/recovery/what you were doing before you turned off your tab and anything else you can think of that may be relevant
Thanks
It's download mode with a different interface Reflash your Tab, use Odin.
I've installed cyanogen 10.1 RC without problems. The tablet worked fine. Then I plugged the tablet to charge. When I took again the tablet (after 10 hours more or less) it was off.
In this mode (triangle, computer, phone), I'm trying flashing a stock rom. Without pit file, odin fails saying "write error", and with pit file and repartion checkbox marked sais "there's no pit partition".
Only way to turn off the tablet is quitting the battery. When I put again the battery, the tablet still is off; but when I try to turn on/get into download mode/get into recovery... only shows the triangle, phone and computer screen...
I think that my galaxy tab is bricked... :crying:
Sorry about my bad english and thanks for your answers.
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try heimdall. Never tried by myself flashing system partition using it but work for recovery, boot, and param partition.
ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to go into download mode and flash a custom recovery using odin. I recommend CWM. Then try to go into recovery mode and wipe data, cache, dalvik cache and factory reset (NOTE: It will delete EVERYTHING and your tab will be like out of the box). Now try to boot into android, if android doesn't boots up then use odin to flash a custom rom or find a stock rom for your device and then your tablet should be fine.
Good luck :thumbup: and happy flashing .
And if you found this helpful then don't forget to hit the thanks button.
Sent from my GT-P3100 using xda app-developers app
Nothing...
I've tried Heimdall and doesn't detect my device. I've tried to install another one CWM and the same problem...
I've reinstalled the samsung drivers into 2 computers, differents usb ports... no recovery, no download mode and the charging icon (battery icon) doesn't appear (but charges).
I think my tab is dead... I don't know how more I can do it.
Thanks for the ideas
OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.
The computers I've tried to flash with odin are with windows 8. But I flash my phone without problems...
Maybe with another windows version. I'll give a try this afternoon at home.
Thanks!!
daniel644 said:
OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.
Click to expand...
Click to collapse
I've only used Windows 8 for flashing so far and works perfectly fine in my experience
Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...
ofwise said:
Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...
Click to expand...
Click to collapse
YOU shouldn't EVER use a PIT file in Odin, especially if your not even sure it's the right one, using an incorrect PIT file can totally screw up your device.
The ONLY time you could ever need a PIT file is if you flashed a ROM that changed the format of the partition tables (like rfs to mtd or bml) which to my knowledge non of the ROM for these tablets do that.
Hrmmm... Have you tried to see if Samsung Kies can do anything about it?
I mean, really. Your system partition is corrupt so i doubt it can detect anything.
As a last resort could you open up the tab and pull out the battery? Or even let the battery completely run out?
I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).
ofwise said:
I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).
Click to expand...
Click to collapse
Check this out ofwise- h**ps://www.youtube.com/watch?v=pJnoiMTw5cY&feature=youtube_gdata_player
Note-replace (**) in the link with (tt).
Sent from my GT-P3100 using xda app-developers app
Fastboot sais "Waiting device"...
ofwise said:
Fastboot sais "Waiting device"...
Click to expand...
Click to collapse
Well, your f*cked.
Sent from my GT-P3113 using Tapatalk HD
Son was playing Words With Friends and this Samsung Galaxy Tab 2 7" GT-P3113 was acting up. Only other recent change was my wife downloaded a Southern Living magazine. The screen went dark blue like it was on but not responsive.
None of the lengthy holding down the Power or Power and Volume Up would ever produce a reboot, only a battery symbol. I did get it into the load an alternate OS screen, but didn't try it.
Took into a Samsung Experience desk at Best Buy and they said it was DEAD. Apologized that this year and a half old unit was done and said that was "probably not what we were expecting as far as lifespan of the unit." Ya think????
Came home, as a complete noob with nothing to lose and downloaded Odin and the files to try and load the recovery. Odin recognized the device and tried to start installing but got to the first step and FAILED. Something about NAND.
So in your opinion is this completely dead or maybe I don't have the right files? If you have current links to the right files please point them out to me. I've spent tons of times find links that are dead.
Thanks!
dailyvideo said:
Son was playing Words With Friends and this Samsung Galaxy Tab 2 7" GT-P3113 was acting up. Only other recent change was my wife downloaded a Southern Living magazine. The screen went dark blue like it was on but not responsive.
None of the lengthy holding down the Power or Power and Volume Up would ever produce a reboot, only a battery symbol. I did get it into the load an alternate OS screen, but didn't try it.
Took into a Samsung Experience desk at Best Buy and they said it was DEAD. Apologized that this year and a half old unit was done and said that was "probably not what we were expecting as far as lifespan of the unit." Ya think????
Came home, as a complete noob with nothing to lose and downloaded Odin and the files to try and load the recovery. Odin recognized the device and tried to start installing but got to the first step and FAILED. Something about NAND.
So in your opinion is this completely dead or maybe I don't have the right files? If you have current links to the right files please point them out to me. I've spent tons of times find links that are dead.
Thanks!
Click to expand...
Click to collapse
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from www.sammobile.com exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
No logo for reboot, which sammobile files?
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
Tetakpatak,
Thanks for jumping in!!!
1. That's the thing. We can never get the unit itself to the logo screen using that method, only the battery screen with a little sunshine symbol inside of it and only when the unit is plugged in.
2. I found sammobile before but my search for GT-P3113 produces only Cellular South files. This is a wifi tab only without a carrier. Does that make a difference? Can I use any of the listed files? Should I try each one?
Thanks!!!
No luck with sammobile files yet
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
tetakpatak, thanks for your help! please see my other reply.
i went ahead and tried one of the sammobile files. guessing as to which one because this is a wifi not cellular tab. when i ran it i got...
>Firmware update start
>SingleDownload
>boot.img
>NAND Write Start!!
>FAIL!
>
>Complete(Write) operation failed.
>All threads completed. (succeed 0 / failed 1)
Does this mean it is completely dead or do I need to keep trying files from sammobile?
Thanks!!!
dailyvideo said:
tetakpatak, thanks for your help! please see my other reply.
i went ahead and tried one of the sammobile files. guessing as to which one because this is a wifi not cellular tab. when i ran it i got...
>Firmware update start
>SingleDownload
>boot.img
>NAND Write Start!!
>FAIL!
>
>Complete(Write) operation failed.
>All threads completed. (succeed 0 / failed 1)
Does this mean it is completely dead or do I need to keep trying files from sammobile?
Thanks!!!
Click to expand...
Click to collapse
Hmmm, it isn't definitely dead, of course. That guy in the service was anyway bit dumb IMO.
With JTAG, man of skills can repair any device, no matter how hard bricked.
Actually to get further, it would help to know if you can reach download mode or recovery mode?
Tried two more from sammobile
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
Tetakpatak,
Tried two more from sammobile and both failed. Once mentioned NAND and the other did not. I see there is a NAND Erase option in Odin. Is that something I should be checking before Starting?
Not sure what else to do.
Thanks.
Reply
tetakpatak said:
Hmmm, it isn't definitely dead, of course. That guy in the service was anyway bit dumb IMO.
With JTAG, man of skills can repair any device, no matter how hard bricked.
Actually to get further, it would help to know if you can reach download mode or recovery mode?
Click to expand...
Click to collapse
Sure, I can hold Power and Volume Down to get to the screen to load a custom OS.
I'm
1. Opening Odin
2. Loading in the file from sammobile in the AP field
3. Leaving Auto Reboot and F, Reset Time checked.
4. Letting Odin check the validity of the sammobile file
5. Then plugging in the GT-P3113 and hitting Start in Odin
Thanks.
dailyvideo said:
Sure, I can hold Power and Volume Down to get to the screen to load a custom OS.
I'm
1. Opening Odin
2. Loading in the file from sammobile in the AP field
3. Leaving Auto Reboot and F, Reset Time checked.
4. Letting Odin check the validity of the sammobile file
5. Then plugging in the GT-P3113 and hitting Start in Odin
Thanks.
Click to expand...
Click to collapse
OK, @dailyvideo don't flash any P3110 build because the bootloaders differ in something!!
I have got meanwhile for you download links of an excellent stock UEUCMK3 firmware for your P3113 click HERE or you can also download it HERE
Now your flashing checklist:
use entirely Odin v1.85 or 3.04
run Odin as administrator
choose any stock firmware for your Tab and download (you probably did already), unzip it and you will get one tar-md5 file
tap in Odin on PDA, choose that extracted single tar.md5 file
run now (not before) your Tab into download mode
connect it with USB cable
Odin must display "Added" in status bar, left on the bottom
Odin must also display ID:COM port numer above it
If both there, click on "START"
Good luck!
Didn't work
I was using Odin 3.09 so I went back to 3.04 per your suggestion. I tried UEUCMK3 firmware I had already downloaded. Still didn't work...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Suppose I could try to use the firmware link you provided in case it is different. It's still downloading. Any other thoughts?
Thanks so much for your help.
dailyvideo said:
I was using Odin 3.09 so I went back to 3.04 per your suggestion. I tried UEUCMK3 firmware I had already downloaded. Still didn't work...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Suppose I could try to use the firmware link you provided in case it is different. It's still downloading. Any other thoughts?
Thanks so much for your help.
Click to expand...
Click to collapse
NAND is vital part of the device, IDK if it has to do with the bootloader. We might need a developer's advice, @Android-Andi, what do you think- can we help this poor mate?
Still trying
Ran again with your firmware and got the same results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I tought I just wrote back....? My post is gone...
NAND is vital part of the device, may consist bootloader or some other really important things.... IDK exactly, we might need a developer's advice here. @Android-Andi what do you say about this problem?
Thanks, next?
tetakpatak said:
I tought I just wrote back....? My post is gone...
NAND is vital part of the device, may consist bootloader or some other really important things.... IDK exactly, we might need a developer's advice here. @Android-Andi what do you say about this problem?
Click to expand...
Click to collapse
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.
dailyvideo said:
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.
Click to expand...
Click to collapse
He will see our mentioning and check this as soon as he can (he works now).
Try to google a bit about NAND partition, don't panic and have bit of patience, we will try to solve it.
Service can solve it for sure (not the dumb guy you've talked to )
Will wait
tetakpatak said:
He will see our mentioning and check this as soon as he can (he works now).
Try to google a bit about NAND partition, don't panic and have bit of patience, we will try to solve it.
Service can solve it for sure (not the dumb guy you've talked to )
Click to expand...
Click to collapse
Thanks will wait to hear back from you guys. Really can't tell you how thankful I am.
To the guy's credit at the Samsung Experience desk at Best Buy he couldn't get the OS screen to come up. I have trouble with it too at times unless there is enough of a charge. He said if he could get it to a certain point he could drill in and work with the code and really wanted to. I think because he could get to the OS screen he just assumed it was dead. To his credit too his dad died within 48 hours of our visit to the store.
Looking forward to the wizard advice.
dailyvideo said:
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.
Click to expand...
Click to collapse
Can you give this firmware a shot ?
http://terafile.co/82942a5b4d57/P3113UEUCMK3_P3113XARCMK3_XAR.zip
and one more mirror link if download speed is slow from above URL :
http://rapidgator.net/file/ec20cf98f5f712958760fd2b0457f939
But please make sure only Auto-reboot and Reset time are checked inside odin.......
No luck with new firware
Thanks lokesh, but still no luck. Here were the results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
dailyvideo said:
Thanks lokesh, but still no luck. Here were the results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Brother, Try using this .pit file that i am gonno share :
https://www.dropbox.com/s/wvn09tw1780irei/gt-p3110.pit
click on PDA in Odin and navigate to .pit file you have downloaded.
Now select the firmware you have downloaded as PDA and make sure only reboot option,,Repartition and reset time are checked.
Try this and give me a feedback soon.
Clarifying
lokesh.3440 said:
Brother, Try using this .pit file that i am gonno share :
https://www.dropbox.com/s/wvn09tw1780irei/gt-p3110.pit
click on PDA in Odin and navigate to .pit file you have downloaded.
Now select the firmware you have downloaded as PDA and make sure only reboot option,,Repartition and reset time are checked.
Try this and give me a feedback soon.
Click to expand...
Click to collapse
Lokesh,
Thanks for hanging in there with me. Just to clarify. Are you saying load your .pit file with the PIT button because when I click PDA to try and load that a .pit is not a valid extension.
Also, are you saying to load the .pit with PIT and the .md5 file with PDA ans Start with the Auto Reboot, Re-Partition, and F. Reset Time Options checked?
Just making sure I have all this right.
Thanks.
dailyvideo said:
Lokesh,
Thanks for hanging in there with me. Just to clarify. Are you saying load your .pit file with the PIT button because when I click PDA to try and load that a .pit is not a valid extension.
Also, are you saying to load the .pit with PIT and the .md5 file with PDA ans Start with the Auto Reboot, Re-Partition, and F. Reset Time Options checked?
Just making sure I have all this right.
Thanks.
Click to expand...
Click to collapse
You should choose in Odin just like last time: firmware under PDA. In addition, also choose PIT file under PIT. The PIT file will ensure your system partitions will be set properly.
If this also fails, it is possible that your internal memory is maybe corrupted and nothing can be written on the card.
GT-N8013
Blue/Gray
16GB Wifi Only Model
I was watching a youtube video, my tablet froze for an hour, died, then I let it charge and it rebooted into the samsung logo. After that it decided to go white screen and goes to a white screen every time it's booted. I've been trying to resolve this on my own with various resources for about a month now.
I can get to ODIN mode no problem, but I can't flash anything. I have recently bought a new OEM Samsung USB cable and tried multiple versions of ODIN on two different machines. Directly connected to the motherboard and not USB 3.0 ports.
I think the solution to my problem may be answered:
Here: http://forum.xda-developers.com/showthread.php?t=2268735
or
Here: http://forum.xda-developers.com/showthread.php?t=2713297
It is hard for me to comprehend the English used in the first link as I think Authors first language is not English. I think what he is saying is that if ODIN is not working then you have to flash the PIT file via adb and a SD card, but I cannot access Recovery, and I don't recall fully how to use ADB in Downloading Mode, if that's possible at all. He also states I may need to downgrade my bootloader version based on the last ROM that I had on my tablet. If someone could educate me on that I'd appreciate it.
The 2nd link says I need the stock firmware for my country(I live in the U.S. of A.) and to nand erase all but I feel like that should be used as a last resort. I did download both N8013UEALI3(4.0.4) & N8013UEUCMI3(4.1.2) from sammobile.com though.
When I try to flash just a Recovery/ROM, with Autoreboot checked, I get the PIT error message below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, with Auto Reboot & Re-partition checked, I get the error message:
<ID:0/007> Added!!
<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>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT w/ Recovery/ROM, Re-partition Checked and Auto-Reboot checked, I get:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any assitance would be greatly appreciated, I've been without my tablet for a month now. I have any backup, I don't recall the ROM I flashed because it was so long ago, but I'm pretty sure the version was Jellybean. I know my recoevry was one of the later CWM TouchScreen Rom recoverys but I can't recall the version. Thanks for any help, please let me know what information I'm lacking or what I can do, thank you all for your time.
Update
Any assistance would be greatly appreciated. I have tried to different PIT files for the PIT mapping and they both failed. Getting pretty desperate now. I can't even NAND Erase All, I gave that a shot and it failed:
When I select NAND Erase All, stock rom(4.0.4 or 4.1.2), Pit, & Re-Partition checked, Nand Erase all Checked, I get the following in ODIN 3.07 and 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.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> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think its the ECCM and maybe I need a JTAG repair. Like I said before, I can't get into recovery, I just get a all white screen. When the tablet first died I got the Samsung logo and then it rebooted and went White, I never got the Samsung logo again. Any help please? Even if it's just recommendations for trusted JTAG repair sites, because I don't trust the ones I've found ths far. Or know PIT files that have worked for flashing on the N8013. Anything at all.
BUMP
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.
onlysafonne said:
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.
Click to expand...
Click to collapse
@onlysafonne what file fails? I see your log above
carl1961 said:
@onlysafonne what file fails?
Click to expand...
Click to collapse
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!
onlysafonne said:
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!
Click to expand...
Click to collapse
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you
Heimdall
carl1961 said:
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you
Click to expand...
Click to collapse
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.
onlysafonne said:
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.
Click to expand...
Click to collapse
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
carl1961 said:
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Click to expand...
Click to collapse
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
if you not under warenty I would maybe buy a used one on ebay that might just have a cracked screen, you might even find a 32GB one
http://www.ebay.com/itm/Samsung-Galaxy-Note-10-1-32-GB-Wi-Fi-GT-N8013-/361155880699?pt=US_Tablets&hash=item54169166fb
onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
onlysafonne, I have the same problem. I can use Odin and get to CWM but nothing I flash will get me past the Samsung Galaxy Note 10.1 image I cannot even get it to shut off. It will go black then power right back up.
I have flashed with Nand Erase All checked only
KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_u ser_low_ship.tar
Any ideas? I have not heard of JTAG
I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks
Flying_Phil said:
I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks
Click to expand...
Click to collapse
have you tryed to odin install your firmware? usally the bootloop is caused because you need to do a factory reset to get rid of (in your case OmniRom 4.4.4) your firmware as I see is http://www.sammobile.com/firmwares/confirm/31427/N8010XXUDNE4_N8010BTUDNF1_BTU.zip/
Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or cwm recovery. But there is still twrp.
I can't open your link :-/
Flying_Phil said:
Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or can recovery. But there is still twrp.
I can't open your link :-/
Click to expand...
Click to collapse
try this N8010 recovery with the included 3.07 odin put in PDA slot and do no check re-partiton look at picture
@Flying_Phil
yes samfirmware is picky go here and search your N8010 you most likly need to signup (it's free) and as you see most odin updates or "home" which means it does not do a factory reset which is ok if your updating a stock unrooted rom so you need to do a factory reset when coming from a custom rom.
well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Flying_Phil said:
well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Click to expand...
Click to collapse
ok so did you try and reboot to stock recovery and do a factory reset
carl1961 said:
ok so did you try and reboot to stock recovery and do a factory reset
Click to expand...
Click to collapse
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.
Flying_Phil said:
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.
Click to expand...
Click to collapse
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB
carl1961 said:
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB
Click to expand...
Click to collapse
GT-N8010 16GB. Need more?
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Flash the latest Firmware .tar file with ODIN
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
Download the latest firmware for your Galaxy tab 2.
Use odin to Flash the file.
This is the method i always use whenever i get into some type of trouble. However in my case the open recovery or philz recovery method is useless. !!!
I download last ROM P5113UEBLH3_HOME.tar.md5
I tried to install with Odin, at middle of proccess, fail:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do?
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Samsung Galaxy Tab 2
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Galaxy Tab 2 Q&A, Help & Troubleshooting
Good luck!
Is tab rooted?
Not mentioned in op.
Without root flash will fall and you get stock recovery.
Pp.
Root?
Root, no was rooted.
Roby007 said:
Root, no was rooted.
Click to expand...
Click to collapse
Don't know what this means?
But check your root, it may be borked.
Use root checker from play store.
Pp.
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
I'm experiencing this exact issue, however it's with the LTE version of this tablet, model # SGH-I497.
It should be noted, starting with a stock tablet without root, I've TWRP'd + restored a "master image + rooted" backup on many of these same tablets in the past, all without any issues whatsoever.
The TWRP I'm using is an unofficial build by @tselling, filename recovery_twrp2.6.3.0_tselling.tar.md5 (can't remember which thread I found it in exactly)
Now, no matter what I do, I can't replace the Stock Recovery. Tried uninstalling and reinstalling the drivers (Samsung USB v1.5.14.0), disabled and re-enabled USB debugging, multiple flashes of the recovery.tar.md5 via Odin v1.85, different USB cables and USB ports on my computer, etc. I even tried a Factory Reset using the Stock Recovery, and doing everything again. This particular tablet has given me more trouble than the 10+ I've done in the past couple weeks.
Right now I'm just downloading this firmware from SamMobile, and I'll try the instructions listed at the bottom of that page. Will try using Odin 3.09 as instructed.
Here is the most recent Odin report I received after my latest attempt at flashing the recovery:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery_twrp2.6.3.0_tselling.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> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
---------- Post added at 12:44 PM ---------- Previous post was at 11:47 AM ----------
So I tried flashing the stock firmware, no luck. This is the report I got from Odin:
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I497VLAMJ2_I497XACAMJ2_I497VLAMJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sbl1.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If it helps, while in Odin Mode my tablet says that Qualcomm Secureboot is ENABLED. It also displays a "Secure Check Fail: sbl1" message after the flash failure.
Anybody have feedback/fixes for this?
I am unfortunately still stuck
Also of note, my previous successful attempts on these tablets never added to the flash counter, i.e. it always remained at 0.
I checked this morning on the tablet that's giving me so much trouble, and it counted each one of my 6 unsuccessful attempts.
I got TWRP to stick!
@Roby007
MAJOR UPDATE - after racking up a healthy 10 on my flash counter, I finally got TWRP to work!!!
My SGH-I497 has just been sitting on my desk since my original post, completely Stock Samsung and non-TWRP'd. Today, I decided that I would give it another shot.
What I did, step-by-step:
1. Settings > ensure that USB debugging is enabled > ensure that when using Minimal ADB and Fastboot that "adb devices" returns the Device ID > disconnect device's USB cable from PC.
2. Right click on Odin3 1.85.exe file > Run As Administrator > click PDA option and select twrp2.6.3.0.tar.md5 recovery file.
3. Power the device down > boot into Odin/Downloading Mode using Power + Volume Down buttons then Volume Up button to continue > reconnect device's USB to PC and ensure that device gets "Added" in Odin.
I repeated above process four times, each time with a slightly different iteration, detailed below:
Iteration #1 - USB Port 1 with Auto Reboot checked and F. Reset Time unchecked
Iteration #2 - USB Port 1 with both Auto Reboot and F. Reset Time checked
Iteration #3 - USB Port 2 with Auto Reboot checked and F. Reset Time unchecked
Iteration #4 - USB Port 2 with both Auto Reboot and F. Reset Time checked
Despite receiving no errors and Success/Pass messages each time, Iterations #1-3 did not work - I still had the Stock Recovery after each flash.
Iteration #4 however was successful, and I finally have TWRP on this device! I wasted no time in restoring my carefully-crafted master image.
I really hope this post helps you out - I know from firsthand experience how frustrating this can be.
(Apologies if I'm keeping this thread alive unnecessarily, however it's proving very useful for documenting my ongoing challenges with this TWRP-not-sticking issue. Hopefully someone else will find it useful as well.)
MAJOR UPDATE 2
I encountered the same "TWRP not replacing Stock Android Recovery" issue today, this time with a different device, a Samsung Galaxy Tab 2 10.1" tablet (model # GT-P5113, WiFi-only).
I tried the method that worked for me above, i.e. changing the checkbox options in Odin and switching USB ports/cables. 16 flashes later on the counter, and still no TWRP.
After doing some more research, I came across this post by @Android-Andi. Following the steps, especially numbers 9-14, resulted in a successful TWRP flash. I actually unchecked both Auto Reboot and F. Reset Time, waited 2-3 minutes after Odin's "Success/Pass" message, then disconnected the USB cable and booted directly into TWRP Recovery from there.
I also found this guide for the S4, although the steps that refer to Odin appear to be relevant for any Samsung device. Right after Step 7, there is instruction that follows a similar process outlined above, however with an added battery pull for good measure.
Hi All,
I was using the SM-N915A as normal...then i left it idle for a while and came back saw it kept resetting itself. I tried clear cache partition already didnt' work. It keeps looping on startup after the samsung logo. It got worst as time went on, it wont even load into recovery anymore, it just loads with the android icon saying it's updating then freezes and restarts....I read that I can manual recover using Odin. I used odin and a stock rom to fix it, but the rom failed now i am bricked. Please help.
Odin3 v3.10.7
Stock Rom: AP_N915AUCU1BOC6_CL4376893_QB4361884_REV00_user_low_ship_MULTI_CERT.tar
Log
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> NAND Write Start!!
<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)
At this point i am bricked..."the phone just says firmware upgrade encountered an issue please recover mode in Kies and try again" Kies/SS doesn't work, when i plug in this phone, it doesn't recognize it.
What can I do now?
pubtemp said:
Hi All,
I was using the SM-N915A as normal...then i left it idle for a while and came back saw it kept resetting itself. I tried clear cache partition already didnt' work. It keeps looping on startup after the samsung logo. It got worst as time went on, it wont even load into recovery anymore, it just loads with the android icon saying it's updating then freezes and restarts....I read that I can manual recover using Odin. I used odin and a stock rom to fix it, but the rom failed now i am bricked. Please help.
Odin3 v3.10.7
Stock Rom: AP_N915AUCU1BOC6_CL4376893_QB4361884_REV00_user_low_ship_MULTI_CERT.tar
Log
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> NAND Write Start!!
<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)
At this point i am bricked..."the phone just says firmware upgrade encountered an issue please recover mode in Kies and try again" Kies/SS doesn't work, when i plug in this phone, it doesn't recognize it.
What can I do now?
Click to expand...
Click to collapse
Get md5 tar file & make sure your in download mode connect phone to Odin and try again
pit file with Odin 3.07 0 3.09 single and tell me how it went
pubtemp said:
Hi All,
I was using the SM-N915A as normal...then i left it idle for a while and came back saw it kept resetting itself. I tried clear cache partition already didnt' work. It keeps looping on startup after the samsung logo. It got worst as time went on, it wont even load into recovery anymore, it just loads with the android icon saying it's updating then freezes and restarts....I read that I can manual recover using Odin. I used odin and a stock rom to fix it, but the rom failed now i am bricked. Please help.
Odin3 v3.10.7
Stock Rom: AP_N915AUCU1BOC6_CL4376893_QB4361884_REV00_user_low_ship_MULTI_CERT.tar
Log
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> NAND Write Start!!
<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)
At this point i am bricked..."the phone just says firmware upgrade encountered an issue please recover mode in Kies and try again" Kies/SS doesn't work, when i plug in this phone, it doesn't recognize it.
What can I do now?
Click to expand...
Click to collapse
ltindi32 said:
pit file with Odin 3.07 0 3.09 single and tell me how it went
Click to expand...
Click to collapse
Thanks, I managed to use the pit file and it got pass the brick page.
However, now the system goes into the Samsung Galaxy Note Edge loading screen and just stays there for a very long time and then restarts itself again....I pulled the battery out to manual shutdown (power button will not shut it down) and tried to go into recovery mode, it says loading recovery, but ends up restarting back to the Samsung loading screen indefinitely again. I would assume that's because the rom is dead at this point, and I would need to go to dl mode and flash a new stock rom back in ? What is my next step ?
pubtemp said:
Thanks, I managed to use the pit file and it got pass the brick page.
However, now the system goes into the Samsung Galaxy Note Edge loading screen and just stays there for a very long time and then restarts itself again....I pulled the battery out to manual shutdown (power button will not shut it down) and tried to go into recovery mode, it says loading recovery, but ends up restarting back to the Samsung loading screen indefinitely again. I would assume that's because the rom is dead at this point, and I would need to go to dl mode and flash a new stock rom back in ? What is my next step ?
Click to expand...
Click to collapse
I will upload the stock n915a cu2co2 5.1.1 for mega t pass the link to try with that
ltindi32 said:
I will upload the stock n915a cu2co2 5.1.1 for mega t pass the link to try with that
Click to expand...
Click to collapse
is this filmware with Odin3_v3.10.7. chek mark nand flash erase ALL_ATT_N915AUCU2COI2_N915AATT2COI2_CL5613658_QB6196305_REV00_user_low_ship_MULTI_CERT.tar.md5 enter the recovery mode and give him a factory resset and clear cache and comment. I improved my with this procedure. download it from herehttps://mega.nz/#!Ax5zEShb
ltindi32 said:
is this filmware with Odin3_v3.10.7. chek mark nand flash erase ALL_ATT_N915AUCU2COI2_N915AATT2COI2_CL5613658_QB6196305_REV00_user_low_ship_MULTI_CERT.tar.md5 enter the recovery mode and give him a factory resset and clear cache and comment. I improved my with this procedure. download it from herehttps://mega.nz/#!Ax5zEShb
Click to expand...
Click to collapse
It says I need the decryption key in order to dl the file.
pubtemp said:
It says I need the decryption key in order to dl the file.
Click to expand...
Click to collapse
!bawMPPRshf_1tFt1xeqtXh1a9zP1ow5KkRYaJlhXWf8
Hey guys, i have 1:1 the same problem with my n915fy. It dont boot and when i try to get in recovery it just stuck on booting recovery.
Have anyone the files for me too? I bought the phone Bricked.
Edit: Things I already tried:
Installed stock 5.1.1 per odin
Installed 5.1.1 per odin while checked the mark Nand earse all
Installed 4.4.4 per odin
Installed CWM per odin
Still stuck on Samsung Galaxy booting logo, when i try to go in Recovery menu its calls: " Recover booting" but just restart after one minute.
Hope someone can help me...
Btw where can i get pitfiles and would it help when i patch one?
pubtemp said:
Thanks, I managed to use the pit file and it got pass the brick page.
However, now the system goes into the Samsung Galaxy Note Edge loading screen and just stays there for a very long time and then restarts itself again....I pulled the battery out to manual shutdown (power button will not shut it down) and tried to go into recovery mode, it says loading recovery, but ends up restarting back to the Samsung loading screen indefinitely again. I would assume that's because the rom is dead at this point, and I would need to go to dl mode and flash a new stock rom back in ? What is my next step ?
Click to expand...
Click to collapse
You know what, try to clean power button. It may sticks. Pull battery and put small drop of rubbing alcohol. Then press couple times ( with out battery). Let dry for 10 min( you may use hair dryer on low power) . Put battery back and let us know.
Sent from my SAMSUNG-SM-N920A using XDA Premium HD app
Hey, i having the same problem, i was wondering if someone could make a step by step guide on how to fix it. also mine says mmc: mmc_write fail.
When i did Nand erase it says
mmc: mmc_read fail
ERASING USERDATA PARTITION
My SM-N915A went full dead on incomplete upgrade. Tried everything possible no lights, no vibration, no nothing: fill dear brick.
Was told its emmc corrupt.
Kindly help
can't you use samsung kies?
Hi to all. I was trying to recover some files with DrFone when it tried to root my phone. The rooting process failed and the phone bricked. If I try to power it on, it appears the writing "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Obviously kies can't connect to the phone.
If I press pwr+vol_dn+home and then select "volume up" the phone goes in download mode but doesn't accept the reset of drfone, the download process freeze at half...
What can I do?
Thanks in advance!
try flashing only pitt file
is there anyone that does this upload , reload repair for others. are is there instructions to follow somewhere?
ltindi32 said:
pit file with Odin 3.07 0 3.09 single and tell me how it went
Click to expand...
Click to collapse
thanks for the pit file,saved my n915a after encountering "DRK error" after the 6.0.1 update. Cheers