Related
Hey guys need some help. I've gone through as much of the forums as possible and still trying to resolve this without having to send it away.
My brother's SGS II has the following symptoms:
-turns on and stays at the SGS II GT-i9100 screen (will not change)
-phone can enter download and recovery modes
-when phone is plugged in to charge the battery symbol will not show that it's charging then continue to the SGS II GT-i9100 screen...then back to the battery icon (and loop)
-attempts to reflash anything will either be successful or fail in ODIN but still results in the 1st issue above.
What should I try next?
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Are you using pit file when you flash with odin ? could be partition problem so using pit would fix that
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Thanks for the sarcasm my friend but when I say i've gone through most of the forum as possible I meant I've tried both those fixes to no avail...thanks anyway though :good:
leechseed said:
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Click to expand...
Click to collapse
yeah right now I haven't gone any pit routes yet. I've gone through both boot/bricked guides and right now it's a wash...hell i'm getting a loop between the battery screen and GT-i9100 screen now.
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
MistahBungle said:
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
Click to expand...
Click to collapse
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Doing the .pit and re-partition as we speak and hangs up on the exact spot...DATAFS (data.img). *sigh*
I'm going to try the bootloader option next. I know my bro says he's done it already but I want to be sure. Thanks for your help man.
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
here's another note...when flashing bootloader it comes up into the recovery screen and says "E: failed to mount /data (unknown error: 0)
trying a format data/system
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
yeah i'm comfortable with flashing pit files due to my weekly rom addiciton from my SGS/cappy hahaha
Anyway I may be experiencing that corrupt SD card issue i've been reading about...not sure.
sminky01 said:
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
Click to expand...
Click to collapse
Why dont you just try to flash a Stock Rom??
I would try that first - wipe - flash Stock (via CWM)
I always used the ONE file package of Roms and never had any probs..
Why on earth are you re partitioning with Odin? You know Odin isn't build for the S II, and the re-partitioning it does is for the Nexus or something. IE using Odin to re partition an S II royally ****s it. Flashing a PIT might work but why don't you just start at a logical place, before going out and doing a full manual JTAG on your phone with a pair of pliers, some masking tape and a bunsen burner, why don't you do the obvious. Which is update your Odin, uninstall Kies and reinstall it for the Samsung drivers, check the USB etc. something is clearly going wrong during the flash process despite it being "successful". Failing that, take it back to the shop, if your phone isn't a £500 paper weight by the time you read this, just apply for a new one. Make sure you erase any evidence of you messing around with it and return it.
sirknattar said:
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
Click to expand...
Click to collapse
The problem might be the Omega rom ??? is it compatible with I9100M series or just the I9100 the M could be the clue to the flash failing same as when Samsung released the I9100G and people who flashed that got screwed up with the incorrect bootloaders since the hardware is different in the I9100 and I9100G same problem might exist with I9100M
Thanks for everyone's help and suggestions. I've got a vague idea of the problem now and it's being sent back to Samsung for warranty (after I clear it with the JIG).
try to do the following.
1-flash any gingerbread CF kernel via odin
2-boot into recovery mode
3- wipe everything under mounts and storage including system partition
4-reboot into download mode
5-try to flash the CM9 Resurrection Edition
hope this helps mate. mine just emmc bricked on me, with the crappy LQ5 samsung firmware and had to RMA the bastard.
check ur pm mate
Hi All,
Noob here with what I think is a soft brick issue.
Under the battery it says Model: GT-i9100, SSN: i9100GSMH
Originally Gingerbread, then I upgraded to 4.03 via official Kies firmware release.
Couple of days ago tried to upgrade to 4.04 using ODIN and got a fail at factoryfs.img. probably used the wrong firmware.
Could still get into download mode at that stage, but can't anymore. I tried to install a couple of different firmware versions of 4.04. I can still get 'added' when I connect to ODIN though.
Can somebody please help me to upgrade to either 4.04 or Jellybean? I'm willing to go fully custom, just don't know how to do it....Can I do it with ODIN? Do i need a new kernel or pit or something?
Thanks heaps, really appreciate any help.
Cheers,
Jackson
Given you can't get into download mode (and I presume the phone won't boot & you can't get into recovery either ?) it's either a JTAG or service centre job.
MistahBungle said:
Given you can't get into download mode (and I presume the phone won't boot & you can't get into recovery either ?) it's either a JTAG or service centre job.
Click to expand...
Click to collapse
Hi Mistah Bungle, thanks for your reply.
So is that even though the phone shows up as added in ODIN?
J
If the phone shows 'added' in Odin (yet the phone show no signs of life whatsoever; you still haven't clarified this btw), then you might as well try flashing a stock rom & see what happens. I mean, the phone's borked. It probably won't work, but it's not like you'll bork it worse if you do try another flash.
Forget about upgrading to 4.0.4 for now. Just download a stock firmware for you phone no matter Gingerbread or ICS. Search this forum, you'll find many links. Connect your phone to Odin and try flashing the downloaded stock firmware. Once you get it up and running, you can try upgrading it.
In this situation, it wouldn't be wise to go for a custom firmware. Your best chance of bringing your phone back to life lies in successfully flashing a stock firmware.
No problem if the screen isn't showing anything. I remember Vibrant behaving like this. Just flash the firmware once Odin detects your phone. If the flashing fails, disconnect, take out the battery and start over.
Good Luck!
Hi Guys, thanks for the updates. I'll try to suss out what the correct stock option is and try my luck. and yeah, for clarification purposes - the phone doesn't respond to anything bar an Odin connection as far as I can see. Cheers again )
Hello all,
I have tried many things before asking for help, but nothing worked so far.
Here is the story:
I was on ICS 4.0.4, with default ROM coming from carrier.
I wanted to install CM9.1,
spent countless hours doing all backup and reading tutorial.
Tried finally yesterday and it was stuck doing "wiping data". Left it for 20min+ and nothing.
After restarting it, it is now stuck on the boot logo.
I couldn't enter anymore CWM or stock recovery (up+home+power), but could enter Download mode.
So I tried a couple of things I have read on the forum, like installing Siyah-s2-v5.0.1.tar through Odin 3.04 but I still cannot enter recovery mode.
I've read (too late) about the mmc brick bug (couldn't find anyone speaking about it in any tutorial until I reached this point... nothing on CM wiki or in other tuto... classic!).
I hope I'm not in this case though as I can still go to DL mode, and the phones having the brick bug are completely dead (blank screen or no DL mode), as per http://forum.xda-developers.com/showthread.php?t=1756242
I managed to finally get CWM working only by using GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar from Odin, then tried to install CM9.1 from SD card but after reboot it is stuck on the blue cyanogenmod animation boot screen and nothing happens.
Tried also to restore from CWM my nandroid backup, but during the restore it seems to hang then restart by itself, and then I'm back to Galaxy S boot logo (the animated one with the big S).
And after this I have lost again access to recovery mode.
I can't go back to stock and I can't install CM... I was not expecting such issues, it all seemed pretty basic on paper.
I'm really stressed and don't know what to do
Flash a stock rom in Odin (download mode), re-root your phone/flash a kernel with CWM, restore your backup ?
Hi,
thanks for answering,
I have tried to locate such a rom, but I'm not sure which one... is there a specific one to try ? could you point me to it please ?
so far I have tried I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5
but no luck
you also say "re-root", at the time I used this method:
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel - xda-developers
http://forum.xda-developers.com/showthread.php?t=1501719
Do I need root to install Siyah kernel from Odin ?
I'm trying one from sammobile... let's hope :/
The bad thing is I had no Yellow triangle at the beginning since I'm stuck in this boot loop or no boot to be precise.
Now that I have tried different things to fix it, it is still not working and I have my flash counter = 10.
I cannot even go back to the shop, is there a way to reset it knowing I cannot even reach the OS, I have only DL mode or CWM...
Use a stock rom for your region/carrier (or any stock rom from any region really), it doesn't really matter as I presume you'll be restoring a backup and/or going back to a custom rom anyway won't you ?
Samfirmware & AndroidFirmwares.net have lots of stock roms.
No, you don't need root to flash an Odin version of Siyah. So yes, you can flash that after you've got stock up & running to root your phone rather than re-rooting your phone by flashing a CFRoot kernel or using another root method. Just make sure the version of Siyah you're going to flash matches up with the stock rom you've got on (I.E if you flash a GB stock rom use GB Siyah, ICS stock = use ICS Siyah, etc, etc).
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Don't worry about the flash counter. That's the least of your problems while your phone is borked Worry about it when it's fixed. There's nothing you can do about the triangle while your phone is cactus.
When you've got it up & running again, use Triangle Away.
But first things first.
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
You're welcome.
Um, no. Absolutely not. Nothing personal, but if I did that for every person who's asked me for 'hands on' help since I've been here, I'd have spent my time doing nothing else. I don't do 'personal' with people from XDA (which is why I have PM's blocked except for mods).
Besides, you're going to learn much more fixing this yourself. I've given you a stack of information thus far, ball is in your court. Every answer to every question you could possibly ask is on this site. It just sometimes takes a bit of work/reading on your part to find it.
megosu said:
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Click to expand...
Click to collapse
ok I understand.. it is just I have literally spent more than 8 hours on it and had not make any progress at all (even worse I cannot return it to the shop because of the yellow triangle).
I appreciate your help, it gives me a bit of hope but I'm in a very bad situation and I feel I have read and do so much already with no success at all.
I will try your option of restoring the one from Sammobile, I have tried other before without any luck, maybe this one will do... (5min left to DL it).
thanks again for your support
I know where you're coming from. The first flash I tried when I got my phone in 2011 borked because I was careless, and it took me a bit over a day to get the right info/files/etc to get it fixed. I know it's frustrating/tiring/annoying & you're wondering at the start whether you can even fix it. But as long as you've got download mode 99 times out of 100 you can save it.
And as I said, it's good experience; once you've fixed it, you'll be able to handle anything that comes up in future
Let us know how you go. I'm going to bed shortly, but I'm sure someone else will step up & help if you have any further problems.
You're welcome Happy to point you in the right direction.
I have flashed the rom, the exact same one as I had before everything happened...
if it helps, I flashed it from Odin 3.04 as PDA.
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5
I'm now back to the Samsung GALAXY S2 GT-I9100 logo and nothing happens.
I cannot use recovery mode,
I can use DL mode (it shows 11 counts and current binary as Samsung official.)
update:
I left the phone on the first logo for about 5min and it moved to the next Samsung Galaxy S2 logo, with the big animated S.
I'm waiting but nothing else is happening.
I'm still desperate to fix it.
One thing which can be relevant, whenever I try to wipe or format /data from CWM, my phone is restarting after a few minutes or is saying it cannot be done.
I can format /cache and /system.
Could it be the root cause ? Any way of fixing it ?
Thank you
update: I cannot mount /data from CWM, it says Error mounting /data!
is it the brick bug ? :|
Easy now....your device is still good.
Those animations should take like 1-2 mins when you flash a rom.
Now, you are completly sure that you are actually flashing the right ROM for your device model?
If so, just keep flashing stock roms until you're up and running again, so you can start from scrap.
I tried, the issue is as soon as I flash a stock rom (through Odin), then I can't get into stock recovery mode anymore, I have to flash GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar to get back the recovery mode.
I tried to flash several times, I think it is down to the fact I cannot mount or format /data.
Which is why I'm wondering if it is the famous brick bug.
My device is GT-I9100 and I took the stock rom from sammobile:
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is ICS 4.0.4 (that I had before trying to move to CM9.1 and having all this mess in my hands.)
flash this:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/.
you are on siyah kernel right?
what you wanna do know is to get to whatever rom your flashing, forget about cmw for now.
this also might help:
http://forum.xda-developers.com/showthread.php?t=1457458
So it is not lost yet ? Not the brick bug ?
just to be sure:
you want me to install through Odin: Siyah-s2-v5.0.1-CWM.zip
then going back to DL mode
I flash through Odin: I9100XXLSJ_I9100OXXLS1_OXX.zip (coming from your link).
anything I'm missing (even if it seems obvious, please let me know as I'm maybe missing something important)
?
I still cannot do Factory reset... is it a problem ?
I dunno what kernel you are using, If stock 4.0.4 kernel you should flash siyah first (safe kernel, no brick bug), and then countinue flashing the ROM. Check out the brick bug thread in general SII forum for directions if you want.
BTW, Odin recognizes your phone right? Check it out, you'll get a huge long breath.
BTW 2: you don't have any kies applications running in your pc.....am I right? if so, CLOSE THEM ALL!
I did had stock 4.0.4 kernel when I first tried to follow CM9.1 wiki, and I did a factory reset through CWM... which is why I think I might have bricked it...
I have checked the brick bug thread (too late it seems...) but so far I can't be sure if I'm in this case or not as they say they can't even reach DL mode, and I can.
Odin recognizes my phone, yes, but anything I flash is stuck on the animated logo.
I do not have Kies installed, just installed the drivers.
Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).
Hello everyone, First i have to say that i have done everything to my phone and i think i just hard brick it but i really need an Expert Opinion.
Right now i dont know what is the rom i am because everything i flash just fails.... i have trying with different Odin versions, different Roms, differents pc, differents cables, 3 files , 1 file, and i have flashed bootloader, different kernels, i have to say that i have trying everything, also i tried hg42 guide or the guide to flash an unflasheable soft brick phone.
Anyway as i say i think i just broke the logic board .
Ok Hope is the last thing you lost, so the last thing i did was flash a pit file that avoid the brick bug+ dorimax kernel by odin 1.85, in recovery i format everythihng and wipe everything and flash CM 10.1.3, but i dont know what happen with the phone , it just freezee in CWM or in language selection of the rom and after it freeze i have to remove the batery like 10 mins or sometimes 30 min to get the phone working again....
also i have to say that i cannot flash by odin a rom because it just get stuck in factoryfs.
thanks for reading i hope that you can help me out