Hi guys. I'm trying to fix this phone for my brother. He said he went to factory reset and wiped his phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I put it in ADB mode to show more of the messages. I never flashed anything from ADB)
So it looked like he managed to wipe his systems so I downloaded Odin, installed the drivers and got the stock firmware from sammobile for his model. When I tried to flash it fails. I am not sure what I can do from here. Is the phone done? The previous forum threads were suggesting turning on USB debugging but the system isn't even on the device anymore for me to enable it.
I was thinking maybe I can flash it through recovery but I didn't find anything on google that said I could do that.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUDNH2_I317MOYADNH2_I317MVLUDNH2_HOME.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance. Any help would be greatly appreciated.
So I tried flashing a custom recovery both through Odin (get failed message) and through recovery (get cant mount /cache and /cache recovery)
So is this phone bricked?
any news? I have exactly same problem.
Same problem here, my friend's N7100 Hong Kong Version is dead just like this.
Stock 4.4.2 rom, not rooted, same message in recovery mode and Odin.
Please help!
Same here, stock recovery can't mount anything, ODIN mode can't flash anything, I think it is EMMC brick bug. N7105
Kicking myself for not copying a recent backup to external SD (it is on now inaccessible internal SD). Would be good if I could flash a decent recovery with some tools to try to get the internal SD card mounted, but I think nothing can be flashed at this point.
My SGH-i317M 16GB with Telus also suddenly failed to boot, and failed to flash using ODIN as well. After sent to several shops, including one which can perform JTAG flashing, confirmed that the eMMC is damaged.
This is not a simple software bug in eMMC, but a hardware failure, which requires to spend several hundred dollars in part and labour to replace the eMMC (embedded MMC 16GB NAND flash memory).
According to my weeks long research in the internet, this seems like a eMMC IC manufacturing problem on 16GB Note2 models in early release phones back in 2013, but not affecting 32GB model.
There are several users reporting that they used non-Samsung charger to charge the phone, including me, who use car charger. Poor quality charger somehow can shorten the life of the eMMC 16GB IC, and the phone will either slowly has storage corruption in this 16GB storage (which stores mount points /system, /data, /user). Unluckily this storage memory also stores the bootloader, recovery screen, charger percentage, Android OS, as well as user data + apps.
For me, it first reporting data issue by showing "I'm Lucky" button after booted up, which I though it resolved by factory reset without realize this is an early symptom of eMMC damage/failing. After 3 weeks, it stuck in boot screen, but manage to go to recovery screen, and neither Samsung Kies nor ODIN can write to the eMMC storage. This is later confirmed by a technician who has JTAG equipments/software that the eMMC is not writable at all, and needs to be replace.
The Android app that you can found on internet for the "fix" is actually a workaround, which will do a write test to identify bad block in eMMC storage which failed, and prevent the phone from using those areas to store any data. This app doesn't fix the hardware failure, which needs to be physically replaced. Theoretically, it can be replaced with 32GB eMMC IC but I don't find anyone posting the picture or model of the 32GB eMMC for SGH-i317M, as well as nothing for international model - i7100. If you are DOS users who used a floppy disk before, this is alike a dirty floppy disk with bad block, which the chkdsk utility can mark the FAT area for bad cluster to prevent DOS to write any data into those area. It is near impossible to repair the floppy disk to recover the bad cluster, unless replacing the disk.
For those who read this post early, and their phone is early release, and using the bad eMMC IC, I will advice to root it and install custom ROM which can boot from external fast microSD card, in addition of not using car charger and only use Samsung charger. This should prolong the time of eMMC lifespan
Hope this clarify for all users who has a failing eMMC chip, and be proactive about it
Related
i tried to restore my device to stock rom
downloaded N7100XXDLJ2_N7100OXADLJ2_OXA rom
went to download mode
started odin
got the tar file at pda
started to restore then stuck at this point
sboot.bin
then odin fails
here is the log
"
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDLJ2.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> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> param.bin
<ID:0/007> recovery.img
<ID:0/007> sboot.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
Samsung have black listed older bootloader (like 2012 released)
you can't flash that ROM (also not safe security wise) and chances are there some of also don't have SDS patched.
select some newer ROM
I don't recommend but if it is must to flash that ROM, use mobile odin (that won't flash bootloader)
i tried another new rom .. N7100XXDMC3_N7100OJVDMC1_EGY downloaded from Sammobile
and the same error
when it gets to sboot.bin i get fail and stop flashing
and the device stops at samsung logo and can't go in to use mobile odin too
is there any another way to solve this issue !!
Use pit file
First flash pit only
Then pit + rom
Sent from my GT-N7100 using xda premium
when i flash pit file the re-partition option got ticked .. do i un-tick it or leave it ticked ???
Yes you have to keep it selected (ticked)
Sent from my GT-N7100 using xda premium
still the same problem ... is there any way to bypass flashing sboot.bin ??
just thinking ... is there any way to erase any thing and every thing on the phone and start from the beginning .. flashing a boot loader then recovery then the room .. just thinking ... i guess it's a newbie question but had to try !!
What are the different potential reasons for Odin failing at the “sboot.bin” line? I’m flashing my Note 2 (GT-N7100) with the stock firmware (well, the one that had been listed at the top of the Recovery screen) using a brand-new Samsung-branded USB cable in Odin v3.09 and v3.11 and tried in each of my laptop’s four USB ports in turn, with nothing else connected to my laptop (not even a mouse) and no USB hub. I also tried using my brother’s laptop. I’ve included the full Odin log at the foot of my message as it’s different from the OP’s, going straight to sboot.bin and not reaching the other parts.
Only thing is prior to this I accidentally flashed a few incorrect stock ROMs before I found the right one listed in the Recovery screen. On each of these first four attempts with different ROMs I had received different failures in Odin, such as “system.img” and “boot.img” for two of them, and “sboot.bin” for the other two. None of them completed so I figured they can't have caused any damage but I'm certainly no expert.
Might flashing some incorrect stock ROMs have rendered it impossible to flash it with the right one once I found it, and cause it to fail at sboot.bin? Even if none of them completed?
My phone had been (and is) suffering the typical symptoms of being stuck on the boot screen, “E:failed to mount…” etc. message scroll in the Recovery screen, similar errors when wiping cache or doing factory reset while still in the Recovery screen etc. It meanwhile won't connect to Kies. When I try in Smart Switch it says it’s an unsupported device.
I'm a newbie who's learning the ropes Any help would be much appreciated!
<ID:0/023> 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/023> Odin engine v(ID:3.1101)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> SingleDownload.
<ID:0/023> sboot.bin
<ID:0/023> NAND Write Start!!
<ID:0/023> FAIL!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sboot.bin is failing because the ROM is not for your phone, the bootloader in the phone is newer than the bootloader in the ROM, you need to use the original Samsung USB cable, or a different USB 2.0 port.
Hi audit13,
Thanks for your reply, I appreciate it
Can I presume that the ROM is correct if it appears listed at the top of the Recovery screen? There’s a small chance I might have tried flashing that ROM in the first few attempts before realising you could check correct ROM there but then none of my flashing attempts with this or other ROMs ever completed so I guess it must have been listed there all along.
And if it is the correct ROM would it therefore be the right bootloader within it?
It's the most recent ROM for O2 network phones in the UK that I could find on SamMobile (PDA: N7100XXUFNJ1; CSC: N7100O2UFNJ1). The phone was locked to O2 when I bought it second hand so I paid for it to be unlocked and it ran fine for over a year with a different network. Because it was unlocked those first few attempts had been with the newest ROMs for unlocked UK phones I could find on SamMobile but none of them worked in Odin. Back when the phone was still working fine it continued to show the O2 splash screen after the boot screen after being unlocked.
First thing to do is boot the phone into download mode and confirm the model number. If the phone model matches the ROM, try different USB cables and ports.
Hi audit13,
Thanks again
The Download screen confirms it's a GT-N7100. The values on the subsequent lines are "Samsung Official", "Official", "0" and "A2".
Each of my laptop's USB ports are 2.0. I've tried flashing using the original cable of another GT-N7100 (my first Note 2 which I got new on a contract and clumsily managed to smash early in its life) when connected to each of the four ports and then same again with a brand new genuine Samsung USB cable.
The original cable was frayed at the end where it meets the connector. Meanwhile the new Samsung cable has a slightly different micro connector on the front side with the USB symbol (as per attached photo, which is old cable on left/bottom and new cable on right/top). The seller I bought from had and still has a photo of the old style connector but I guess if I ordered another I would get the new style again since that is what they sent out last time, and probably other sellers too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before I chance ordering another cable is there any chance it could be the wrong ROM after all or a problem with the bootloader?
Since the phone was locked and subsequently unlocked, the latest firmware for the original carrier should work.
Do you see anything in download mode about "warranty bit"?
As a test of the internal memory, I suggest flashing the tar version of TWRP via Odin: https://dl.twrp.me/t03g/
Boot into TWRP and flash a CM ROM for the gt-n7100: https://download.cyanogenmod.org/?device=n7100
If the phone boots CM, you'll know that the internal memory chip is probably okay and something else is going wrong when flashing a stock ROM.
NOTE: flashing TWRP will trip the knox/warranty bit counter to 1 from 0 which voids the manufacturer's warranty.
Hi audit13,
Thanks very much for that.
Yes, currently have "KNOX WARRANTY VOID: 0" in Download screen.
I've been away from my own laptop tonight so will try this tomorrow and report back. Really like the idea of testing the memory to rule this in or out.
Hi audit13,
I downloaded the “twrp-3.0.1-0-t03g.img.tar” from the link, attached it under AP but got the following log with failure. I tried this in each USB port in Odin 3.11 and Odin 3.09.
<ID:0/023> Added!!
<ID:0/023> Odin engine v(ID:3.1101)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> SingleDownload.
<ID:0/023> recovery.img
<ID:0/023> NAND Write Start!!
<ID:0/023> FAIL!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does that look like the memory is faulty then?
(I also tried the same with the “twrp-3.0.0-0-t03g.img.tar.md5” and the “twrp-3.0.2-0-t03g.img.tar.md5” on the offchance but Odin instead hug on Not Responding for 20+ minutes after selecting it under AP before I disconnected and pulled battery. I presume that’s because .md5 file extensions are for ROMs and .tar extensions are for CMs?)
The extension can be tar or tar.md5 when flashing in Odin.
Try Odin 3.07. If that doesn't work, it's possible that the memory chip is damaged or needs to be force flashed via jtag or a repair box.
Hi audit13,
Thanks so much for all your help
I’ve tried in Odin 3.07 and the same failures occurred.
I’ve looked into the JTAG method and think I’ll probably pass on that for this time but thanks for pointing it out. I can see potentially huge benefit of it for a pricey nearly new phone which is bricked whereas as it happens I have an option of donating its screen to my first Note 2 with broken digitizer. I’m glad to have given it a good shot at flashing it, and expanded my knowledge with your help.
Just out of interest, and because I’d like to ensure I don’t get another soft brick… The phone ran flawlessly for 12 months. It might be coincidence but shortly before the phone started going wrong I was staying at a hotel and needed to use the Wifi. I could only connect by ticking ‘Unknown Sources’ in my Settings under Security but forgot to untick it for about a week. About another week after that the phone suffered a slow decline of worsening problems. I started getting various errors, increasing in severity. At different times I had the following:
- downloaded iPlayer programmes disappeared
- occasional “Android is Upgrading” message when booting
- crashing and auto-resetting
- "Unfortunately [various apps] has stopped" message at random points when not even using whatever app it mentioned
- "Unfortunately Touchwiz Home has stopped" message whenever pressing Home, Back or Menu buttons)
- At times could only use touchscreen operations such as pull down notifications bar, open settings etc. but no use of Home, Back or Menu buttons
At various points in its decline I did factory resets in Settings but then the next problem would come along. I put it into Recovery mode and tried wiping cache partition and factory reset there as well but still no success. Then one day it lost its ability to boot.
That said you do see a few folk on forums with Note 2/3/4 etc whose phone suddenly stopped working, and no doubt other models (I’m a Note fanboy), with seemingly no indications of problems prior to that. Anyway, I’m probably digressing into another thread now.
Thanks again
Yes, I would agree that the phone is considered very "old" in the Android world. You cheapest fix may be to find a used Note 2 with a working motheboard and smashed screen. Swapping motherboards is very simple.
Ridil said:
still the same problem ... is there any way to bypass flashing sboot.bin ??
Click to expand...
Click to collapse
Unzip the rom, reselect all the .img and .bin files except zboot.bin and the bootloader file, rezip as tar and flash in odin
I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.
You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your problem
Click to expand...
Click to collapse
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.
OK, found this which seems to indicate I may be able to salvage data. Thanks for pointing me in the correct direction. :good:
I've got a followup question, if you don't mind. I've followed the instructions in the referenced article and Odin is reporting the following:
<ID:0/008> 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/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
I went to lunch, so I don't know how long it's been on the NAND Write Start!! but it's going on about 2.5 hours from when I clicked start and the process started going. The top left box is white and outputs SBL2. Should I continue to wait or start thinking something is broken/hung at this point? TIA!
Just updating the thread in case I can (a) solve the problem and (b) folks find it useful.
I have tried Odin 3.07, 1.87 and 1.83 to no success. They all seem to fail in about the same way, either at sbl2.mbn or at NAND Write Start!!. Waiting anywhere from 10-30 minutes doesn't seem to change anything. I've tried different cables and USB ports. I don't have another computer to try. Currently researching whether I should try to include the PIT file and if doing so will result in data loss.
wnoonan said:
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.
Click to expand...
Click to collapse
Well if that's the easier option, send me the S3 lol.
bilgerryan said:
Well if that's the easier option, send me the S3 lol.
Click to expand...
Click to collapse
Well, at some point you cut your losses. At this point I've spent the better part of 7 hours trying to get the phone recovered in some fashion. Multiple versions of Odin. Multiple USB cables. Multiple USB ports. Currently installing the Samsung USB drivers on another PC to try it all from there. I'll admit it, I'm not a cell phone developer (I'm a data center guy, want to know how to setup DFI, why you use FabricPath, what ACI is, why you use a pVC, how to setup OTV, etc. I'm your guy). I don't know the in's and outs of what a PIT file is, what it means when the phone just sits there at NAND Write Start!! and does nothing, and I can't seem to find an answer. Every article I can find seems to indicate I'm doing exactly what I'm supposed to be doing, but nothing works. I'm certainly open to ideas, but so far I'm not getting anywhere really.
And FWIW, I just fired up Odin3 v1.85 up on a totally different PC, with yet another totally different USB cable (so I'm not 0 for 2 on PC's, 0 for 3 on cables) and it's the same result. Starts the firmware update, sbl2.mbn goes, the next message is NAND Write Start!! but no progress is made and in the top left box, it's simply white with "SBL2". Clearly something isn't write, but just as clearly I'd be danged if I can figure out what it is.
bilgerryan, a question if you don't mind. You said "Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin." I have to confess, I have no idea what ND8, MK3, MD4, etc are, but at the QBKing77 link he mentioned a TAR file at a hotfile.com location, but that link appears to be dead. So I subsequently (after doing more reading in more threads) went here to grab what I presume is a valid TAR file, which I then extracted into a MD5 file. Odin seems to find it to be valid, but again it never seems to update. Any ideas? TIA!
OK. If anyone else happens to run across this thread, here are the things I attempted:
cf auto root chainfire - didn't work. It actually seemed like it was trying to copy, but would stop about halfway and never finish.
Tried the following ROM's. None of them would get past the NAND Write Start:
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
Tried multiple PC's, cables, ports, you name it.
Currently the phone won't even power on anymore. Not sure if the battery is just dead (tried another old battery, same result) or if the phone is just outright dead.
If this happens to you and you can figure out how to recover, you're a better man than I. Near as I can tell it's pretty much a total loss when this happens.
HTH.
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
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/show....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/show....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.
sdw8253 said:
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
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/show....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/show....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.
Click to expand...
Click to collapse
First thing, most of the time we moderators don't have time to go through every thread and post on XDA. Rather than asking us to delete a post in an obscure thread we may not see it would be helpful to us if you report it. I'm mobile right now so I can't do it but please report the other thread and make your request in the report.
Second, Odin isn't working because you're on a new bootloader. This one-click comes with the newest. Try flashing it. http://forum.xda-developers.com/showthread.php?t=2755793
Good luck!
If you were on KitKat 4.4.2 nd8 and tried to Odin the mk3 stock tar you've probably bricked your phone. Once on the nd8 boot loader and modem you cannot revert to an older version.
Many devs have bricked there phone with the new nd8 build.
I know I haven't answered all your w
Questions but I hope I've helped you understand what happened.
Luckily for you @rwilco12 has a solution for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIXED!
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
How do you force into download mode
badmojorayman said:
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
Click to expand...
Click to collapse
sparks.calvin said:
How do you force into download mode
Click to expand...
Click to collapse
Press and hold down Volume down and Home button.
While holding both the above keys press and hold the power button, then you will see the disclaimer.
Let go of all the buttons and press Volume up to accept the disclaimer.
The phone goes directly into ODIN/Download mode right after this. You will see a green droid which indicates you’re in ODIN/Download mode.
sdw8253 said:
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.
Click to expand...
Click to collapse
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
6th_Hokage said:
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
Click to expand...
Click to collapse
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
sdw8253 said:
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
Click to expand...
Click to collapse
ohhh okay well that's good; you got it sorted out
Hi, yesterday my note 2 decided to die. It shows the first boot screens but nothing happens. I can enter recovery (TWRP) and with ADB i see that i can't mount any partition on the internal sd. Running dsmeg there are a lot of mmc timeout errors, so i think that it's hardware related.
Download mode works as well, and even trying to flash .pit with odin doesn't help.
So i was thinking into try to boot some custom software from ram/external sd (yep i can mount external sd from recovery). It would be cool if somebody can guide me into how to boot custom software to play with, if possible
Kevgretor said:
Hi, yesterday my note 2 decided to die. It shows the first boot screens but nothing happens. I can enter recovery (TWRP) and with ADB i see that i can't mount any partition on the internal sd. Running dsmeg there are a lot of mmc timeout errors, so i think that it's hardware related.
Download mode works as well, and even trying to flash .pit with odin doesn't help.
So i was thinking into try to boot some custom software from ram/external sd (yep i can mount external sd from recovery). It would be cool if somebody can guide me into how to boot custom software to play with, if possible
Click to expand...
Click to collapse
You have twrp?
Then wipe and flash
Wipe: (data system, cache, dalvik cache)
Flash: (Rom+ Compatible Gapps)
MigoMujahid said:
You have twrp?
Then wipe and flash
Wipe: (data system, cache, dalvik cache)
Flash: (Rom+ Compatible Gapps)
Click to expand...
Click to collapse
Err...i think you missed the part where i say that i have a lot of mmc errors (aka no /system /data /cache partition can't be mounted and/or flashed)
Kevgretor said:
Err...i think you missed the part where i say that i have a lot of mmc errors (aka no /system /data /cache partition can't be mounted and/or flashed)
Click to expand...
Click to collapse
Oh, sorry, i saw "can't" as "can" in the adb part, anyway, that prevents you from doing anything actually, can you post the error you get when you flash the firmware with Odin??
Post the whole Odin log if possible..
MigoMujahid said:
Oh, sorry, i saw "can't" as "can" in the adb part, anyway, that prevents you from doing anything actually, can you post the error you get when you flash the firmware with Odin??
Post the whole Odin log if possible..
Click to expand...
Click to collapse
Here is the flash log
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFOE1_N7100ITVFOF1_N7100XXUFNG1_Home.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> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
When i try to flash .pit i just get stuck on "Get PIT for mapping..." then nothing happens until i disconnect the device
By the way i can't understand why boot and recovery partitions aren't corrupted either.
Kevgretor said:
Here is the flash log
When i try to flash .pit i just get stuck on "Get PIT for mapping..." then nothing happens until i disconnect the device
By the way i can't understand why boot and recovery partitions aren't corrupted either.
Click to expand...
Click to collapse
Unfortunately it's obvious, it's a "NAND Write error", that means your board is broken, you will need a new motherboard.
It's actually strange, many Note 2 users reported dead NANDs over the last couple of months
Sorry for the bad news..
Regards
MigoMujahid said:
Unfortunately it's obvious, it's a "NAND Write error", that means your board is broken, you will need a new motherboard.
It's actually strange, many Note 2 users reported dead NANDs over the last couple of months
Sorry for the bad news..
Regards
Click to expand...
Click to collapse
Yeah it's strange, at the beginning i blamed the CM 13 rom that started corrupting my /data partition, but now that is totally dead i think that wasn't rom-dependant
But there's a way to paly with this half dead phone, like edit the recovery/bootloader part to load a custom software from an sd card instead of the internal memory?
Kevgretor said:
Yeah it's strange, at the beginning i blamed the CM 13 rom that started corrupting my /data partition, but now that is totally dead i think that wasn't rom-dependant
But there's a way to paly with this half dead phone, like edit the recovery/bootloader part to load a custom software from an sd card instead of the internal memory?
Click to expand...
Click to collapse
I don't think so, the phone can't function at all with a dead NAND, sorry i think it's the end of the Road here...
UPDATE: I noticed that the original dev name of the internal mmc was mmcblk0. Now that is broken i can have my external sdcard under that name. So i repartitioned my external sd with the partitions that should be inside the mmc and i could flash the CM13 zip through recovery.
Now when i try to boot up the phone i have the CM boot animation playing! But the phone seems to not go through this process. I think that maybe i have to make some modifications to the rom actual kernel, but i don't know where to start.
Can somebody help me to troubleshoot this problem and help me booting the phone?
The /cache /system /data and /efs partitions are working well. If necessary i will post the full partition table of my ext sd card at the end of the day.
EDIT: currently can't access adb while the booting animation is playing
EDIT: i managed to boot and use the rom by creating those partitions in my sd card. Is a litte slow but is better than nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now i have problem with deep sleep. If the phone enters deep sleep it won't wake up anymore, forcing to reboot it with the power button long press. Any suggestions? I think it's kernel related
EDIT: Uh, ofc i can't connect via adb when is sleeping
Can you share how you r able to boot via sdcard?
Rawrjaaa said:
Can you share how you r able to boot via sdcard?
Click to expand...
Click to collapse
It's all written on the previous posts. You'll need gparted to format your sd card as on the image. An 8 gb sdcard is enough.
Hello All,
I have a Samsung Galaxy Tab 3 Lite (SM-T110). Recently, the phone crashed, and now stuck on boot loop. I tried to access the Recovery Mode to Clear Cache and perform Factory Reset, but the device keep rebooting with Samsung Logo. If I access the Download Mode, it works. I'm unable to find the official/stock ROM, and don't think a custom ROM will work without custom recovery.
I need assistance to get the device running again (Hopefully without clearing the data) ..
Flash TWRP using Odin 3.07 or newer:
https://drive.google.com/open?id=1yPxGpaMGSPHNckZ-UUISpqUWARNBCLC2
Select file in PDA, and UNCHECK AUTO REBOOT, exactly like in the image. After it finish upload image, hold power button. After successfully reboot, hold power + volume up + home till you get recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, you can flash ROMs using recovery. Just put zip on SD CARD, insert it on tablet and chose to see External SD CARD files, when press install.
Note, if you stuck in recovery, you need to flash stock recovery and start again .. .
Make sure you reboot tablet from stock recovery to unstuck it.
Here's stock recovery:
https://drive.google.com/file/d/1iSkrzZgTxjYNgyGsBeyWZZeMOGuoUnOn/view?usp=sharing
If you still don't rescue it, use this tutorial.
Download links are in description
https://www.youtube.com/watch?v=e7o3e6Km640
adryyy said:
Flash TWRP using Odin 3.07 or newer:
https://drive.google.com/open?id=1yPxGpaMGSPHNckZ-UUISpqUWARNBCLC2
Select file in PDA, and UNCHECK AUTO REBOOT, exactly like in the image. After it finish upload image, hold power button. After successfully reboot, hold power + volume up + home till you get recovery.
After that, you can flash ROMs using recovery. Just put zip on SD CARD, insert it on tablet and chose to see External SD CARD files, when press install.
Note, if you stuck in recovery, you need to flash stock recovery and start again .. .
Make sure you reboot tablet from stock recovery to unstuck it.
Here's stock recovery:
https://drive.google.com/file/d/1iSkrzZgTxjYNgyGsBeyWZZeMOGuoUnOn/view?usp=sharing
If you still don't rescue it, use this tutorial.
Download links are in description
https://www.youtube.com/watch?v=e7o3e6Km640
Click to expand...
Click to collapse
Flashing T110.TWRP.2.7.0.1.tar.md5 didn't work .. Odin gives "Failed" .. Tried the video, fails also ..
When I try to flash the TWRP, I get the logs below on the Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110.TWRP.2.7.0.1.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I started to believe this is a hardware malfunction .. Could be fried ROM
Did you tried to flash full ROM? You have a Youtube link in my post.
What is your country? I found my Stock ROM from a site (i don't remember) Maybe I can send you a Stock ROM!