Related
hi
i updated my phone by many many ways now device can not recognize any memory not internal and not external .
i checked everything i used terminal i changed Rom and Kernel. now 4.1.2 kernels wont work on my phone and 4.2.2 kernels cannot recognize Any memory. when i connect USB device is not recognize on PC but when i connect as mass storage just my sd card is working.
alos you must know that i use PIT file with odin 3.07 to re-partition and everytime i install new ROM , i Wiped all cach and Factory /Data
also emmc cannot mount (i'm thinking it's not there anymore)
right now i am using Supernexus 2 and Philz kernel
PLZ help me.
Deja vu?
"To err is human, to forgive is divine"
Sent from my SGS II
FIX it
hi all
i found my problem i have two files that can fix this
use this with ODIN
1-unrar it
2-use pit as your device is (16 or 32)
click start and wait to restart your phone
So you repartition on every flash?
sh*t just got real.
Sent from the little guy
gastonw said:
So you repartition on every flash?
sh*t just got real.
Sent from the little guy
Click to expand...
Click to collapse
not everytime but sometimes ROMs re-partition our memory and that cause this problem i had so i use this.
believe me i did everything to fix that even from terminal. nothing worked so i found this and used it and worked. and now i suggest everyone that have this problem use this as their last hopr.
FarshadFallah said:
not everytime but sometimes ROMs re-partition our memory and that cause this problem i had so i use this.
believe me i did everything to fix that even from terminal. nothing worked so i found this and used it and worked. and now i suggest everyone that have this problem use this as their last hopr.
Click to expand...
Click to collapse
Hmm.. thanks for the info.
Please add [SOLVED] to the title of ur post, so that others with this same problem can get help too.
"To err is human, to forgive is divine"
Sent from my SGS II
Hello everybody!
Recently I've got used Galaxy S2 (GT-I9100) from ebay. I'd like to update it from GB to JB. Found lots of great information on this forum an in the net, but still not sure if I understand the procedure right.
Some information about current system:
- rooted by previous owner, no idea how exactly.
from "About":
- Android version: 2.3.6
- Baseband: I9100XXKI3
- Kernel: 2.6.35.7-I9100XWKK5-CL754841 [email protected] #2
- Build number: GINGERBREAD.XWKK5
*#1234#:
- PDA: I9100XWKK5
- PHONE: I9100XXKI3
- CSC: Unknown
eMMC check:
- Type: VYL00M
- FwRev: 0x19
- Brick Bug: YES, insane chip
I'm using linux, so Heimdall is a way to go. I downloaded current PIT file from device, XWLSE firmware from Sammobile (includes boot.bin and factoryfs.img only), and PhilZ kernel for this firmware.
Now, if I understand it right, I have to do the following:
1. backup
2. Restart in Download mode
3. Detect device in Heimdall-frontend
4. Choose PIT file I downloaded from device before
5. Choose partition files
6. Flash
At the step 5 I have the problem: boot.img should be the BOOT partition. Different sources say also IBL+PBL, or SBL. However, I have only SBL1, SBL2 in the list.
So, I have following questions, aswers to which I couldn'd find:
1. Do miss something?
2. Why CSC is unknown? is it okay?
3. What is a right Partition Name for boot.bin? Is it OK to call it SBL1 (probably not)
4. If not, what can I do? Can I use different PIT? From where?
5. Is it safe to repartition? (brick bug)
6. If I repartition, do I need images for all partitions?
7. Why Sammobile firmware doesn't include kernel?
I'd be happy to get some answers, or links to relevant information. Meanwhile, reading the forums.
Thanks in advance for any help!
Since u are rooted already, flash using Mobile Odin. Trust me, much safer than Odin/Heimdall.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
AntonGut said:
1. Do miss something?
2. Why CSC is unknown? is it okay?
3. What is a right Partition Name for boot.bin? Is it OK to call it SBL1 (probably not)
4. If not, what can I do? Can I use different PIT? From where?
5. Is it safe to repartition? (brick bug)
6. If I repartition, do I need images for all partitions?
7. Why Sammobile firmware doesn't include kernel?
Click to expand...
Click to collapse
As for ur questions:
I have personally never used Heimdall, and so I can't answer questions related to it.
Sammobile firmwares do contain kernels (named zImage I guess).
Brickbug affects only 4.0.4 firmwares. U are safe on 2.3.6.
I have heard using PIT files with Odin is a last resort (like when u cannot flash normally), but I don't know if that applies to Heimdall also.
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Since u are rooted already, flash using Mobile Odin. Trust me, much safer than Odin/Heimdall.
Click to expand...
Click to collapse
Thanks, will look into it.
immortalneo said:
Sammobile firmwares do contain kernels (named zImage I guess).
Click to expand...
Click to collapse
I have three XWLSE with different CSC, one XWLSD and XWLSN from sammobile. All unpacked, none contains kernel (no zImage). All have boot.bin and factoryfs.img, XWLSD also has cache.img. That's all. Not a big issue IMO, since kernels are available separately. Just currious, why is it so, would those firmwares work with older kernel, and which ones do contain kernel.
immortalneo said:
I have heard using PIT files with Odin is a last resort (like when u cannot flash normally), but I don't know if that applies to Heimdall also.
Click to expand...
Click to collapse
It seems, in Heimdall PIT is required. You don't have to repartition though, there is separate checkbox for it. Heimdall doesn't accept .tar.md5 package, but wants to have pratition images separately. If I understand it right, it looks in PIT what partitions are needed, and which image goes where. So I unpacked firmware, downloaded existing PIT, and tried to use it. However, it doesn't have anything called "boot" or "IBL+PBL", but SBL1, SBL2 and some others. That's where I stuck.
Thanks for the info on Heimdall.:thumbup:
On flashing stock firmwares, my custom kernel gets replaced by a stock one. So am sure there must be a kernel in a stock firmware.
Sorry I couldn't be of much help..
"To err is human, to forgive is divine"
Sent from my SGS II
All right, then I have to learn more about contents of firmware and its packaging
Thanks for your input, hope it'll lead me to right solution.
AntonGut said:
All right, then I have to learn more about contents of firmware and its packaging
Thanks for your input, hope it'll lead me to right solution.
Click to expand...
Click to collapse
Please share what u learn here..
And do let us know if u solve ur issue.
"To err is human, to forgive is divine"
Sent from my SGS II
Just a short update. I'm still getting courage to actually flash something on device. Just prefer to understand what I'm doing.
Here is a quite detailled guide for using Heimdall, which confirms that I understood it right in earlier posts. It just didn't mention pit-download function, and suggests to repartition, which is not a good idea according to some.
As for partition purposes, names etc, I'm still quite confused.
This thread explains, that BOOT, RECOVERY, and KERNEL partitions are basically the same, and include actual kernel and initramfs image. This kind of answers the question, where did they hide kernel in sammobile-firmware. It is also mentioned there, that "recovery" is an exact copy of "kernel". However in pit-file from my device they have different size.
Anoter problem/question is why there is boot.bin file in firmware, if partition is zero-size? (as is the case in thread mentioned above). Can it be flashed in kernel-partition? Or in SBL, as per recommendations from this guide? Did partitioning scheme change sometime between GB and JB? How does (mobile) odin handle this?
immortalneo said:
On flashing stock firmwares, my custom kernel gets replaced by a stock one. So am sure there must be a kernel in a stock firmware.
Click to expand...
Click to collapse
Is it correct, that you use sammobile firmware with mobileOdin?
I just tried opening sammobile-XWLSE with it. According to mobileOdin manual, when opening a file it finds all partitions inside it, and puts the filename next to partition names. However, I see it only finding "System" partition. "Kernel" says "None". How does it look on your device?
Screwed it up...
Finally I got courage to flash anything. Used MobileOdin, firmware from sammobile (from which only factoryfs got loaded), and PhilZ kernel.
Program reported success, but devise didn't want to start afterwards. It showed "Samsung Galaxy GT-I9100" with yellow triangle, then short pause, same again. Then PhilZ recovery menu. Reboot, shutdiwn and start again ended up in recovery each time.
I had CWM-backup from original system. Tried to restore factoryfs from this one. Seemingly succeed, but nothing starts anyways. Now not even recovery. Still available via button combination though, as well as download mode.
It would be really great if somebody can give a hint how to get this thing into working state again...
If you can get into recovery, and ur not on 4.0.4, do a factory reset and wipe cache partition.
If you can only get into Download mode, flash a stock firmware via Odin.
"To err is human, to forgive is divine"
Sent from my SGS II
What I actually did was to completely restore from CWM backup. Apparently first time i only restored system partition, and it wasn't enough. Complete restore returned my old system. I'm glad it worked.
As for your suggestion with Odin: like I say, I don't have access to windows. On the other hand "to flash the stock firmware" is what I'm trying to do from the very beginning, and can't manage so far.
Okay, finally got it up and running.
The major problem was that my archive-decompresser got only part of .tar.md5 out of sammobile-zip. No idea why. As a result I saw only some of the actual firmware contents, not all of them. So disregard my questions about "why is there no kernel inside". It's all there.
I don't understand, how those .tar.md5 passed checksum-check in mobileOdin.
After I got that sorted there were some others, but everything worked fine after some tries. For one, I could not use mobile Odin anymore, and heimdall-frontend gave errors. Console version worked fine.
Thanks for your help!
No wonder the kernel went missing!
Thanks for sharing mate! Happy you got it sorted out!
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
I updated my Galaxy S2 GT-I9100 to Jelly Bean via Kies. It worked fine for 10 days and yesterday night when I was switching Wi-Fi off, it hanged. So I pulled off the battery and after that it got stuck on boot screen. I am able to get in to download mode but not to recovery mode. I flashed the phone with Official JB rom available at sam mobiles using Odin but the problem still persists. Can someone help me in reviving my phone
Had u done factory reset after flashing the update?
Since u have download mode only, ur only option would be to flash a stock firmware via odin.
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Had u done factory reset after flashing the update?
Since u have download mode only, ur only option would be to flash a stock firmware via odin.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
When I updated for first time using Kies, i didn't. After flashing via Odin, I can't factory reset as it's not going to recovery mode. I used stock firmware available at Sam mobiles only to flash. Please guide me what to do next?
konquerror said:
When I updated for first time using Kies, i didn't. After flashing via Odin, I can't factory reset as it's not going to recovery mode. I used stock firmware available at Sam mobiles only to flash. Please guide me what to do next?
Click to expand...
Click to collapse
Sorry, read ur first post really fast. Didn't notice that u already flashed stock JB!
If u can't get recovery mode, flash a stock ICS 4.0.3 firmware. Then, get into recovery and factory reset. That should help u boot.
Once you do that, you can either flash JB using odin again, or u can root the ICS and use Mobile Odin app to flash JB.
"To err is human, to forgive is divine"
Sent from my SGS II
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Sent from my GT-I9100 using xda premium
immortalneo said:
Sorry, read ur first post really fast. Didn't notice that u already flashed stock JB!
If u can't get recovery mode, flash a stock ICS 4.0.3 firmware. Then, get into recovery and factory reset. That should help u boot.
Once you do that, you can either flash JB using odin again, or u can root the ICS and use Mobile Odin app to flash JB.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Thanks I will try that. However I searched the forum and according to this thread:
http://forum.xda-developers.com/showthread.php?t=1457458
I might have NAND rw corruption. This guide doesn't have instructions for Jelly Bean. Can you guide me how to recover a possible JB SGS2 with NAND rw corruption?
stopro said:
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Can you please point me to correct rooted JB kernel and instructions for the same?
stopro said:
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Click to expand...
Click to collapse
Or that..
(Now why didn't I think of that!)
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
konquerror;40315112according to this thread:
[url said:
http://forum.xda-developers.com/showthread.php?t=1457458[/url]
I might have NAND rw corruption.
Click to expand...
Click to collapse
Its too early to say that mate. If all other attempts fail, we will try that guide.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
konquerror said:
Can you please point me to correct rooted JB kernel and instructions for the same?
Click to expand...
Click to collapse
Download Siyah v6 beta 5 (tar file) from www.gokhanmoral.com and flash it via Odin (select it as PDA).
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Or that..
(Now why didn't I think of that!)
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Its too early to say that mate. If all other attempts fail, we will try that guide.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
Download Siyah v6 beta 5 (tar file) from gokhanmoral and flash it via Odin (select it as PDA).
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Thanks a lot. Will try and let you know the result
After flashing with Siyah Kernel, I was able to go in to recovery mode. I did a factory reset and wiped the cache after which my phone started working fine. Thanks a lot people for your help.
konquerror said:
After flashing with Siyah Kernel, I was able to go in to recovery mode. I did a factory reset and wiped the cache after which my phone started working fine. Thanks a lot people for your help.
Click to expand...
Click to collapse
Ur welcome! Thanks should go to @stopro though!
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
s2 stuck on startup screen
I got my galaxy s2 in january prepaid thru walmart straighttalk. Yesterday it got stuck on startup screen. The reset option will not work...is there anything else I can do? Thanx
Aphrodite
Wot rom u r on
Sent from my GT-I9100 using xda premium
Just quickly, if you got it on January, are you still under warranty? If you are, save yourself some trouble and take it back under warranty, assuming you've never messed with (rooted etc) your phone? There's things to try but warranty is there for a reason.
Sent from a galaxy far, far away
Had the same problem, seemed like a NAND corruption to me on my phone since the progress bar on the main boot logo screen was slow and was stuck half the way, which otherwise used to slide pretty quickly, indicating that the phone is having trouble reading from its NAND flash.
Before the corruption I was running RootboX 4.1 with Dorimanx Kernel 9.38.
Was all prepared to do the ODIN flashing with latest firmware for my country, kernel and possibly a PIT flash with repartition , if in case else would have failed.
However to my skeptic mind a pretty safe suggestion read here somewhere on a thread, appealed for a while, and I was amazed to see the power of hunches.
Someone reported to have restored back his set, by SIMPLY taking the battery out and leaving it naked overnight. I did the same thing last night, and guess what, sipping the morning tea, I inserted the battery again and VOILA, its ALIVE....its ALIVE.....like any other FRANKENSTEIN defying all boundaries of logic.
So someone else in the same fix, should try it at first before jumping in the ODIN waters.
Lets see for how long does it lives, which TOUCHWOOD should be for a long time, till i save enough to a buy the S4 or Note3.
Cheers.
S2 stuck at boot screen. need some help
Hello everybody,
I'm new here and came here because of a problem with my Samsung S2.
Never rooted, original updates with KIES, android 4.1.2
Two days ago i woke up and the s2 was off and didn't restart. At first it was in a splash screen loop and i could get in recovery mode tried the factory reset but it got stuck in there to... After waiting for about an hour i pulled out the battery to restart it but then it didn't get any further than the boot screen. Couldn't get into recovery mode but could get into download mode. Searched the android forums for hours and came across this post. followed several possible solutions but now i'm stuck again, nothing did the trick... Hope you guys are willing and able to help me solve this thing.
What have i done so far:
Downloaded the original firmware for my device: I9100XWLSW_I9100XXMS3_I9100ITVLS2_HOME.tar
Downloaded ODIN v3.07
Updated KIES and after restarting pc stopped all the kies processes.
Started Odin without cable connected to the S2, selected the firmware, got the S2 into download mode, connected S2 to the Pc.
Odin recognizes the comport pressed start and can see that Odin gets stuck at NAND write start!!. first it says boot in white and after about 5min got the red fail.
Tried it different times with the same result.
Went on reading this tread and cam across the possible solution to firs flash kernel (in my case i've used Siyah-s2-v6.0b5.tar), go to recovery mode, factory reset and wipe and then flash original firmware again.
Same problem ODIN gets stuck at NAND write start!!
Detail: on the S2 during all this i''ve never seen a progress bar or any other movement, However although every attempt failed, when i go in to download mode now it says
Custom binary download: yes (2 counts) -my attempts to flash kernel with Siyah-s2-v6.0b5.tar
Current binary:custom
And at the boot screen i get the yellow triangle...
I'm stuck! :silly:
Any help would be very much appreciated!
Made some screenshots:
So because this is my first post they are attached to this post.
You've been pretty thorough so far. Search for Hopper 8's 'Odin troubleshooting' thread, try all the stuff in the thread, particularly flashing the 3 part firmware. That's the only way you're fixing it yourself. Could be NAND corruption, but most of these cases are fixed by perseverance (for example, the first 7 times you try flashing stock firmware it doesn't work, but the 8th flash does for whatever reason), sometimes it's something really small/obvious tripping you up that can be a bit hard to figure out if you've trying to fix it for hours/days. Hopper's thread should enable you to try everything you possibly can to fix it.
MistahBungle said:
You've been pretty thorough so far. Search for Hopper 8's 'Odin troubleshooting' thread, try all the stuff in the thread, particularly flashing the 3 part firmware. That's the only way you're fixing it yourself. Could be NAND corruption, but most of these cases are fixed by perseverance (for example, the first 7 times you try flashing stock firmware it doesn't work, but the 8th flash does for whatever reason), sometimes it's something really small/obvious tripping you up that can be a bit hard to figure out if you've trying to fix it for hours/days. Hopper's thread should enable you to try everything you possibly can to fix it.
Click to expand...
Click to collapse
Thanks MistahBungle... I'll go and try that... I'll reply here if it worked.
http://forum.xda-developers.com/showthread.php?t=2345831. If it doesn't, it's a motherboard replacement job. I very much recommend you flash as many stock firmwares you can download (10, 20, whatever), because the alternative is expensive/means getting a new phone.
Hi, i have a really bad situation here.
so my phone needs its firmware flashed as it no longer will boot in either recovery mode or boot in general.
so i have to correct firmware open in odin and my phone in download mode but the firmware flashing failed.
the error was "Can't open the serial(COM) port."
im unsure if it has anything to do with the fact that my phone is not in usb debugging mode although i thought that the downloading mode bypassed that?
i would really like to save my data on my phone (pictures and such) so if anyone has a way i can either flash my firmware or retrieve my data that would be wonderful.
There is a picture of my attempt at flashing my firmware attached. (i think)
and here is the firmware i used (not a link to a download): firmwaredown.blogspot.com.au/2012/04/i9100tdvlp4-android-403-ics-australia.html
Do you have the correct drivers installed? Make sure Kies isn't running in the background, try different USB ports and download Odin v1.85 (most stable version).
Sent from my GT-I9100 using xda app-developers app
themadba said:
Do you have the correct drivers installed? Make sure Kies isn't running in the background, try different USB ports and download Odin v1.85 (most stable version).
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
i am just trying odin 1.85 now. thankyou!!
themadba said:
Do you have the correct drivers installed? Make sure Kies isn't running in the background, try different USB ports and download Odin v1.85 (most stable version).
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
so it has been stuck on this screen for a while now, should i be worried?
thatsrightbru said:
so it has been stuck on this screen for a while now, should i be worried?
Click to expand...
Click to collapse
yeah it is not changing :/
thatsrightbru said:
so it has been stuck on this screen for a while now, should i be worried?
Click to expand...
Click to collapse
Worried? Hmm.. A little.
Before I suggest anything, tell us how u messed up ur phone.
How did it get bricked?
What firmware are you on now?
Are you rooted?
As for the problem u have now, its called a NAND corruption. It may or may not be fixable.
Try these steps (all of them) first and see if you can successfully flash a rom:
http://forum.xda-developers.com/showpost.php?p=25731280&postcount=4
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Worried? Hmm.. A little.
Before I suggest anything, tell us how u messed up ur phone.
How did it get bricked?
What firmware are you on now?
Are you rooted?
As for the problem u have now, its called a NAND corruption. It may or may not be fixable.
Try these steps (all of them) first and see if you can successfully flash a rom:
http://forum.xda-developers.com/showpost.php?p=25731280&postcount=4
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
okay immortal. tried all of that list with no improvement.
the firmware im running is the stock GT-19100T for australia.
i havnt fiddled or touched it in anyway.
as to how it bricked im unsure, yesterday my apps stopped working (like couldnt open them) and so i restarted only to get stuck on the screen that says "samsung galaxy s II GT-19100T"
ahhh anything i missed?
p.s. i might be going to sleep soonish so if i dont reply soon thats why.
and i realllllyyy appreciate your help!!
Keep trying a few more times. There must be something u haven't tried yet.
Also try flashing another firmware.
Once Odin flash succeeds, let us know.
If you can't get it to flash after a lot of trying, ur NAND could be borked. Take it to a service centre then.
"To err is human, to forgive is divine"
Sent from my SGS II
thatsrightbru said:
okay immortal. tried all of that list with no improvement.
the firmware im running is the stock GT-19100T for australia.
i havnt fiddled or touched it in anyway.
as to how it bricked im unsure, yesterday my apps stopped working (like couldnt open them) and so i restarted only to get stuck on the screen that says "samsung galaxy s II GT-19100T"
ahhh anything i missed?
p.s. i might be going to sleep soonish so if i dont reply soon thats why.
and i realllllyyy appreciate your help!!
Click to expand...
Click to collapse
Only thing I can suggest it to download a stock ROM for your region from sammobile.com (sign up required - 5 mins) then select i9100T etc and then get the latest ROM for your region, if you can compare the md5 checksum then do this. If they match, stick your phone in download mode (you can still do this yes?) and pray that it goes well.
But before you should do this, wait and see if anyone shouts at me for suggesting this since you may have NAND corruption and it would be a bad idea! You never know...
Edit: well according to post above, you can continue to flash away, so try a few different ROM's, try to compare the md5 checksums for errors during downloading, and hope.
Sent from my GT-I9100 using xda app-developers app
themadba said:
Only thing I can suggest it to download a stock ROM for your region from sammobile.com (sign up required - 5 mins) then select i9100T etc and then get the latest ROM for your region, if you can compare the md5 checksum then do this. If they match, stick your phone in download mode (you can still do this yes?) and pray that it goes well.
But before you should do this, wait and see if anyone shouts at me for suggesting this since you may have NAND corruption and it would be a bad idea! You never know...
Edit: well according to post above, you can continue to flash away, so try a few different ROM's, try to compare the md5 checksums for errors during downloading, and hope.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
okay, you guys are amazing!
thanks heaps!
ill check back after a good sleep and see if that helps as well :S
i do fear that it will end up a costly adventure for me
immortalneo said:
Keep trying a few more times. There must be something u haven't tried yet.
Also try flashing another firmware.
Once Odin flash succeeds, let us know.
If you can't get it to flash after a lot of trying, ur NAND could be borked. Take it to a service centre then.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
i think my nand is borked
which sucks!
As Gaston & I were saying last week, in these instances, it's either a case of something really simple being missed/not being done (people not trying all the things suggested/saying they have but they haven't, etc) which is more likely, or the phone is genuinely borked, which is less likely (Tho it does happen).
Unless you've left something out (about what's happened to the phone, what you have/haven't done with & to it), it makes no sense for it to be 'borked' given what you've told us. I suggest you keep trying, and try with as many different PC's as you can get access to (and try all the troubleshooting steps you've been given on each PC if necessary).
thatsrightbru said:
i think my nand is borked
which sucks!
Click to expand...
Click to collapse
do u have ur phone in warranty ?
thatsrightbru said:
i think my nand is borked
which sucks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1457458 Or JTAG !
What's all this jtag frenzee?
Please read more about this method before you keep suggesting it.
Soon people will start throwing it to solve bootloops and we'll have a big brick-o-rama.
Sent from the little guy
N00bs trying to JTAG. Can't wait to see that start happening. Seriously, if someone is incapable of doing something as simple as flash a phone, you really think they're going to be able to JTAG without permanently damaging the phone beyond repair ?
Please.
The advice should be 'Take it to someone who knows what they're doing'.
Lol they must be mistaking "riffbox" for "magic box", the box that solves it all.
Sent from the little guy
My mum sold her S2 on eBay yesterday. On a previous occasion I had rooted it for her, so to reset it back I used stock (Orange) firmware from SamMobile. I followed this guide to unroot and reset it for the buyer, however, when I hit start in ODIN, it tried to set up the connection, but then stopped and said 'FAIL!'. When trying to turn it on it says to plug into Kies and hit restore. Should I do this, or is there another option?
Many thanks in advance
You need to keep trying the Odin flash; search for Hopper8's 'Odin troubleshooting' thread if you're unable to do a successful one. Stuff to try in that thread should enable you to get it done.
MistahBungle said:
You need to keep trying the Odin flash; search for Hopper8's 'Odin troubleshooting' thread if you're unable to do a successful one. Stuff to try in that thread should enable you to get it done.
Click to expand...
Click to collapse
Ok. Just to check, it it the CORE file that goes in the PDA field?
CORE file ?? What SGS2 variant do you have ? Normally with Samfirmware you'll end up with a zip file that contains a .tar.md5 file that you flash in the PDA section of Odin, an a .dll file which you discard.
MistahBungle said:
CORE file ?? What SGS2 variant do you have ? Normally with Samfirmware you'll end up with a zip file that contains a .tar.md5 file that you flash in the PDA section of Odin, an a .dll file which you discard.
Click to expand...
Click to collapse
UK Orange. It included 3 TAR.MD5 files, as said in the tutorial. It seems to be working now, anyhow!
Then do add SOLVED to the title of your post.
"To err is human, to forgive is divine."
Sent from my SGS II