Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<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> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg
Related
So, I tried to root my phone, following Chainfire's guide. I did everything EXACTLY as I was supposed to, but after flashing the kernel in Odin, with XWKDD_insecure.tar, the device no longer worked. It rebooted into a screen with a grey battery and the loading loop, but nothing happened. I didn't even get a chance to use SuperOneClick, because the program just stalled when it said "Waiting for device...". After about 5 minutes, I held down the power button, and then the GS2 logo appeared with a yellow exclamation sign underneath it. And SuperOneClick still didn't register the phone.
I pulled the battery out, booted into download mode again, then tried to install the factory firmware I downloaded from samfirmware.com. But then this happened:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKDJ_REV_02_CL996627.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXXKDD.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
<ID:0/004> data.img
<ID:0/004> cache.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
When I saw it, I actually felt physically ill.
So what do I do now? I have a choice of booting into download mode, or turning the phone on normally, and getting a screen that says the update fail to load. Is there something else I can do to reset factory settings, or is that the end of my brand new phone
U could still try to reflash the rom again, check if the file u downloaded is not corupted.
You have to bear in mind that Odin can be temperamental, redownload a firmware and flash it again.
Going off memory here as im not at my pc but it looks like you have too many things in to your odin program.
first thing i notice is that you have the "Re-Partition" box selected, it was my understanding you only need Auto Reboot and F.Reset Time checked.
You could also try getting the most upto date version of Odin too which is v1.85.
Also you have entered something in to the PIT section, when i flashed my device with the firmwear from samfirmware (I9100XWKDF) i didnt put anything in the PIT section.
Maybe try changing them and i hope it works.
Crucio
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Looks like you get first to brick an SGS 2 prize any way .
jje
Not a prize i would like to win heh..
Lets just hope it can be flashed again.
moparman said:
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Click to expand...
Click to collapse
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
im a rookie to
I just read the instructions to root...
Maybe it works if repartition is not checked and reflash?
I hope someone with better skills then me can help.
If i had done this i wouöd die of a broken hearth
I remember how afraid i was to flash my TyTn2 the first time..And i didnt have any problem
yeah im a rookie also, lets hope someone with a bit for knowledge can help this guy out if we havent ^^
my heart would sick too, it did a bit when i flashed the firmware and it was german that was fixed easy tho lol.
The repartition basicly changest the size of some system partitions based od the PIT file, its not recomended to use the repartition, but that shouldnt be the problem why the ODIN failed.
As he said he is able to go to download mode so he should be safe, just reflash the rom or try other rom versions and flash them.
Crucio_ said:
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
Click to expand...
Click to collapse
The screenshot I posted was from after the damage was done. I had already given up on trying to root my phone, and was trying to install the firmware from SamFirmware, in the hope that it would get my device back to factory settings.
Initially, when I flashed the kernel with Odin, nothing was selected except for "Auto reboot" and "F. Reset Time", and the only file loaded was the XWKDD_insecure.tar on the PDA line. I was also using Odin3 v1.85 at the time. The firmware I downloaded from SamFirware came with v1.83 and I didn't even notice that it wasn't the latest version.
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
rheedan said:
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
Click to expand...
Click to collapse
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
bilboa1 said:
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
Click to expand...
Click to collapse
I don't know if I should be comforted by the fact that I tried to do the right thing, or disheartened by the fact that doing the right thing didn't solve my problem.
Is there perhaps another way to go about the whole process? Should I try another ROM? The one I used was a European XWKDF Gingerbread 2.3.3, but I also have the Russian XEKDB firmware from http://forum.xda-developers.com/showthread.php?t=1057535 - I think it's 2.1.1.
there is not much experience with the SGS2 yet and I don't have one yet personally. Never saw that one error but form the SGS1 experience i'd say try reflashing, and try flashing other SGS2 firmwares ;-)
i havnt flashed mine yet but will wait till i get insurance for the phone because (and i mention this so that people can do the same thing if they wish).. if it does brick then the option of it "accidentally falling onto a busy motorway" is open to me lol
OK, looking at your screenshot, you flashed too many files, and reformated.
Follow this guide.
http://androidadvices.com/how-to-up...ii-i9100-to-gingerbread-xwkdd-2-3-3-firmware/
Make sure you download the files from there as well. I have flashed mine with them after I broke a few things playing, and it worked fine after.
This will get you up and running again.
Then for Root, go to this thread
http://forum.xda-developers.com/showthread.php?t=1056334
Download the XWKDD_insecure.tar file
Odin, Without repartion checked.
Only files to link are the pit file, in pit and XWKDD_insecure.tar in PDA
Then you can use SuperOneClick to add root.
Don't panic, I doubt its a brick.
Good luck
Broomfundel said:
Don't panic, I doubt its a brick.
Click to expand...
Click to collapse
It is fairly hard to brick a Samsung properly, without actually trying... Hope that's some reassurance.
The fact you can get into download mode is a reassurance, as that should be the key. I've not owned a Samsung device, so I won't try and advise how to fix it, but I'd agree about trying that above link to install the "beta" firmware.
ODIN is pretty good, but there isn't much experience in flashing these yet, as I don't know of any devs with them. I might go out at the weekend and get one, but I'll not be starting properly on it until June realistically...
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
dhruvmalik said:
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
Click to expand...
Click to collapse
now i will never root my s2 when i will get it, faced the same sitution with my n8 once
Gave my phone to a friend to root but he was unsuccessful with it so before it gets screwed up anymore thought I would try it. My Aria was really easy this one is a bit different.
My desktop won't run S2 says it is for galaxy S2 only.. Windows 7 64 bit. My laptop is windows 7 32 bit, it says the device is not plugged in. I installed SAMSUNG_USB_Driver_for_Mobile_Phones_V1.4.2.2 on the laptop but not sure if I need further drivers aside from Kies. I tried another kernel and now my laptop says the same thing as the desktop does.. S2 root application is for Samsung Galaxy S2 devices only.
Secondly the kernel he installed the phone doesn't like it so I can't make calls on it or do anything with it. I can still boot it into download mode but since he didnt take note of the original kernel that was on the phone it is making it difficult to backtrack. What should I do at this point? Keep trying another kernel till I find one that works or be best to just put the phone back (which may be hard since its unknown what kernel was on it)
Thanks
just re-flash your original firmware and yourll get your kernel back.
check here for firmwares
http://forum.xda-developers.com/showthread.php?t=1075278
or here for operater based ones
http://forum.xda-developers.com/showthread.php?t=1113928
root kernels
http://forum.xda-developers.com/showthread.php?t=1103399
Ok im not 100% sure i got your problem, but if you are able to enter download mode, cant' you just flash with odin, the lite'ning rom 6.1? This will already include the root and a stable custom kh3 (i started with this one as my first custom rom)
(be sure to reinstall Kies to put fresh drivers on your pc before, but also be sure to kill kies (not have it active in background) or it will block odin).
Rooting the S2 is very easy, you only need to put the cf-root kernel in the pda section of odin, doublecheck to NOT have "repartition" option active, and press start.
The S2root application is an alternative method that works, but requires more steps.
rembrandtlnx said:
Ok im not 100% sure i got your problem, but if you are able to enter download mode, cant' you just flash with odin, the lite'ning rom 6.1? This will already include the root and a stable custom kh3 (i started with this one as my first custom rom)
(be sure to reinstall Kies to put fresh drivers on your pc before, but also be sure to kill kies (not have it active in background) or it will block odin).
Rooting the S2 is very easy, you only need to put the cf-root kernel in the pda section of odin, doublecheck to NOT have "repartition" option active, and press start.
The S2root application is an alternative method that works, but requires more steps.
Click to expand...
Click to collapse
I can try, downloading it now and we'll see how it goes.
The firmware is not available on Samsungs site so Id have to find it else where is my guess.
greyclear said:
I can try, downloading it now and we'll see how it goes.
The firmware is not available on Samsungs site so Id have to find it else where is my guess.
Click to expand...
Click to collapse
you can find all the firmwares (original) in the "original SII android development" http://forum.xda-developers.com/showthread.php?t=1075278
Also if you want to try flash the lite'ning instead the original one , you can find the rom in the "S II android developement" of this forum http://forum.xda-developers.com/showthread.php?t=1095274
trying the lite'ing taking a while though so going to let it run. Ill update if any of this works or doesnt lol Thanks for the help
still loading, not sure if its stuck or what..give it another hour maybe it usually take this long?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> modem.bin
It should usually take like 10-20 seconds..
Sent from my GT-I9100 using xda premium
Kinda figured as much was over 200 meg download so I expected it to take a little longer. Should I pull out the battery and try again?
this thread should get you bk to stcck
http://forum.xda-developers.com/showthread.php?t=1075278
this thread for root after.
http://forum.xda-developers.com/showthread.php?t=1103399
superhappyfuntimes
looks like you have kies running in background and blocking odin. Check That kies is not active in the System tray.
Also use Odin 1.83, you can find it in the original firmware thread i linked above.
Sent from my GT-I9100 using Tapatalk
yes was running in the background i closed it but no difference just sits there for a long time. i have odin 1.83. even kies doesnt see my phone
on stock firmware i didnt see anything for north america, just use a generic one?
well getting somewhere.. maybe. lite'ing took but when it boots I get all sorts of errors saying force close and if I try to bring up the download mode I get the recovery mode instead that I guess is built into the ROM but nothing fuctions there all I can do is scroll through options.
guess i have to take the phone back to the store odin doesnt even see the phone anymore neither does kies and the recovery section doesnt let me do anything I just get a triangle with an exclaimation point so I couldnt run any thing from SD card if i wanted to. What would I expect to hear from the store they going to charge me alot to repair it?
they took it back lol
greyclear said:
they took it back lol
Click to expand...
Click to collapse
What did they say?
Sent from my GT-I9003 using xda premium
They actually offered to root it for me LOL. They said it would void the warranty but I had it barely 24 hours and I told them a friend was trying to put a custom rom on it. I wasn't going to lie, it was a $200 phone I wasn't about to keep it if it didnt work anymore so I actually expected to be out just $200 bucks and cancel the phone contract as I just signed up with sprint, moved from ATT. Either way I didnt expect that outcome
greyclear said:
They actually offered to root it for me LOL. They said it would void the warranty but I had it barely 24 hours and I told them a friend was trying to put a custom rom on it. I wasn't going to lie, it was a $200 phone I wasn't about to keep it if it didnt work anymore so I actually expected to be out just $200 bucks and cancel the phone contract as I just signed up with sprint, moved from ATT. Either way I didnt expect that outcome
Click to expand...
Click to collapse
Lucky
Keep us informed if they fixed the problem or not ^^
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?
Hi
I am in a serious trouble.
I am having a Samsung Galaxy S2 GT-I9100G
Its running on Stock Rom JB v4.1.2
I wanted to update it to Kitkat 4.4.2 by CyanogenMod 11 Custom Rom.
In order to do that i have rooted my phone using VRoot.
Installed CWM Recovery 6.0.1.2
Copied the ROM files and Gapps to SD Card.
Done all the prerequisite and started installing the ROM.
Then the installation failed showing Error Status 7.
Upon googling about status 7 i got to know that the CWM Recovery 6.0.1.2 which i used doesn't support for
installing CM11.
Then i searched for the latest CWM Recovery and got to know about the Philz CWM Touch Recovery 6.0.4.5
I also got to know that in order to install Philz CWM Touch Recovery 6.0.4.5 you need to have a PC with Odin
v3.09 installed to flash this latest CWM Recovery.
Then i downloaded philz_touch_6.19.3-i9100g.tar.md5.
Installed Odin v3.09 in my PC.
Gone into Download mode by pressing Home + Volume Down + Power Button then warning screen came up then by
pressing volume up i came into download mode.
Then i connected my device to PC using USB cable. I got the added message. I also got the COM Port number.
But instead of Yellow as said in the tutorial i got Light Blue Color which i ignored. I thought the Odin
software might had made any changes to their software.
I clicked the AP button and selected the TAR file downloaded then clicked the START button.
Again failed. I don't know why that happened.
I removed the USB cable and reinserted then done the same. Then some message came and process is going on...
waited for 20 mins till nothing was happening.
Fed up of all the process i removed the USB cable thinking of forgetting Kitkat and use the stock rom.
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Please help me in recovering my phone to Stock ROM or Custom ROM.
Last hope is jig. It force download mode when.you cant by pressing buttons. If this doesnt help i think that your phone is now a clip for paper. In odin you should choose pda and after that choose kernel. I never had blue sign in odin but i had i9100. You should from the beghinig try philz kernel to root amd get cwm recovery. So as i sad you must try jig usb very cheap thing or you can do it by yourself. Maybe you should either try kies and kies recovery firmware.
Wysłane z mojego D5503 przy użyciu Tapatalka
adithyagem said:
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Click to expand...
Click to collapse
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Newer versions of Odin have blue in the ID:COM field.
Done as said by you
Hopper8 said:
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Click to expand...
Click to collapse
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
adithyagem said:
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
Click to expand...
Click to collapse
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
The ability of people to read & comprehend the help they've been given here & then actually do what's been suggested seems to get worse & worse as time goes by.
Give some very specific advice (step by step stuff, or refer them to step by step stuff), they go do something completely different. I mean, if that's going to happen, why bother asking for help in the first place ?
@MistahBungle, read the edit on my previous post (if you haven't seen it already). Do you agree the only chance is a stock ROM? I don't know, I don't see many this stuffed up very often.
Edit: Unless, there is a Philz for i9100g. But I can't find an XDA thread for it just by having a cursory glance.
Yep. Flashing a stock rom & praying is pretty much the only option. Classic case of 'attempting to do without learning'. Imagine how much **** these people would be in if the half dozen of us or so who post most of the useful help here decided to move on ?
I did find Philz for i9100g, but it's ages old (newest one I could find was 6.19.3, think Philz is up to 6.30.something). There's also no xda thread for it, so I'm tipping that the i9100 version has been flashed. Still not holding high hopes even with a correct stock ROM.
I know, there's less people here than when I started by a long shot. You're by far the most active on here, but I thought you had an S4? I'll be getting the N5 in a month or so. I still plan to be in S2 threads but obviously to a lesser extent.
I do have an S4, but apart from the first couple of months, lost interest in modding it. I want stuff to 'just work' these days for the most part. I do run a custom rom/kernel, I just haven't changed it in ages & not interested in anything that trips Knox. Just can't be bothered putting up with stuff not working/spending a lot of time trying to make it work.
So...I accumulated a lot more knowledge of the S2, given I spent 18 mths or so actively modding it.
Understood. Yes that's what seems to be happening more now, phones which, if they're not on stock ROM, lose a lot of functionality/have stuff 'not work' for whatever reason. Like the GNote & its S-pen, HTC One and boomsound, Sony and its Bravia engine. I assume you still own the S2 anyway...
While you're here, is there anything in the Odin troubleshooting guide you've noticed which should be changed? I read over it again the other day but couldn't see anything major. If you don't want to read/comment no problem, asking as you're the resident Odin guru.
Yeah still have the S2. Haven't switched in on in 6 mths tho.
Nah, you've got everything covered in your thread. It's a great resource ('Odin expert' ? Hardly. I just read/learned a lot )
Mmm I imagine it's not the greatest experience after using a phone 3yrs newer for a while Cool. I added a couple little things just now (another pit file thread (shudder) which is quite well done & re-hosted the 3-part firmware instead of dropbox. Nothing special). Ok, call yourself what you want but what I'm sure of, is that by being on Q&A so much you have a lot more troubleshooting knowledge than probably anyone else for S2
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thanks Hopper for the help...
I have downloaded the Stock ROM for GT-I9100 Indian Version from Sammobile. I don't know what is 3-part firmware.
Now what i am going to do is Connect the phone to my PC showing (Firmware update encountered an issue. Please select recovery mode in Kies & try again) screen.
Then by clicking AP button selecting the TAR file extracted from the Zip file (Stock ROM).
Double check that only AUTO REBOOT & F.RESET TIME checkboxes are selected.
Hit Start and try my luck.
Shall i go ahead. Waiting for your nod...
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
MistahBungle said:
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
Click to expand...
Click to collapse
I have downloaded I9100G firmware only...
sorry it was my typing mistake
really sorry to panic you
I have also got a DLL file in the ZIP which i have downloaded. What is it?
Throw the .dll away, you don't need it.
Thanks to Hopper8
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thank You so much
I got my phone back to the original state:laugh:
Thank You so much for your help...
...
Hello guys!
I am new here, nice to meet all you guys. I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
trufogio said:
Hello guys!
I am new here, nice to meet all you guys.
Spoiler
I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
Click to expand...
Click to collapse
You should try to flash a Factory formatting firmware and remapping the partitions with Pit file using Odin. If this doesn't work... There's nothing else to do
TapaStalking
Where can I find the right factory formatting firmware and pit file? I have an International version of GSIII bought in Italy (16gb). In case it doesn't work, will replacing the motherboard do the job? The thing I still don't get is how can the internal memory be damaged if I have full access to the recovery? The recovery is stored in the internal memory, isn't it?
Are you Italian? If so, take a look at this... http://www.androidiani.com/forum/showthread.php?t=344896
TapaStalking
Yes, I am! Thanks, I'll have a look at that link.
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
西村大一 said:
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
Click to expand...
Click to collapse
But if the EMMC chip is bricked, how can I still enter into recovery mode? Isn't the recovery stored in the EMMC like any other partition? Am I missing something? I mean, If I couldn't go into recovery I would agree with you, the EMMC would have broken. But as I DO enter into recovery (and can read some files) looks like another problem... If I am wrong, please explain how it works because I'm a little bit lost
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
trufogio said:
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
Click to expand...
Click to collapse
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
ivano949 said:
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
Click to expand...
Click to collapse
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
trufogio said:
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
Click to expand...
Click to collapse
That's difficult for nothing. Done this summer on my sweet S3, there are tons of tutorial in youtube.... The only thing is wishing new motherboard is OK and don't have a locked imei.... Think at this... Maybe is just time to have a new (and newer) phone
TapaStalking
Are you using the original Samsung USB cable and USB 2.0 ports?
audit13 said:
Are you using the original Samsung USB cable and USB 2.0 ports?
Click to expand...
Click to collapse
yes, I am! I tried several times but it fails every single time... I think I'll buy a new motherboard, 20 euros is a great price. I already have a newer phone (galaxy s6) but I need this s3 to be back to work in order to use it with my secondary sim card Anyway, If you think about installing CM14 nightlies, they are not stable at all at the moment.
trufogio said:
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
Click to expand...
Click to collapse
I am not intending to be rude, I even explained what EMMC Brick bug means as a way to educate you and the ones that search the forums for explanations, but since you got my post deleted because you thought i was trying to be rude, well yeah, okay. That's why I hate people.
Please keep it respectful in here, and respect each others opinions..
Here's a thorough read for you guys : XDA Rulesforum.xda-developers.com/announcement.php?a=81
Regards
Vatsal,
Forum Moderator.