My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/showthread.php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/showthread.php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
You have posted in the wrong forum, anything you flash from here will hard brick it.
Report your own post and ask a moderator to move it for you.
Fail at nand write is usually a dead emmc chip, try flashing full firmware with a pit as last resort.
As long as you can get into D/L mode, then you're fine. If you can get into D/L mode and your phone can turn on, it isn't hardbricked.
Try using this file (in case you're wondering, it's the 4.4.2 stock ROM). If it doesn't work on Odin 3.xx, try using it on Odin 1.85. I had the same problem, too.
Sent from my SPH-L710 using XDA Free mobile app
Related
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
aeinola said:
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
Click to expand...
Click to collapse
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Parva4 said:
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Click to expand...
Click to collapse
Send it for repairs and wait for several weeks to get it back? Very tempting. :cyclops: Lets call that plan B.
If i can do something to wake this baby up today or tomorrow i'll take it.
It sounds like you somehow softbricked your phone without even rooting it lol.
Anyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Instructions for unrooting: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
Hope this helps!
chunghanjie92 said:
IAnyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Click to expand...
Click to collapse
I did try that and it did not work. Maybe i did something wrong? Dont know... Im pretty sure the problem is with broken partition. I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Do not use pit or repartition unless you know what you are doing.
jje
Sent from my GT-I9300 using xda premium
aeinola said:
I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Click to expand...
Click to collapse
NEVER CHECK RE-PARTITION trololololo .... and never use PIT unless you are know what you doing.
Wow! These "never use PIT unless you are know what you doing"-comments are really helpful. Thank you guys! :good:
Follow the instructions on this site:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
The site tells you how to root a phone (look at the picture to see what you need/don't need to check; usually all you need to check is Auto-Reboot and nothing else)
After the phone's rooted you can download a ROM from this site http://samsung-updates.com/device/?id=GT-I9300 and flash it into the phone using the same method you flashed the file to root your phone
Thanks for the help. Odin says: "There is no PIT partition" and FAILS.
So i NEED to Re-Partition, any help would be appreciated.
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
aeinola said:
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
Click to expand...
Click to collapse
Same thing for me, and I'm stuck with this problem for 2 months now!!!
I read that for some reason unknown, some S3 got these fuc*** motherboards!!!
If u can solve this without samsung service center, please post!!!:good:
Of course you can manage it without Samsng Service center, if you want.
The procedure is:
1. download to PC the I9300 Service Manual;
2. buy motherboard;
3. replace it by yourself.
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
I'm not a robot
dckmnn said:
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
Click to expand...
Click to collapse
Hey brother I also had similar problem today midnight here in india . and i also tried several methods to restore my phone.
i tried kies also but but it required full rom package to download ,as my internet speed is slow I tried other method and it worked. I am very happy now :victory:
just connect your GT-I9300 in download mode. use odin 3.07. download CF-Auto-Root-m0-m0xx-gti9300.tar.md5 file that we normally use for rooting. Select pda in odin select CF-Auto-Root-m0-m0xx-gti9300.tar.md5 and click start.
Its just recovery related problem. my entire data is there as it is in my phone.
Hit thanks If I helped you
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
dckmnn said:
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
Click to expand...
Click to collapse
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
homer timpson said:
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
That though is written in the sticky's.
homer timpson said:
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
Sorry for the late response! The phone wasn't able to enter recovery, only download mode.
Another not robot here
[UPDATE]
I sold the phone "as is", I got it cheap and sell it almost at the same price so any mod can mark this thread as "Solved".
Easy come, easy go they say.
Regards.
Hello everyone
I apologize if you think this looks like a duplicate question but I could not find exact same features about my problem.
I've been trying to fix my phone for 2 days now so I thought I could ask for help to see if there is anything to do for my phone.
What happened just before :
I was using cyanogenmod 13 nightly and updated. It worked like a charm even fixing the camera.
I plugged it on the wall to charge and left my apartment. Sadly a storm went for 15 min before I got back to my apartment.
From this time, the phone was stuck on S3 logo.
What works right now :
I can go into download mode, the phone is recognized by computer
Info displayed are : odin mode / Product name : GT-I9300 / Custom binary download : yes (3 counts) / Current binary : custom / System status : custom
I can access recovery, I use TWRP 3.0.0-2
Touch is working well, but like other people I've got the mount error about storage, 0mb is displayed for any storage, and can't wipe or format data to fix it.
I can charge the battery as usual
What I tried to fix :
I tried using odin to flash custom rom, then stock rom 1 file from sammobile (several), even pit re-partition checking right boxes, sadly message is always :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use Heimdall too, with 3 different zadig drivers, I could download my pit several times, but could not flash : most of the times there was no response, handshake error, libusb error or protocol fail.
I tried several cables, and several usb plugs. Phone is always recognised by computer but can never transfer.
I tried to flash from micro sd card via twrp, but the 0mb displayed error prevented me from accessing the card.
I feel that my phone could still work, but I need advices on what to try next, and of people could diagnose the state of my phone, I might have forgotten some steps I completed, and really hope someone can help me try something new or tell me what's wrong with it.
Thanks in advance for your help, feel free to ask for any info I might have forgotten to write here.
Sun of rays from south of France, take care,
Emy -`ღ´-
Bump
Can somebody make a diagnosis about the state of the phone?
Do I need to change the motherboard?
Any help appreciated !
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
You can flash alone system.img, sboot.bin. ect using odin? Did command make_ext4fs /dev/block/mmcblk0p9 ect. work for you ?
Dead nand imo if 16gb
Use last twrp
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
rp158 said:
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
Click to expand...
Click to collapse
Hey, thanks for yout suggestion
Already tried that sadly
asadnow2k said:
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
Click to expand...
Click to collapse
Hey thanks for the suggestion
I downloaded this firmware, but now here is another problem, my phone stayed for 1 month + in my drawer with the battery in... My phone did not charge, for 2 minutes the screen reacted and I thought it was ok, then I tried to trun it on too soon, now does not charge at all... Im going to let it charge for hours now, and hope it will react...
If works than fine or try to get a test with new battery
Sent from my iPhone using Tapatalk
Okay to give the details I have a samsung galaxy note 4 most uptodate version. Earlier today I followed this video.
I cant post links yer but its a video by a guy named wwjoshdew on youtube titled THE EASIEST WAY TO ROOT THE SAMSUNG GALAXY NOTE 4. I would put the link but I cant.
I followed it step by step and made no mistakes and everything happening with his phone was happening with mines until 4:58 in the video. My phone got stuck on that screen while his continued with no issues the only difference is he was using an older version of odin and I was using a newer one. The other difference it our model numbers are almost the same but i have the t3 version and he just has the t version.
Now my phone is stuck on the screen at 4:58 the only thing I can do is hold volume down power and home to navigate to the warning screen. if i volume down to restart phone it simply brings me back to the screen from 4:58. However when i hit volume up I get brought to the downloading screen.
It is impossible for me to go to the recovery screen by holding volume up poer and home it just will not work for whatever reason. I tried downloading the galaxy note 4 2.2 GB stock rom and putting that in odins AP section and hitting start but it fails.
The code log says
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1EPE3_N910T3TMB1EPE3_N910T3UVU1EPE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone ot says sw rev check fail: aboot fused 2 > binary 1
1 emc write fail aboot.
I dont need root all I want is my precious galaxy note 4 to work again please some smart well educated phone person on here please save my precious note 4 and restore balance and earnesty to my life lol.
Im serious though im devestated over this and after looking at the date of the video and the comment section i see similiar things happened to people who followed this step by step. I didnt do anything wrong so not sure why this is happening please dont tell me its bricked forever please I have no money to get it fixed and need my phone please give me a glimmer of hope somebody please.
Check the model under the battery...Does it have n910T3 or just n910T? I think, for some reason, the firmware is a little different and can cause it to fail.
Another option, if you have the serial number, is to use Samsung Smart Switch for PC in emergency mode.
es0tericcha0s said:
Check the model under the battery...Does it have n910T3 or just n910T? I think, for some reason, the firmware is a little different and can cause it to fail.
Another option, if you have the serial number, is to use Samsung Smart Switch for PC in emergency mode.
Click to expand...
Click to collapse
Thanks but I was able to save it the other day by putting it in download mode and using kies to install the old firmware. Sucks that I lost my porn collection games save data music etc but well at least it works again. I dont need root that bad will never risk again lol.]
Greetings,
Right away, sorry if I'm posting this in the wrong spot.
My story:
One of my friends was about to throw away his tablet because of the "Firmware upgrade encountered an issue" problem. He took it to a "repair shop", they tried restoring the tablet with Kies and Smart Switch. They couldn't get it to work, so he gave it to me.
Kies does not detect the tablet.
Odin DOES detect the tablet, but flashing fails.
I've tried flashing absolutely anything I could find (apart from a custom rom, couldn't find one I could flash with odin).
I CANNOT flash ANYTHING with odin. Sometimes it fails on NAND write, other times it appears like the flash was successful because it says RESET in odin and the tablet turns off, but after turning it back on it goes right back to the "Firmware upgrade encountered an issue" screen.
The USB drivers are OK.
I've tried all ODIN version I could find from 1.85 to 3.11.1.
I CANNOT boot to recovery or download mode (if I could there wouldn't be a problem).
What could be wrong with it? What can I try to fix it? I'll try to list all of the things I tried to flash but forgive me if I forget some (there have been QUITE a few over the past 3 days of trying).
What I've tried to flash:
CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100
Clockworkmod_Recovery_for_P5100
espresso-any-root-kernel.v2.tar.md5
p5100-recovery.tar.md5
P5100XXAOF1_P5100BTUAOF1_BTU (stock rom region GB I think)
P5100XXDNA1_P5100NEEDNA1_NEE ([Pays Nordiques] 4.2
recovery-cache-fix.tar
philz_touch_6.03.8-jfltexx.tar.md5
CWM-root-P5100-v1
I've also tried flashing with PIT files:
gt-p5100_signed_espresso_20120220_16G
I've also tried to flash with NAND erase all (after everything else failed). That failed also.
I have no idea what else I can try.
I get this when I try to flash a stock rom:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XWALD7_P5100OXXALD9_P5100XXLD7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> system.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be GREATLY appreciated.
UPDATE:
I tried flashing P5100XXALD6_OXEALD5_v4.0.3_Repair_Firmware, it looked like it was going to succeed, but then the tablet powered off and now it doesn't turn on at all, not even to the "Firmware upgrade encountered an issue" screen. The battery only charges to 3.75 volts and then stops (measured with a multimeter). I tried removing the battery, completely discharging the circuitry (it was still showing 0.5 volts on the board after disconnecting the battery from the tablet). It didn't help. The tablet "turns on" just enough for my PC to play the USB CONNECTED sound, but the screen doesn't power on and it shuts down immediately (1 second in between the USB CONNECTED and USB DISCONNECTED sounds on the pc).
Did you manage to find a solution?