"E:Failed to mount [Everything]" - Galaxy S III Q&A, Help & Troubleshooting

Hello gentlemen, here I am asking for help.
After trying different ROMs, I decided to go back to stock because of the frequent reboots. Today, after a few days since stock, all of a sudden the phone reboots itself and gets stuck on the Galaxy S3 logo (not bootloop). Opening recovery leads to a list of errors similar to this post, if not identical. Alas, being the d***head I am, i didn't backup EFS or system, or at least I don't know where did i put them lol

@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.

rp158 said:
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
Click to expand...
Click to collapse
Failed, here's the log
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Btw, the firmware I tried to flash was the one Kies gave me, then I downloaded it from sammobile. But since it didn't work out, could you explain me the second method, or link me a guide? Thank you

OP, your eMMC (your phone's, actually) might be on its way to the garbage - and might not. The problem is that if it is - it takes the whole phone with it.
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
After that, repartition FW + PIT, and if it fails - try working from a different PC. If it fails from any PC when trying to write eMMC - well, then you probably need to buy a new phone.
Repartitioning FW:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
or
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367

Hey @Jack_R1, thanks for your answer. Before I proceed with one of those guides, what do you mean with:
Jack_R1 said:
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
Click to expand...
Click to collapse
because I think I don't get what you mean

He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.

boomboomer said:
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
Click to expand...
Click to collapse
@boomboomer so is this to save files like pictures, music, videos, etc...? Because if that's the case, it doesn't matter really that much, the important matter is to make this phone work again. So, is there anything else I need to know before going with those guides?

Other that you'll probably need to buy a new phone, no.

boomboomer said:
Other that you'll probably need to buy a new phone, no.
Click to expand...
Click to collapse
Well, that's encouraging lol just out of curiosity, is there a reason becuase it stopped working all of a sudden and ****ed itself up so badly?

Nand memory wear.

Flash an official cwm or stock recovery.
Sent from a stolen phone!

Related

[Q] [HELP] Phone won't boot...

A question. After attempting to flash a theme... I got a bootloop. So I flashed the provided undo file. Now my phone will not boot past the Galaxy S 2 screen with the warning triangle. Any help? I'm kinda panicking...
dont you make any cwm backup first ?
i believe u can still enter recovery mode ( power + home + volume up ) ,
and do full wipe, and flash any other rom .zip .
p/s: i believe you already have root, and install any rom before
no i didnt... i was rooted. i have both cwm and download mode... but phone wont boot. I live in canada so samsung has not uploaded our stock rom files...
If it is not backup-ed, then you will have an issue.
Now, try wipe phone via CWM, clear cache and clear dalvik.
Finger's crossed it work.
If not, last choice will be install any Custom ROM and it will wipe (hopefully) all the not 'right' files.
nope.... nothing... guess i will take it in for warranty... thank you anyways my friend
I got that as well in the past, although mine was caused by incompletely flashing Cyanogen. Had a major freakout before I figured it out.
The only way I found to fix it is to flash stock firmware using Odin (and you will not be able to restore stock Canadian as it hasnt been released for us yet). I went with the xxKG2 (polish firmware I think).
There may be other ways to fix the problem but this will 99% sure take care of it. Your warranty will of course be void untill the Canadian firmware is released.
Cheers!
Sent from my GT-I9100 using XDA App
An additional note: from what I understand you're also getting the insecure kernel triangle. If the counter in download mode also shows that you flashed non-official firmware/kernel, your warranty could already be void. In that case Samsung may now honour their Limited Warranty Agreement.
Sent from my GT-I9100 using XDA App
right but when i purchased the phone i also purchased an extended warranty that covers software problems
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Ahh, well in that case, lucky you =D
Sent from my GT-I9100 using XDA App
ohyeahar said:
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Click to expand...
Click to collapse
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Click to expand...
Click to collapse
/emmc is the external sd card, you probably don't have one in the slot so it wasn't able to mount it.
The Yellow Triangle means you had something changed in the kernel partition, so the custom binary counter went up by 1.
As for stock rom, you will have to wait for Bell Canada to release one.
If you are not looking for stock, I'd recommend CyanogenMOD7, however it is still on nightly development, which means it has it fair share of issues.
I prefer CM7 and its problem over the stock which also has a fair share of issues.
if you can use downloading mode , you can flash back stock rom. believe me it will work.
you can study how to flash back stock rom using odin here --> http://forum.xda-developers.com/showthread.php?t=1075278
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
Click to expand...
Click to collapse
Are you sure you've "repeatedly" followed those instructions? You claim that flashing a stock ROM isn't possible. But those instructions require you to flash a stock ROM.
You don't have to flash the ROM that is specific to your region/carrier. Just flash ANY stock ROM to get your phone working again. Then you can flash back to whatever ROM you were on previously.
But if you wanted to get back onto whatever ROM your phone initially came with, you're out of luck.
hi all, my phone simply would not boot, it shows a down load error screen whenever i try to power up the phone.
i am not able to get into the reset screen using "up vol + home + power", but i am able to get to the download screen using "down vol + home + power"
I have tried flashing a stock rom using odin, but it just got stuck at
<OSM> CODE_I9100XXKG6_CL425236_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG6_REV_02_CL1044543.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKG6.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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
thereafter the screen went crazy flashing and now i am not able to power up the phone.
i a really at a fix as to what i can do. hope i am able to get some advice and thanks in advance~!
<ID:0/007> Set PIT file..
Wow... you repartitioned the phone. Something that was repeatedly told not to do. Now you have a screwed up partition.
Now you will have to find a official stock rom for your phone, and the correct pit file, then repartition it and hope it works.
The first rule of Odin (for 99% of us) : you never flash a PIT file.
I feel like that should be stickied front page. It would save a lot of people a lot of trouble and possibly around 700$.
Sent from my GT-I9100 using XDA App
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
edgeboy47 said:
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
Click to expand...
Click to collapse
Same problem? You mean you repartitioned the phone as well?
Double check the md5 checksum to see if it is the same as posted if it is posted at all. If not, double check the file size to see if they are the same. Most browsers say the file downloaded is complete when it was disconnected somewhere, and the file is incomplete.
I find it hard to take devs seriously, when they don't post filesize or don't post md5 checksum. Either that, or those two information is really hard to find, not on the download page.
http://www.villainrom.co.uk/forum/content.php/319
Ok so what i mean is cant start the phone I just get the logo with a yellow triangle at the bottom of the page so I tried to flash kernels but that doesnt help, but whenever I try to flash bigger files with Odin (I think they are firmwares, i downloaded them from Intratech's post) or Villainrom 1.1 it always fails when it says boot.bin in the message window for the big files and factoryfs.img for villain rom

[Q] Stuck In Download Mode

Hey all. There's a lot knowledgeable folks around here, so I thought I'd see if I can get some help on my problem.
I've got a Galaxy Tab 10.1 Wifi (GT-P7510, non-branded, UEKME), that I rooted about two months ago, using the instructions found on the Android Forums (can't post a link, but ti's the basic easy way to root, using Odin3). Not a superuser, but wanted to be able to back up everything. Seemed easy enough and the rooting went fine.
Haven't done anything else to it, aside from installing a few run of the mill apps. It did auto-update a couple of times.
Was working fine, now it just got stuck on this screen with a message:
Code:
ODIN3 Download Mode
(Protocol v2.1)
Reason: No Kernal
Secure Mode: Secure
Check Signature: Check
Custom Binary Download: No (0 counts)
Custom Binary: Samsung Official
Waitting USB Cable...
Downloading...
Do not turn off target!!
Apparently, it went to this screen while I was away. I didn't see it until I picked it up and there it was. It comes to this screen after the Samsung title screen (not the animation) and a VERY quick screen with some red writing (goes by too fast to see what it says).
I tried to follow the original instructions again. Put the tab in download mode (power + volume down), open Odin3, select the md5, and hit start. Get a FAIL with this message:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-cwm_4.0.0.4-sam-tab-10.1.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tab updates with this:
Code:
WritePArtition: Error to NvStorMgrFileWrite![err:0x30000]
DownloadPartition_odin: Error to WritePartition![err:0x30000]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0x30000]
That's as far as I've gotten. I noticed the Re-Partition option is not checked in Odin3, and the errors on the tab have to do with partitions... but didn't want to do that if I could eff it up even more.
I'm also wondering if one of the auto-updates didn't muck up the works. Maybe messed with my bootloader? Again, didn't want to go doing dangerous things without some reassurance. Also, I can't get into recovery mode; it just kinda flashes when I hit the button and stays on the option screen for download/recovery.
Any direction on how to proceed?
Any advice would be so great. It's been like this for about a week and I can't find any help. Thanks everyone.
TL;DR: Stuck in Download Mode, get errors on re-root.
This helped me and I've seen it help many others too in similar situations. Since you're stuck in download mode already it might need to be adjusted and followed from somewhere other than the beginning.
Goto http://www.teamovercome.net/p7500/?page_id=5
Towards the bottom of the guide There is a section called Restocking yer system.
Follow that on down.
Make sure you use the files for you device (7500 or 7510).
Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a Wipe data/factory reset.
Let us know how it goes, as this keeps us trying to help when we know we're successful.
Sent from my GT-P7510 using XDA Premium HD app
You have an incomplete bootsector the bootloader is broken but ofcourse your recovery is safe. Just flash a stock firmware on top of it, or flash CWM. You don't have to worry about the options being checked as Odin 1.83 onwards fixes this issue.
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Is there any other way to flash my firmware and/or repair my bootsector/bootloader?
Thanks for your help.
stusic said:
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Click to expand...
Click to collapse
If you followed what I posted, and triple checked every step and check box in the guide was exactly what you did, then I'm lost for other suggestions. Misledz is on a different time than here, so you can either try my process again, if that's what you used, making sure you do evrything as said in the restocking yer system guide on down or wait for more help.
Yeah, I was hoping because it was a really well written guide with links to the correct files right there that I'd have some luck. The directions are pretty straightforward, so I don't think I missed anything, but I can certainly try again.
Thanks, I'll update in a bit.
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
stusic said:
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
Click to expand...
Click to collapse
Sorry that sucks.
Hope Misledz or someone comes along for you.
Best of luck.
Edit: Looking at the Odin repartition error makes me think it may be a full hardware failure issue. But there is still hope with the right files or method for it to be fixed.
I can't find it, but there was another thread here with the same "Reason: No Kernal" error and I think it turned out to be a hardware failure.
Sorry well yeah I've been on offset timezone's and I tend to check this section regularly as I hope to learn more about the tablet In hopes I can get some development done on it.
In the sense I'll assure you that you can't really brick the tablet as they are somewhat hard to brick via software, unless you install a firmware that isn't compatible (Like a 7500 on a 7510) or like wipe the bootloader. Put it this way anything done in download mode is safe.
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Misledz said:
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
Click to expand...
Click to collapse
That's reassuring.
Misledz said:
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Click to expand...
Click to collapse
I notice the second file is in a p7500 directory. I'm guessing this is an all-encompassing directory with p7500 and 7510 files?
EDIT: I see that the file is for all versions (75xx). Thanks.
I'm at work now, but I'll try it when I get home and give an update.
Thanks for taking the time to help me out.
*fingers crossed*
Dammit. No luck.
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
brieuwers said:
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
If you check out his screen shot posted above it shows he used a pit file at least in one attempt
He's still having issues so your help with this would be and is highly needed and appreciated.
Sent from my GT-P7510 using XDA Premium HD app
I've used the pit file and tar file from the guide that Benzoman directed me to. I also tried using the updated CWMs that were suggested (although a pit file wasn't included).
I had installed the windows drivers a while back, but just installed the Kies. Interestingly, after that, I tried flashing again and, although it still failed, it took a lot longer (as opposed to almost instantly). Almost thought I had it for a second...
Am I right in thinking that I can use the pit file from the guide and the tar file from CWM together?
Slightly off-topic; what's the purpose of flashing a bootloader? That's one thing I haven't tried yet.
Thank you for your continued help. I would have lost all hope by now if it weren't for you and this forum.
So is it all good? I don't tend to like leaving people who need help Especially when it's also educational for me.
Flashing a bootloader wouldn't be advisable cause it may really brick the tab.
You don't really need to pit file as it is used for repartioning, flashing just the PDA is good enough
Misledz said:
So is it all good?
Click to expand...
Click to collapse
No, it's still stuck. It seems like any pit file I try doesn't work, which was why I was asking about the bootloaders (I know it's dangerous, but for all intents and purposes, it's already bricked).
I don't know what else to do; I was hoping the updated CWM would help, but it runs into the same problem the other pda files have. I'd be more than happy to try any other suggestions you may have.
Thanks again.
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
stusic said:
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
Click to expand...
Click to collapse
Sorry over my head, but hopefully Someone will look at the error and know what's going on.
Sent from my GT-P7510 using XDA Premium HD app

