Big problem with 2 different boards mothers! - Galaxy S III Q&A, Help & Troubleshooting

Friends,
I have a problem and need lots of help.
My S3 started to not charge more for usb.
I took him on a assistance and exchanged the USB connector
He worked for 1 week and stopped .... ok I was carrying with the external charger.
However one day he simply stop in the screen sansung not spent more that point even after leaving it on hours ... im took him for official Samsung maintence and was told that the mother board was damaged and needed replacing.
Well as I am persistent, I downloaded the original rom in SamMobile and tried to install the recovery
And then ... he does everything right but always hangs in part: updating partition details ... failed
And give not pass this part even putting a cyanogenmod or sentinel ... simply does not pass.
Ok!
I bought a plate of another S3 used.
I replaced the mother board and the s3 started normally
However the android was older, with a lot of app "VIVO" (mobile carrier here in Brazil) that left the s3 a turtle.
So I downloaded the newest version of the original room in SamMobile and tried to install in the Recovery.
Guess what!
updating partition details ... failed
Imagine my face after buying a new board and still have the same error.
Moreover the phone is now no operating system and only accesses the recovery.
Now I'll describe what I've tried:
I tried to install via TWRP 2.0 - the problem remains in the original room and other rooms modified error appears Sector 7
Tried by clockwokmod 6.0.4.5 - the problem remains in the original room and other rooms modified error sector 7 appears
tried formatted the internal card and nothing
I tried a wipe data factory reset and nothing
tried a wipe chache and nothing.
I'm simply no options and no help.
Please can someone help me?
Sorry for my bad english!
PS: searched on google and the forum and not found anything.

Questions go in the q&a forum. Report your own post and ask a moderator to move it for you.
Flash the rescue firmware with Odin, then factory reset, follow the instructions exactly. If that won't flash then your emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk

boomboomer said:
Questions go in the q&a forum. Report your own post and ask a moderator to move it for you.
Flash the rescue firmware with Odin, then factory reset, follow the instructions exactly. If that won't flash then your emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hello friend,
thanks for trying to help me.
Before seeing your message I got intalar the original room via odin.
But the question still persists.
Why does this not installing via Recovery.
For those who are into the same problem I did following:
accessed the site and downloaded the official SamMobile room for i9300 zto
Unzipped the file
I opened odin 3.9
I selected the file. Md5 of the original room
I installed via Odin ...
Now is working.

emersontavares said:
Friends,
I have a problem and need lots of help.
My S3 started to not charge more for usb.
I took him on a assistance and exchanged the USB connector
He worked for 1 week and stopped .... ok I was carrying with the external charger.
However one day he simply stop in the screen sansung not spent more that point even after leaving it on hours ... im took him for official Samsung maintence and was told that the mother board was damaged and needed replacing.
Well as I am persistent, I downloaded the original rom in SamMobile and tried to install the recovery
And then ... he does everything right but always hangs in part: updating partition details ... failed
And give not pass this part even putting a cyanogenmod or sentinel ... simply does not pass.
Ok!
I bought a plate of another S3 used.
I replaced the mother board and the s3 started normally
However the android was older, with a lot of app "VIVO" (mobile carrier here in Brazil) that left the s3 a turtle.
So I downloaded the newest version of the original room in SamMobile and tried to install in the Recovery.
Guess what!
updating partition details ... failed
Imagine my face after buying a new board and still have the same error.
Moreover the phone is now no operating system and only accesses the recovery.
Now I'll describe what I've tried:
I tried to install via TWRP 2.0 - the problem remains in the original room and other rooms modified error appears Sector 7
Tried by clockwokmod 6.0.4.5 - the problem remains in the original room and other rooms modified error sector 7 appears
tried formatted the internal card and nothing
I tried a wipe data factory reset and nothing
tried a wipe chache and nothing.
I'm simply no options and no help.
Please can someone help me?
Sorry for my bad english!
PS: searched on google and the forum and not found anything.
Click to expand...
Click to collapse
If it is the partition problem, you have to go back to Samsung for a new motherboard. Try flashing other 4.3 roms on sammobile. You dun have to flash one from ur country.

Related

[Q] 'charging.jpg' draw failed when charging [SOLVED]

