I have been researching this problem for a while now and I have read all sorts of threads from forums in every corner of the Internet, but I'm still completely stuck. Any help is greatly appreciated.
What I have is a SCH-i535 Verizon Samsung Galaxy S III (the model # behind the battery actually says SCH-i535V). It belonged to a friend of mine who announced he would be going "Office Space" on it after it stopped functioning. Seeing an opportunity, I asked if I could have it. This friend used his phone solely for regular Internet browsing, texting and email. He never flashed anything custom and it has never been rooted. As of this writing, download mode reports:
Custom Binary Download: No
Current Binary: Samsung Official
System status: Official
Qualcomm Secureboot: Enable
For the record, I don't know any details about the exact version of Android the phone ran before it failed (but I'm operating under the assumption that it ran 4.1.2).
When I first received the phone, it wouldn't get past the "Samsung Galaxy S III" boot screen. It also will not boot into recovery. It will, however, boot into download mode. Therefore, I booted it into download mode, hooked it up to Odin 3.09, downloaded the latest stock firmware from sammobile, and attempted to flash via Odin. Every time I try to do this via Odin 3.09 or 3.07, Odin hangs on the "Initializing" step and does nothing. Samsung drivers are installed, and Odin definitely recognizes the device.
I began researching and came across the Sudden Death Syndrome thread here, which is caused by eMMC failure. My symptoms sounded like the "Half SDS" symptoms in that thread (You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.). However, I believe SDS affects only the international versions of the SGS3, but please correct me if I'm wrong. Thus, I wrote SDS off.
Next, I attempted to use Kies to restore the phone. Using Kies, I used the firmware upgrade/recovery tool. It went through its thing, asked for my model number and IMEI, then downloaded the proper firmware. When it came time to install, however, it told me that it could not communicate with my device. Since then, when I power the phone on, instead of the Samsung boot screen, it now displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Download mode still works, however.
After reading about Odin issues, I tries using older versions of Odin. When I tried to flash the stock firmware using Odin 3.04, rather than hang on "initializing" like the later versions, 3.04 specifically says that there is no PIT partition. Ah, another clue! So I went in search of what the hell this means. By the way, I also tried different USB cables, different computers, different USB ports, popping the battery in and out, standing on one leg and clucking like a chicken, sacrificing a virgin, you name it. After trying Kies, I uninstalled it, and I double checked task manager. Kies is not running the background during my Odin attempts.
I finally found a 16GB PIT file for the SCH-i535 and downloaded it. I loaded it in Odin along with the "re-partition" option checked, and that's also a no go. The write just fails without any particular explanation. Just says "Complete(Write) operation failed. All threads completed (succeed 0 / failed 1). I even tried Odin 1.85, but same result.
I looked into JTAG, but that appears to be necessary if the phone is completely unresponsive and all it does is get you back into download mode. Well, I already have download mode, I just can't do anything with it. This leads me to believe my device is soft bricked, and not hard bricked.
I also followed a couple of tutorials that incorporate flashing bootchains using Odin (like the one here), but Odin wouldn't flash those either.
TL;DR version: ODIN won't write anything to my phone in download mode, and Kies can't do anything either.
I'm at the end of my rope. Short of an actual eMMC failure, I can't see any reason why this phone would be permanently bricked or why ODIN refuses to cooperate. Can anyone suggest anything?
One time bump.
That certainly is cause to go "Office Space" on it. I applaud your patience. However, I do not believe you are experiencing a Hard Brick. It certainly is frustrating that ODIN is not cooperating, but if it were Hard Bricked, I don't believe Download Mode would work. As far as flashing a pit file, aren't these included in Official ODIN firmware files?
Sent from my SCH-I535 using Tapatalk
I am experiencing the SAME EXACT problem. How did you manage to fix it? Thanks.
After I updated to 4.3 Odin wouldn't flash anything other than one 4.0.4 root66 tar. Perhaps you upgraded to 4.3 and that is why you are having troubles.
steinerbombz said:
I am experiencing the SAME EXACT problem. How did you manage to fix it? Thanks.
Click to expand...
Click to collapse
Post everything that you see in download mode
ThePagel said:
After I updated to 4.3 Odin wouldn't flash anything other than one 4.0.4 root66 tar. Perhaps you upgraded to 4.3 and that is why you are having troubles.
Click to expand...
Click to collapse
Agreed.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Post everything that you see in download mode
Click to expand...
Click to collapse
Literally, everything the OP did was what I did. It gets stuck at initialization every time.
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
Never rooted. Just doesn't boot anymore.
steinerbombz said:
Literally, everything the OP did was what I did. It gets stuck at initialization every time.
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
Never rooted. Just doesn't boot anymore.
Click to expand...
Click to collapse
What file did you flash in Odin because you need to Odin flash the 4.3 VRUCML1 image with Odin if your phone can still turn on.
Edit: Those last two lines inform me that you are on 4.3 OTA.
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
Click to expand...
Click to collapse
SlimSnoopOS said:
What file did you flash in Odin because you need to Odin flash the 4.3 VRUCML1 image with Odin if your phone can still turn on.
Edit: Those last two lines inform me that you are on 4.3 OTA.
Click to expand...
Click to collapse
Thanks, I had no idea what this thing needed. I tried stock.vzw_root66.tar and the guide here: androidayos.com/2012/09/19/fix-bricked-galaxy-s3-i535-verizon-unbrick-and-restore-guide/[/url]
None of them seemed to work. Just like the OP said, I got this phone from a friend before he went "Office Space - Die MOFO" on this.
I'm downloading the image you suggested right now and seeing if that will work. I will post results.
steinerbombz said:
Thanks, I had no idea what this thing needed. I tried stock.vzw_root66.tar and the guide here: androidayos.com/2012/09/19/fix-bricked-galaxy-s3-i535-verizon-unbrick-and-restore-guide/[/url]
None of them seemed to work. Just like the OP said, I got this phone from a friend before he went "Office Space - Die MOFO" on this.
I'm downloading the image you suggested right now and seeing if that will work. I will post results.
Click to expand...
Click to collapse
No problem, the pleasure is all @ThePagel since he was the one who found the 4.3 stock image. Show him some love if this all works out for you.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
No problem, the pleasure is all @ThePagel since he was the one who found the 4.3 stock image. Show him some love if this all works out for you.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Same thing, here is the log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Then it just gets stuck.
---------- Post added at 07:00 PM ---------- Previous post was at 06:55 PM ----------
steinerbombz said:
Same thing, here is the log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Then it just gets stuck.
Click to expand...
Click to collapse
If I try ODIN 1.85:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_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> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Follow his thread here. I'm actually heading out to work so I can't respond for awhile,
Tried the Verizon utility, gets stuck at ~83% then tells me that I disconnected the phone when I didn't.
steinerbombz said:
Tried the Verizon utility, gets stuck at ~83% then tells me that I disconnected the phone when I didn't.
Click to expand...
Click to collapse
Try the steps posted in the second to last post by rabidoyster. Looks like they were able to get around it somehow with a pit file.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Try the steps posted in the second to last post by rabidoyster. Looks like they were able to get around it somehow with a pit file.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I saw that, I tried that too with all different versions of ODIN.
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Seems that 1.85 is more verbose than 3.09 showing more progress than getting stuck at Initialization.
I am having the same problem, too. Odin recognizes my phone but does nothing. Whatever I try, after some time stuck at 'get pit for mapping' I get 'complete (write) operations failed' error. Tried all Odin versions, cables, uninstalling/reinstalling drivers, still no use. Help us!
steinerbombz said:
I saw that, I tried that too with all different versions of ODIN.
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Seems that 1.85 is more verbose than 3.09 showing more progress than getting stuck at Initialization.
Click to expand...
Click to collapse
maethelvin said:
I am having the same problem, too. Odin recognizes my phone but does nothing. Whatever I try, after some time stuck at 'get pit for mapIng' I get 'complete (write) operations failed' error. Tried all Odin versions, cables, uninstalling/reinstalling drivers, still no use. Help us!
Click to expand...
Click to collapse
You two should try jodin3. It will work for windows if you have java installed. Check the md5 outside of odin /jodin3 for the vrucml1 tar ball before just in case you have a bad download. In case you missed it the link for jodin3 is at the top end of the soft debrick guide.
---------- Post added at 09:17 AM ---------- Previous post was at 08:57 AM ----------
You can also try heimdall but it can be a pain because you need to extract everything from the tarball and add it in one by one. You also need to use a separate program to select the driver.
ThePagel said:
You two should try jodin3. It will work for windows if you have java installed. Check the md5 outside of odin /jodin3 for the vrucml1 tar ball before just in case you have a bad download. In case you missed it the link for jodin3 is at the top end of the soft debrick guide.
---------- Post added at 09:17 AM ---------- Previous post was at 08:57 AM ----------
You can also try heimdall but it can be a pain because you need to extract everything from the tarball and add it in one by one. You also need to use a separate program to select the driver.
Click to expand...
Click to collapse
I have the exact symtoms and have tried everything suggested but odin and jodin3 writes nothing to my device. Has anyone found a way to get past this? Any help would be much appreciated.
phantomzm said:
I have the exact symtoms and have tried everything suggested but odin and jodin3 writes nothing to my device. Has anyone found a way to get past this? Any help would be much appreciated.
Click to expand...
Click to collapse
I feel like there has been one or two solutions for this problem. I cant remember what they are so youll need to dig for them. One solution seemed odd and possibly dangerous. The other seemed like it got to the root of the problem and fixed it. Sorry I cant be of more help.
ThePagel said:
I feel like there has been one or two solutions for this problem. I cant remember what they are so youll need to dig for them. One solution seemed odd and possibly dangerous. The other seemed like it got to the root of the problem and fixed it. Sorry I cant be of more help.
Click to expand...
Click to collapse
Thanks for your quick response.
I have been digging through this forum for weeks and will continue to do so until I find something that works for me. That said, if you happen to remember what that fix that got to the root of the problem please let me know. It just seems like the phone is not granting write permissions to anything (multiple versions of odin, jodin3, verizon repair utility, kies) from download mode or "Firmware upgrade encountered an issue..." screen and if I could just adjust/override those that I can flash successfully.
Thanks again for your help
Related
I was attempting to follow the root instructions on the FP1 updated thread for rooting my my charge. (step 5)
This is my first time doing this so I picked up ODIN 1.85, the PIT file from IMNUTS and the 302 blue CWM link on the post. I followed instructions and got a fail. Now when I try to boot the phone I get an image of a cell phone and computer with an exclamation mark. I used the PDA setting as instructed. The error I got relates to not having a good pit or something. Did I download a corrupted file? any help restoring my phone to function would be appreciated.
ALSO: output
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 0302_charge_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
sometimes bad downloads do happen. try and download the PIT again, and remeber u only want re-partition checked in Odin, uncheck the other two. The PIT file MUST go in the PIT tab and the .md5 MUST go in the PDA tab, if you put it in one of the other tabs, well, UR ****ED! SO DONT DO IT!
No worries tho man, just try again and welcome to the world of a rooted Charge!
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
your phone got disconnected, thats the problem. just happened to me too. make sure ur connected to the usb in the back of ur computer. once connected put the phone down, in a place where it wont move, these connections can be quite delicate so any slight movement could cause a lost connection, and a FAIL in ODIN.
I changed usb ports and nothing. It still fails at about the 3/4 mark. when I do a test extract of the bin file I get a message about an incomplete block. I dont' have the md5 for the file so I'll start looking
just tried flashing a stock file... again with the removed command. I wonder if my cable is bad?
orcrist86 said:
I changed usb ports and nothing. It still fails at about the 3/4 mark. when I do a test extract of the bin file I get a message about an incomplete block. I dont' have the md5 for the file so I'll start looking
just tried flashing a stock file... again with the removed command. I wonder if my cable is bad?
Click to expand...
Click to collapse
Do you have the battery in when flashing? If not put it in.
You guys saved my bacon, I've installed superuser, though I'm going to let CWR die for now. I want to get tethering operational and let eclipse and the others put out a revision or two of the debloated fp1 before I fully rom up my phone.
I'm looking forward to my doing my homework on the beach thanks to this thing.
nitro already posted an eclipse fp1 debloated rom. just go to the topic that says its all the fp1 roms.
Having slept on it I may try the declared rom tonight. Thanks again guys.
Sent from my SCH-I510 using XDA
Using a stock cable is very important and unforgiving...solves most issues.
Now...if you are new to rooting/roms, etc... You jumped in at a less than stellar time....with new ota update...some kinks not ironed out yet
Sent from my SCH-I510 using XDA
I was a pro on my old droid eris. But the use of odin is still new to me. I actually don't have beef with touch wiz so de bloated roms appeal.
Sent from my SCH-I510 using XDA
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?
First time poster on here, long story short, I tried to root a Galaxy S6 sm-g920f with cf-auto-root. However, that put the phone into a bootloop. I have since downloaded the official g920f patch and it always FAILS right at the end after it says radio. It then stays on downloading screen. Anyone know how to fix this?
Any help is much appreciated.
Flash with stock ROM via odin.
arhjay said:
First time poster on here, long story short, I tried to root a Galaxy S6 sm-g920f with cf-auto-root. However, that put the phone into a bootloop. I have since downloaded the official g920f patch and it always FAILS right at the end after it says radio. It then stays on downloading screen. Anyone know how to fix this?
Any help is much appreciated.
Click to expand...
Click to collapse
Donwload stock rom from Sammobile.com and flash it via Odin / Download mode.
roydok said:
Flash with stock ROM via odin.
Click to expand...
Click to collapse
That's what I've been trying to do but it comes up fail still.
Tried another and it failed at writing NAND
With the sammobile one it gets stuck at SetupConnection
Screenshot below ( can;t post links yet
i . gyazo . com/96ec1ff68247a625c65fdd1b45ad138a.png
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOE3_G920FBTU1AODQ_G920FXXU1AOE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin engine v(ID:3.1005)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013> FAIL!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thats the sammobile stock rom
When trying to flash I get this message in red on download mode screen.
SW REV. CHECK FAIL. DAVICE: 2 BINARY: 1
Try changing ports from USB 2.0 to USB 3.0. Repeat flash as many times until you succeed. Took me 13x 1st time I flash 5.1.1.
roydok said:
Try changing ports from USB 2.0 to USB 3.0. Repeat flash as many times until you succeed. Took me 13x 1st time I flash 5.1.1.
Click to expand...
Click to collapse
Ok, going to try that now, thanks for the reply
This will come to Pass.
roydok said:
This will come to Pass.
Click to expand...
Click to collapse
Turns out my computer doesnt have usb 3... However, now I get stuck at SetupConnection
May try using jodin on macbook
EDIT: Getting the same nand write error now again
Ok, so after trying to reflash with AutoRoot it gets stuck on the start up splash "Samsung Galaxy s6 powered by android). At the top it says "RECOVERY IS NOT SEANDROID ENFORCING"
Please help
Try using another micro USB cable.
I have a Sprint G900P. It was on Lollipop 5.0
I needed to sim unlock but first I had to downgrade to 4.4.4 so I tried flashing a lot of TAR with odin from everywhere but it didn't work,
I saw a post where a used said I could install a Rom without downgrade the baseband.
So I installed a custom recovery, wipe data then flashed this ROM & Kernel trough recovery
http://forum.xda-developers.com/spr...t-sm-g860p-t2951239/post57007695#post57007695
It succesfully unlocked sim, but the ROM give me a lot of errors (many apps stopped working, buttons doesn't work)
Now I need to get back to 5.0 or at least a point where the S5 could work good.
Tried flashing Rwilco12 full tars but everytime the Odin says it failed.
Tried a lot of tars but I get the same Odin error. Don't know what else I need to do.
Can someone help?
Here's the odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1ANK4_G900PSPT1ANK4_3182645_REV00_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
you dont need to downgrade to sim unlock. and it sounds like youre getting bad downloads. Ive also had the instance where the name of the tar.md5 just needed to be changed and it worked. Also, how long it odin taking to load the tarball? It should take about 2 min from the time you select the file until odin is ready to flash, if its anything faster than 60 seconds, then something is wrong. The restore tar.md5s are huge and takes quite a while to load them in odin. Also, are you internationally sim unlocking or domestically?
i just saw your location in mexico, so i assume that you were using the SSU.apk to unlock, which does require the downgrade.
---------- Post added at 10:15 AM ---------- Previous post was at 09:23 AM ----------
this is a great place to get tar.md5s http://idoneapps.com/forum/index.php?topic=8.0, you just need to register to gain access to the tarballs
Thanks for answering. Yes I'm in Mexico. I used the ssu.apk and it worked great. I didn't downgrade. Actually it is not possible. I have tried like 5 tars and no one seems to work. I have tried difderent versions of Odin and different computers and I still getting the same fail error
Sent from my HTC6525LVW using XDA-Developers mobile app
Different cables too, I assume
Sent from my SM-G900P using XDA Free mobile app
also, have you tried getting one of the tar.md5 files from the idoneapps site?