[Q] I9100G at least soft bricked

Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img​
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> cache.img
<ID:0/010> NAND Write Start!!
<ID:0/010> factoryfs.img
<ID:0/010> hidden.img
<ID:0/010> MLO
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
What exactly do you mean by that ?
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
NejaaHal said:
I didn't tried with a x86 computer yet but I will this afternoon.
Click to expand...
Click to collapse
MistahBungle said:
What exactly do you mean by that ?
Click to expand...
Click to collapse
I mean that my computer is running a 64bit OS (windows 7). I will get a computer running a 32bit OS this afternoon (maybe Odin don't like being run on a 64 bit environement <.<
MistahBungle said:
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
Click to expand...
Click to collapse
Bad downloads : maybe, but that would mean that the 3 or 4 differents downloads I did (because I thought of that possibility and I've tried to re-download the roms) all were corrupted at some point ^^'
Connection problem : maybe too, but (yeah again a but) I don't touch my computer at all during the process expeciallt to avoid the connexion to be broke.
PS : all my .tar.md5 archives gives me the "error" "There is no correct records at the end of archive" when I check them with 7-zip
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
MistahBungle said:
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
Click to expand...
Click to collapse
Yeah, I ment to use another computer ^^ I'm trying right now. Can you confirm me that a flashing can take one hour or more? (I'm not used to that amount of time)
And yeah, I don't want to give up and pay someone to do something I could do. I'm not a newbie in IT stuff, (even if I don't really know the architecture of an android phone and I don't know the use of the differents files in a rom).
7zip tell me that everything is ok about the downloaded .zip.
Thanks for the tip, I'm going to read that thread
No, a stock rom flash on the S2 should only take a couple of minutes tops. Normally in these situations, as long as you have download mode you can recover it, unless the NAND is messed up, then it's a JTAG (not always possible though) or in many cases a motherboard replacement. But forget that for now & only worry about that when you reach the end of the line so far as stuff you can try goes.
OK. So we can rule out bad download plus pretty much all the other stuff you've tried so far. Try on another machine & read his thread to make doubly sure there's not something really small/obvious we're both missing here.
ok, The ROM I've took come from sammobile so I guess it shouldn't take that amound of time.
That's factoryfs.img that take the most of the time ^^
I just realized that I forgot to launch Odin as administrator with windows 7 (my current try is on a x86 windows XP). But my previous (successfull ) flashes were like that too ^^'
I will continue to try on that other computer, but that will take some time to try all ports (since there is roughly 1h-1h30 to try to flash + the time for a full recharge of the battery <.<)
After having read a couple of threads here I realized that I took a .pit file from somewhere but haven't followed the step there :
[Fix] [Guide] [For Noobs] Recover from Corrupted Memory[USE EXTREME CAUTION]
But since I still not know how is organized an android phone I don't know if I've just used a generic thing that have just done nothing or if I could have messed up something. The file have this name : omap4_all_20110627_emmc.pit
I'm sorry for the double post : this is an update
The first try failed during factoryfs.img. I'm currently charging the phone for a next try.
So far I've tried
- I9100GXXLB1_I9100GATOKL1_ATO
- I9100GXXLSR_I9100GXEFLSR_XEF
- I9100GXXKL5_I9100GXEFKL3_XEF
Would anyone have any idea of which other rom I could try?
Shouldn't make any difference which rom you use, as long as it's an I9100G rom. Try every stock rom you're physically able to download; Sometimes with these situations you could try 10 flashes and they all fail, yet for whatever reason the 11th works. If I had a dollar for every occasion I've seen that happen on here over the past ~2 yrs, I'd have a fair bit of money - it's not super common, but it's not unheard of either.
So keep at it, perseverance might just recover it when trying every single thing you/everyone else on here can think of won't.
Okay, I'll keep going then ^^ may a custom rom work better?
I still don't understand why it take so much time ^^'
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No, as I said in my first post I can't access the recovery mode. or I don't do it correctly or it don't work anymore.
Hummm ok I will wait about the test firmware ^^' what could happend if it is not compatible?
I'm a little lost into the amount of rom available. Should I only try official roms? could I try other ones, if yes, which ones?
The worst part is that I don't remember which version was running on my phone. I was rooted, up to date I think, but that's all I remember, and I always see "only use this rom with a x.x.x rom" so <.<
also, after having tried so much time to reinstall it, does the indication "only use this rom with a x.x.x rom" still apply?
It doesn't matter which stock firmware you flash/whether it's specifically for your carrier or not. The aim is to get the phone working normally, so any stock I9100G firmware will do.
The suggestion to try a 3 part firmware is a good one, but I honestly don't know if there is such a thing for the I9100G as there is for the I9100.
You really need to start trying with a different PC and more than one if you can, because the alternative involves paying a Samsung service centre a not insignificant sum of money to fix your phone.
Done some google searching and it seems that there is no test firmware for your phone.....I WOULDN'T recommend using the one linked to in hopper8s thread.....the hardware in the phones (specifically the chipsets) are different......you'd probably kill your phone if you used it.
Below is a link to the latest firmware for your phone...
http://hotfile.com/dl/193267715/c98...GT-I9100G-XEF-I9100GXXLSR-1359122020.zip.html
Sent from my GT-I9100 using xda app-developers app
Thanks for all your answers.
I will then continue to try severals computers and severals roms.
I still wonder one thing :
would it be possible to install all the different parts separately? it always fail at the same step, is it possible to install the different parte one after the other? that would avoid me to have to wait 2h between two tries ^^
Also I wonder : what is the use of the .dll file I always find in the .zip ?
Edit : I just noticed something; in the latest version of Odin there is a option called "NAND erase all". would it be a good alternative to the 3-part test firmware?
I hate to do that but : little up about my last questions ^^'
NejaaHal said:
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img​
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
Click to expand...
Click to collapse
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Jimsilver73 said:
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Click to expand...
Click to collapse
Thanks ^^ but I am completly absolutely sure I have a i9100G ^^ because I already had problems before to find a way to root my phone ^^ and it say I9100G on the phone ;p I even tried to change it for a normal i9100 at the store I bought it but they told me they only had that version^^
Edit / news: I've tried to flash some part separately (from here :
[COLLECTIONS][MIRROR] Official Firmwares, Kernels, Modems, Bootloaders ). the bootloader don't fail, the kernel don't fail but the modem always fail while writing (now writing [...] -> blank line -> Received response from LOKE -> fail)
I don't know what to do now <.<
New question : have anyone any solution to allow me to have at least access to the recovery? is there any way to flash only the recovery? I made a lot of searches but couldn't find anything :/
If you can flash a custom kernel, you'll get (usually) CWM recovery.......then at that point you can do the full range of wipes and in theory flash custom roms.....
Sent from my GT-I9100 using xda app-developers app