Hi guys,
I just tried flashing the leaked ICS build from samsung through odin and I'm pretty sure something messed up somewhere because whenever I try to charge the phone when the power's off, it shows "'charging.jpg' draw failed". Also whenever reboot the phone it goes into the recovery and hitting 'reboot now' only starts up my android. I've tried everything- factory reset, wiping cache, reflashing new roms; nothing has worked. I read that it could be a corrupted param. Not sure what that is. Please help!!
Its a Alpha unstable test build what else will have have but problems .
....................................
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
None of that worked. I actually managed to solve it. Someone over at the i777 forums had a similar problem and fixed it by flashing a stock param file. I got the i9100 param file from this link- http://forum.xda-developers.com/showthread.php?t=1315401&highlight=param
For anyone else who's facing this problem, use mobile odin to flash it 'cause it doesn't increase your binary counter
http://forum.xda-developers.com/showthread.php?t=1136699
easy step guide video.. excellent work from connexion2005 ;thumbs;
I have the same problem with my samsung tablet but I do not understand what you did to fix it odin?flashing? None of this makes any sense to me can anyone help please? Thanks Lynn
I even flashed successfully official firmware so i dont know what to do
help- Samsung tab 11- 5 yrs old is showing 'charging_7.jpg' draw failed when plugged in to charge but when off charge does not turn on
-
One restore your backup.
Two. Factory Reset.
Three Flash stock rom via Odin.

Need help! Lost IMEI and phone refuses to update.