[Q] [SOLVED] My Samsung galaxy s2 just got bricked, & now its between life and death

[Q] [SOLVED] My Samsung galaxy s2 just got bricked, & now its between life and death
Samsung Galaxy S2 LTE
Model name: SHV-E110S
No Custom Binary Download
Current binary is Samsung Official
Jelly bean 4.1.2 (90% sure)
Froze while using it and upon reboot froze at boot screen where the logo of "T" keeps rotating.
Firstly, being myself a complete Noob when it come to stuffs like Custom Roms, firmware, kernel etc got the phone in worse condition.
Upon reading few forums here, tried using Odion3 v 1.85 and tried fixing it following some ideas from these forums:
http://forum.xda-developers.com/showthread.php?t=1457458
http://forum.xda-developers.com/showthread.php?t=2016984
Reckoning that the mobile must have been soft bricked, tried using recovery package which failed as shown below:
http://oi39.tinypic.com/678nls.jpg
Then committed second mistake by using "PIT" file selecting Re Partition. After that on turning on the mobile, instead of BIOS, came "Odion Mode" where additional logo of "Update appears" The failed pic using PIT is shown below:
http://oi40.tinypic.com/14ihn5h.jpg
So, is there any hope for the phone or it's gone? It doesnt gets detected on kies but is detected on odion. I closed the kies in processes in taskmngr too.
So, please tell me what should i download now?
So, please help me everyone. I need all of your guidance.
I wont use that software without any knowledge.
Please tell me the steps to be taken by me now. I badly need that phone. There's no warranty now, so i dont want to go to customer care center.
And is there any way in which none of the files get deleted inside it. It's internal system memory is 2 GB. And USB memory is 12 gb. No SD card inside it.
Thank you!
best of luck
go here
http://forum.xda-developers.com/showpost.php?p=31319717&postcount=495
How?
gohel.vishal said:
go here
http://forum.xda-developers.com/showpost.php?p=31319717&postcount=495
Click to expand...
Click to collapse
I'm so sorry man, but i didnt understand anything from that forum. I mean the forum hasnt provided kernel for the SHV-E110S. I'm a noob. I'm so sorry
sulav_rock said:
Samsung Galaxy S2 LTE
Model name: SHV-E110S
No Custom Binary Download
Current binary is Samsung Official
Jelly bean 4.1.2 (90% sure)
Froze while using it and upon reboot froze at boot screen where the logo of "T" keeps rotating.
Firstly, being myself a complete Noob when it come to stuffs like Custom Roms, firmware, kernel etc got the phone in worse condition.
Upon reading few forums here, tried using Odion3 v 1.85 and tried fixing it following some ideas from these forums:
http://forum.xda-developers.com/showthread.php?t=1457458
http://forum.xda-developers.com/showthread.php?t=2016984
Reckoning that the mobile must have been soft bricked, tried using recovery package which failed as shown below:
http://oi39.tinypic.com/678nls.jpg
Then committed second mistake by using "PIT" file selecting Re Partition. After that on turning on the mobile, instead of BIOS, came "Odion Mode" where additional logo of "Update appears" The failed pic using PIT is shown below:
http://oi40.tinypic.com/14ihn5h.jpg
So, is there any hope for the phone or it's gone? It doesnt gets detected on kies but is detected on odion. I closed the kies in processes in taskmngr too.
So, please tell me what should i download now?
So, please help me everyone. I need all of your guidance.
I wont use that software without any knowledge.
Please tell me the steps to be taken by me now. I badly need that phone. There's no warranty now, so i dont want to go to customer care center.
And is there any way in which none of the files get deleted inside it. It's internal system memory is 2 GB. And USB memory is 12 gb. No SD card inside it.
Thank you!
Click to expand...
Click to collapse
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use ODIN V3.07 (latest version much safer much easier to use)
No problem with download mode
j.posarekar70 said:
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use
When i turn on my mobile, it directly opens Download mode. And it wont even close when i press power button. I've to force shut down by taking out the battery. There's no boot screen showing Samsung logo.
Actually i used odin3 v3.09 on first place. I knew nothing about it. so following a forum on recovering soft brick i switched to old version.
Click to expand...
Click to collapse
sulav_rock said:
j.posarekar70 said:
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use
When i turn on my mobile, it directly opens Download mode. And it wont even close when i press power button. I've to force shut down by taking out the battery. There's no boot screen showing Samsung logo.
Actually i used odin3 v3.09 on first place. I knew nothing about it. so following a forum on recovering soft brick i switched to old version.
Click to expand...
Click to collapse
You still have Download mode on the Phone, so your bootloader is still ok. Flash a stock rom image with Odin and you should be ok...post your results.
Click to expand...
Click to collapse
Questions
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
first of all, thank u so much for responding. Ok i'll try downloading the pre rooted ROM.
I'll post the results on the thread in the forum after it completes.
Since u're really talented in these stuffs, i wanted to ask u few questions.
1) Will installing Pre Rooted ROM root my device or not? Or do i have to root separately?
2) Will everything get wiped out? I'm sure wallpapers, messages, and settings configurations will be deleted. What about songs, photos? Will the USB storage get wiped out too? btw there's no sd card.
3) Can i recover anything? If yes. how?
sulav_rock said:
first of all, thank u so much for responding. Ok i'll try downloading the pre rooted ROM.
I'll post the results on the thread in the forum after it completes.
Since u're really talented in these stuffs, i wanted to ask u few questions.
1) Will installing Pre Rooted ROM root my device or not? Or do i have to root separately?
2) Will everything get wiped out? I'm sure wallpapers, messages, and settings configurations will be deleted. What about songs, photos? Will the USB storage get wiped out too? btw there's no sd card.
3) Can i recover anything? If yes. how?
Click to expand...
Click to collapse
1) Pre-rooted means just that, it is already rooted for your convenience.
2) Wiping data/cache can be different on different phones. It always wipe the internal data partition (place where app specific data and such are stored) and sometimes the internal user data storage (place where your pictures and other user files are stored). Whether the user data storage is cleared, I can't say for certain, varies between roms and phone models. (external sd card is never cleared, so that's why you should get yourself one and store your data there or in the 'cloud')
3) Depending on what happens in 2), yes or no. If it's wiped, it's gone, if not, then you're lucky I suppose.
When you manage to resurrect the phone, try to follow these rules...
- sync photos with Google+
- keep other data, songs, documents, etc... on the external sd card as much as possible
- sync contact, agenda/calendar, notes, and other personal management data synced with a cloud service (Google+, Exchange, etc...)
- make regular backups with for example Titanium Backup, Super Backup, etc...
- a Samsung account and Google account will help to automatically backup some settings, call logs, etc... (If you let/allow them)
so you have download mode,
download this pre-rooted stock rom here
then this pit file for e110s here
once the files are downloaded,
head to odin then choose pit for the pit file you downloaded
same goes for the pda file
then it should flash without any errors. after that if your phone is stuck in boot animation.
turn off the phone then Reboot to recovery (volume up+volume down+power)
use the volume rockr keys to navigate and power button to select an item.
choose wipe data/factory reset and cache.
flash the rom again without the pit file, only PDA to make sure everything is fine.
it should fix your soft bricked e110s.
Thank you so much.
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
Bro,
Thank you so much for all the trouble you took to help me. Finally, i was successful in fixing it.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E110SKSJMH2_SLIM_PR20130904.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> userdata.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> recovery.img
<ID:0/004> param.lfs
<ID:0/004> mdm.bin
<ID:0/004> cache.img.ext4
<ID:0/004> boot.img
<ID:0/004> amss.bin
<ID:0/004> aboot.mbn
<ID:0/004> ums.rfs
<ID:0/004> tomb.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
really want u to thank from my heart. Not only that, i've actually learned so many things in this 3 days regarding ROMS, multiple zip file etc.
So thanks again
best one??
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
Hi,
I'm sure you've flashed at least once samsung gs2 shv e1102 with custom ROM. Did it work? Actually currently, if it's safe i want to switch to the latest version that's available for my device. The stock is JB 4.1.2 So, is it bad if i use the latest verson which will trigger the status of Rom i guess. If it's actually good then i want to try it. Coz the phone has just been recover. There's no need to backup. And i've always been bothered by the sms limit of 80 letters. More than that, it becomes mms and will be sending failure. So, do u have any suggestions. And if i have to upgrade, which one will be good for me? And is the procedure same? By using Odin software?
sulav_rock said:
Hi,
I'm sure you've flashed at least once samsung gs2 shv e1102 with custom ROM. Did it work? Actually currently, if it's safe i want to switch to the latest version that's available for my device. The stock is JB 4.1.2 So, is it bad if i use the latest verson which will trigger the status of Rom i guess. If it's actually good then i want to try it. Coz the phone has just been recover. There's no need to backup. And i've always been bothered by the sms limit of 80 letters. More than that, it becomes mms and will be sending failure. So, do u have any suggestions. And if i have to upgrade, which one will be good for me? And is the procedure same? By using Odin software?
Click to expand...
Click to collapse
Go to this post and download the GT-I9210 Based MF1 Stock Root Ready rom. Same method as stock images with Odin. This is a regionalized version for the European S2 LTE variant. It works well on the E110S and will take care of that 80 character sms limit.
If you have warranty on the Phone, then you might be worried about triggering the custom binary counter, otherwise, don't worry.
Root/unroot
dc_power! said:
Go to this post and download the GT-I9210 Based MF1 Stock Root Ready rom. Same method as stock images with Odin. This is a regionalized version for the European S2 LTE variant. It works well on the E110S and will take care of that 80 character sms limit.
If you have warranty on the Phone, then you might be worried about triggering the custom binary counter, otherwise, don't worry.
Click to expand...
Click to collapse
Ok i'll download it. btw i dont have warranty coz the phone was bought in south korea itself. I didnt even find a flip cover case for that phone is my country. now the question Is there any latest version of JB where the sms limit has been removed. I mean any custom Rom having version greater than 4.1.2. If yes, which one should i download?
and the procedure is same isnt it? I've go in download mode(odin mode) and flash ROM using Odion on the PDA section isnt it?
sulav_rock said:
Ok i'll download it. btw i dont have warranty coz the phone was bought in south korea itself. I didnt even find a flip cover case for that phone is my country. now the question Is there any latest version of JB where the sms limit has been removed. I mean any custom Rom having version greater than 4.1.2. If yes, which one should i download?
and the procedure is same isnt it? I've go in download mode(odin mode) and flash ROM using Odion on the PDA section isnt it?
Click to expand...
Click to collapse
MF1 is 4.1.2. It is a stock based rom, but is identified as custom because some work had to be done with the boot kernel.
If you want anything later than 4.1.2, google cyanogenmod based roms for the e110s/celox devices. There's enough out there, but you have to put some effort into researching and finding it.
4.2.2
dc_power! said:
MF1 is 4.1.2. It is a stock based rom, but is identified as custom because some work had to be done with the boot kernel.
If you want anything later than 4.1.2, google cyanogenmod based roms for the e110s/celox devices. There's enough out there, but you have to put some effort into researching and finding it.
Click to expand...
Click to collapse
The link u gave me before also had Jelly bean 4.2.2. So if i download and flash that using Odin, will it also remove the sms limit. I actually want to switch from 4.1.2 to 4.2.2. The procedure is same isnt it? Flashing it on Odin. Or do i have to factory reset before flashing?
When i flashed official roms with Odin i never used PIT files. Just out the rom on PDA section and flash it. Usually wipe data/factory reset will erase your data on internal storage card,but in my case is not happeni g. I am trying custom roms on my s2 (i9100) and when i wpie cache,data and delvik,no data is lost from the internal memory. Still got my obb files,music and stuff. Try to flash your device using an official rom and after that i recommend omni 4.4.2. It is very stable for samsung galaxy s2.
Trimis de pe al meu GT-I9100 folosind Tapatalk
Bricked again after 2 years
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
You wouldn't believe it but my phone "Samsung Galaxy s2 LTE SHV E100s" got bricked today after 2 years. Yes i'm still using the same phone. And thank you for helping me out last time my phone got bricked.
I have a question for you. Hope you'll help me out this time too david.
1) Which ROM would be best for my phone now? Currently i had "pre rooted 4.1.2 JB" the one you gave me link. I'm sure you have tested all sorts of ROM's.
2) DO You have any new ROMS for shv e110s? if yes, is the procedure to flash it via odin same as before? e.g leave settings on default, select .tar file on pda section and flash?
Thank you!