Hi XDA and a Happy New Year to everyone.
I recently bought a SGSII from someone, at a very low price, because of some software problems.
I could use it for spare parts, but I`d like to fix it if it is possible.
As far as I know, the phone was used to "test" different roms and tweaks by a kid who thought was a developer, and accidently messed up its efs folder without backing it up, so the phone now has a generic IMEI (0049..)
I found a final solution for this, in case nothing works, from user Odia, who can restore your efs folder without having a backup, and I`ll keep this option as a last resort.
But wait, there`s more.
The phone is acting really weird. Each time I start it, it reverts back to its default settings. From power options, to widget location, everything goes back to their original state.
Further more, while taking photos with it works perfect, when recording a video, it doesn`t save its self on to the flash memory.
I`ve tried flashing a different ROM (at the moment it has a default 2.3.3 Samsung ROM) from 2.3.3 to 2.3.5, using Odin. Everything goes well while flashing, with no errors in Odin. But after the phone reboots it has the same firmware/rom as before. Nothing changes. I`ve confirmed this by dialing *#1234#.
The IMEI problem isn`t that important (at the moment), but I`d like to be able to at least use the phone and to install a different ROM.
I don`t know what could be the problem, it`s like everything on it is on Read Only, or like a computer with Deep Freeze installed - everything looks ok while writing, but after a reboot, nothing was saved.
If you need anymore details regarding the device, please let me know and I`ll try to post them asap.
Hoping someone can help me with it.
No IMEI means your phone will not connect to a network as its part of the handshake process .
Suggestion would be .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery or install CWM and ROOT kernel if needed
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware from stock firmware post
jje
Stuck again.
First of all, thank you JJEgan for your reply.
I`ve tried what you`ve told to, but failed.
Tried installing CWM (GT-I9100_ClockworkMod-Recovery_4.0.0.2 and GT-I9100_ClockworkMod-Recovery_5.0.2.3) from the official thread, using Odin (both 1.83 and 1.85) but after the phone reboots, it isn`t there.
If I try accessing it via VolUp + Home + Power, it goes directly into the Android Recovery System, the default one, and not CWM.
I`ve even installed it via Odin and immediately removed the battery in order to prevent the phone from rewriting itself after Odin said everything is OK, and got the same results.
Dialing *#1234# gives me the following:
PDA: I9100XEKDB
PHONE: I9100XXKDH
CSC: I9100XEKD9
Build Info: Tue Apr 26 09:10:03 KST 2011
Click to expand...
Click to collapse
I`ve tried locating the correct version of CF-Root for it but I can`t find one for KDB in the official thread.
As I said in the first post, when I try to write something on it using Odin, everything goes well, no error, it doesn`t freeze, but after it sends the reboot command, it`s like nothing happened. It reverts everything to stock.
Any other thoughts ?
I do not believe you have an international version of the sgs2, you may have 19100 G or other version which cannot be rooted by using the standard cfroot.
check the label under the battery for which version you have.
I do not trust any of the information from the firmware as it may have been altered as one of the tweaks.
as far as I know the was no XXKDH. the number system used is 2 letters followed by a number
k = year d= month 2011 - april is correct but the H is not.
you may have a chinese rip off of the sgs2.
# = version for that month.
Thank you for your answer Cosmic Blue
The phone isn`t a rip off. It`s a SGS2 from Orange, Ukraine (I believe).
Everything on the device is signed by Samsung. The phone`s specs are exactly what they should be. Kies identifies is perfectly and I can sync everything with it. Samsung drivers also work correctly.
Label behind the battery:
MODEL: GT-I9100
SSN: I9100GSMH
RATED: 3,7V = ; 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
Click to expand...
Click to collapse
Plus IMEI (The original one I`m trying to restore) and Serial Number.
Also, on the bottom rim, next to the speaker, there`s the Orange logo and I9100.
I had a brand new I9100 before, and this one isn`t any different from that one in anyway, except that the OS is all messed-up and the IMEI is a generic one, a problem a lot of people found themselves in around here.
Also, you can find the firmware version I mentioned above at samfirmware.com
As XWKDD was one of the first i would say KDH is probably correct but you are reading wrong info .
Therefore H is correct and phone is i9100 SGS 2 not a Chinese rip off .
First firmware on stock roms thread .
XWKDD
Firmware info
PDA:XWKDD
PHONE: XXKDH
Build date: 26/04/2011
However it looks like you have failed to install cwm and root .
Go to the cwm and root thread and flash the first one as below via ODIN
http://forum.xda-developers.com/showthread.php?t=1103399
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip -
Flash that one via ODIN report back
jje
Same problem with it.
Downloaded the mentioned CF-Root version, flashed it using Odin as PDA, rebooted with no SuperUser app in application drawer. Rebooted and tried accessing CWM with no success. Just Android System Recovery <3e>.
Also, reflashed CF-Root without Auto Reboot in Odin, and when it finished, I removed the battery and put it back in. Tried to access CWM with the same results as above.
I managed yesterday to root it by flashing XWKDD_insecure.tar as PDA and using SuperOneClick v2.3.2. The phone had a SuperUser app on it, but the phone was really lagging and after a reboot, it wasnt` there anymore.
The problem is definite then the read only memory is not holding the flash possible its a part that holds the ram during flash that is corrupt .
Sorry not a clue it looks like service job to me .
A thought have a look at Mobile ODin thread .
jje
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
proone said:
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
Click to expand...
Click to collapse
I have seen this before, basically the NAND controller is toasted so it cant write, only read.
As they said, only way is to replace the motherboard (Where the NAND/controller) is.
Its a shame they wont repair it under warranty, I suppose they noticed that its been flashed and killed
Model: GT-19100, SSN: 19100GSMH, made in korea by samsung, I flashed it back using a rom from Xda forums but now its Android 2.3.5, no super user, I have HC-kTool that I downloaded from new Android market, it says I need root to use HC-kTool. I have Root explorer and Rom manager but I dont have root, how do I fix imie, baseband, my Samsung galaxy s2 works well on wifi, everything works but it doesnt read my sim?????

SDS S3, Need Help Flashing Please

Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
if it's a sudden death, there's no way of recovering the data
Katanaqui said:
Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
Click to expand...
Click to collapse
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
chap rriespr
JJEgan said:
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
Click to expand...
Click to collapse
Ahh thanks, I had a read of a few of these but I missed the 'for the ultimate noob' one
I've got the USB drivers installed correctly on my pc, I think the phone just won't boot up far enough to do whatever it does to be mass storage at its end.
I've tried pulling my files via ADB as well and nothing.
My problem is there doesn't seem to be a way of getting my data off my phone onto my pc as my phone won't boot. So as a long shot, I'm trying to fix the booting problem by flashing it, hopefully without wiping any data, so then I could boot properly and rescue my files.
My question is what would be the best way to go about attempting this: flashing the whole stock firmware file, or just the boot loader file?
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
JJEgan said:
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
Click to expand...
Click to collapse
I thought SD meant a soft brick, ie. stuck in bootloop but with the possibility of recovery/download modes, whereas a dead phone is hard bricked?
Ok thanks
Sd means "softbrick" or "sudden death" depending on who abbreviates it.
Sudden death is a full hardware brick ( no chance of recovery), softbrick can be fixed through recovery, download mode and/or jig
Sent from my GT-I9300 using xda premium

[Q] Soft-Brick help!

Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy

[Q] Galaxy SII - GT-I9100 - unresponsive after boot to home!

Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Hopper8's 'Odin troubleshooting' thread stickied in the General section; in particular flashing the 3 part firmware (this will wipe your phone). Also try everything in that thread for as long as you have the patience for it. These cases tend to be fixed by perseverance, or not at all. There's no easy fix. It's either a hardware issue(s), NAND corruption, or something really obvious being missed here. If it's the latter, hopefully the stuff in Hopper's thread helps you fix it. If it's either of the other two, I'd be cutting my losses.
Ansell2k12 said:
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Click to expand...
Click to collapse
lcd may be the culprit but also the firmware is crashed flash it again properly after a factory reset from e3
Progress...but not as id hoped...
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Ansell2k12 said:
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Click to expand...
Click to collapse
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Ansell2k12 said:
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Click to expand...
Click to collapse
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
??
king_below_my_lord said:
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
any chance you could point n the right direction?
i have had a look at the stuff to edit vold, and it seems i am unable to do so as my phone isnt usable once booted
cheers Ansell2k12
Phone has gone in the bin cheers guys, thanks for the help
....
You could easily flash a edited vold.fstab file by generating a flashable zip file. That's why I said via recovery or if you are clever enough you can easily use recovery flashable Aroma file manager to overwrite the file.
Sent from my GT-I9100 using Tapatalk

Categories

Resources