Possible dead NAND SCH-I605?

Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Hellstorm32 said:
Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Click to expand...
Click to collapse
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Hellstorm32 said:
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Click to expand...
Click to collapse
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Hellstorm32 said:
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Click to expand...
Click to collapse
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Well, I hope I didn't jump the gun. I did use the .pit file in Odin 3.07, I just saw your message about Odin 3.12. I loaded the PIT in the PIT slot, loaded my ROM in the PDAslot, and it seems to be taking a while on the <ID:0/003> Get PITfor mapping..
Droidriven said:
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Hellstorm32 said:
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Click to expand...
Click to collapse
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Text in Odin so far..
<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> Get PIT for mapping..
Hellstorm32 said:
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Click to expand...
Click to collapse
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Hellstorm32 said:
Text in Odin so far..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Click to expand...
Click to collapse
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, I've closed Odin. I've disconnected my device. I've checked and yes, I can still enter download mode (phew, I don't have much hardmod skills to get it running if it's hard bricked).
I'm going to bring it in to Best Buy today and see if the Samsung staff can flash it there. I was running stock when this happened. It's crazy, I was driving my car and I had my phone in my mount on the dash. I just happened to look over and it was stuck on the boot screen. No warning. It just restarted and froze on it's own.
Thanks for the help, I'm going to keep working on it today and see if I can get things moving.
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Hellstorm32 said:
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Click to expand...
Click to collapse
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Hellstorm32 said:
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Click to expand...
Click to collapse
If you did NAND erase all its dead. I started to warn you when you first mentioned NAND to leave it alone and don't mess with NAND in Odin. You can send it in for JTAG service, its usually $50 and they send it back to you fixed. Cheaper than replacing the motherboard. JTAG is the last ditch effort.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
If you did NAND erase all its dead. You can send it in for JTAG service, its usually $50 and they send it back to you fixed.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Hellstorm32 said:
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Click to expand...
Click to collapse
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Great help. Thanks man. I think I'm going to look at new models and see about upgrading. I believe with all the battery problems on the Note 7 that Verizon is offering 0$ down as incentive to purchase one. I'll have to do my research, but it's listed as 36$ a month and I may be able to afford that. After I get a new phone, I'll do my best to get the old one working again (new mobo) and probably look to unload it on Ebay after it's up and running no problems. Either that or let my wife take tthe Note 2 over (She has an S3).
I'm bummed. Especially because this happened out of the blue. I was running stock ROM and phone rebooted out of the blue to the splash screen and BAM...dead. I've been able to recover devices before (I bricked a Stealth Trio 7 before and had to write .sh files to get the touch screen to work again), this is the first time I've been unable to fix an android device. Had to happen sometime.
Thanks again for your efforts.:highfive:

Categories

Resources