[Completed] Galaxy A5 (SM-A500FU) HARD BRICKED please help pls - XDA Assist

Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.​

Mrelenschi said:
Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.​
Click to expand...
Click to collapse
Hi
thank you for using XDA assist
Im really sorry to hear that OP,
Cant see any relevant for your device here at XDA but i can route you over here for your questions about your device..
http://forum.xda-developers.com/android/help

Related

Failed to flash, phone dead.

Good day people,
First of all. I want to say that I am aware of the forums regulations and that I have to use the search function before even creating a topic but I found nothing related to my situation.
A few days ago ( 3 ) I tried to flash my Samsung Galaxy SL i9003 with a the following ROM I9000XXJVU_I9000OXAJVU_OXA. Bare with me before saying that it's not compatible because it is a i9000 ROM. Which I wasn't aware of due to my foolishness at the beginning. I did not even bother to look for any consequences of what could happen of a unsuccessful ROM flash.
After flashing my phone with the i9000 ROM, odin said everything was successful, my phones screen turned bright light green. I turned the phone off and plugged out the cable. As far as I'm concerned, on the Q&A it said that flashing i9003 with a i9000 rom it would brick the phone. But this isn't the case. When I try to power the phone, it doesn't power at all, no signs of life. No button combination work. I have tried to make a custom JIG for it, using the 301k/300k Ohm resistor method, unsuccessful. Can any of you provide any information of how do I proceed? Maybe it is the batteries fault? I don't know. If the only option is warranty repair, I have broken the given rules and it will be most likely voided. Does any of you know what could I say ( lie ) to not get it voided?
Curoar said:
Good day people,
First of all. I want to say that I am aware of the forums regulations and that I have to use the search function before even creating a topic but I found nothing related to my situation.
A few days ago ( 3 ) I tried to flash my Samsung Galaxy SL i9003 with a the following ROM I9000XXJVU_I9000OXAJVU_OXA. Bare with me before saying that it's not compatible because it is a i9000 ROM. Which I wasn't aware of due to my foolishness at the beginning. I did not even bother to look for any consequences of what could happen of a unsuccessful ROM flash.
After flashing my phone with the i9000 ROM, odin said everything was successful, my phones screen turned bright light green. I turned the phone off and plugged out the cable. As far as I'm concerned, on the Q&A it said that flashing i9003 with a i9000 rom it would brick the phone. But this isn't the case. When I try to power the phone, it doesn't power at all, no signs of life. No button combination work. I have tried to make a custom JIG for it, using the 301k/300k Ohm resistor method, unsuccessful. Can any of you provide any information of how do I proceed? Maybe it is the batteries fault? I don't know. If the only option is warranty repair, I have broken the given rules and it will be most likely voided. Does any of you know what could I say ( lie ) to not get it voided?
Click to expand...
Click to collapse
I am glad at least u are aware of wrong rom flashing. Anyway ur phone is dead now. Simple solution is go to samsung service center & tell them a fake reason such as while updating ur phone via kies ur phone switched off automatically. Purposefully tell them that there is no fault from ur side. Never tell them that u have attempted to flash anything from odin. Thats all They will surely take ur phone & they will repair it without any cost.
But be carefully from next time. Have a habit of read everything before flashing anything
Adding a little thing.
You said:
" As far as I'm concerned, on the Q&A it said that flashing i9003 with a i9000 rom it would brick the phone. But this isn't the case. When I try to power the phone, it doesn't power at all, no signs of life. No button combination work. "
That IS a brick, and that is the correct meaning of the word.
A soft brick is when you flash a firmware and it boots to the SL logo, a hard brick (yours) is where the phone dies completely.
Just wanted to clear this
And you can give JTAG a go, search for somebody that offers it first.
Curoar said:
Good day people,
First of all. I want to say that I am aware of the forums regulations and that I have to use the search function before even creating a topic but I found nothing related to my situation.
A few days ago ( 3 ) I tried to flash my Samsung Galaxy SL i9003 with a the following ROM I9000XXJVU_I9000OXAJVU_OXA. Bare with me before saying that it's not compatible because it is a i9000 ROM. Which I wasn't aware of due to my foolishness at the beginning. I did not even bother to look for any consequences of what could happen of a unsuccessful ROM flash.
After flashing my phone with the i9000 ROM, odin said everything was successful, my phones screen turned bright light green. I turned the phone off and plugged out the cable. As far as I'm concerned, on the Q&A it said that flashing i9003 with a i9000 rom it would brick the phone. But this isn't the case. When I try to power the phone, it doesn't power at all, no signs of life. No button combination work. I have tried to make a custom JIG for it, using the 301k/300k Ohm resistor method, unsuccessful. Can any of you provide any information of how do I proceed? Maybe it is the batteries fault? I don't know. If the only option is warranty repair, I have broken the given rules and it will be most likely voided. Does any of you know what could I say ( lie ) to not get it voided?
Click to expand...
Click to collapse
Obviously a brick. Time to get a new phone. IPhone 5 is suitable for you.
Sent from my GT-I9003
by mistake i olsoo flashed s rom to sl nd it failed on odin nw it cnt get on neithr in recovery nor in download iz dere ne way to get bck plzzz help
Sent from my GT-S5360 using xda premium
There is a whole sticky thread dedicated to this issue. See if there's anything out there that can help you.
http://forum.xda-developers.com/showthread.php?t=1120785
longfeng said:
Obviously a brick. Time to get a new phone. IPhone 5 is suitable for you.
Sent from my GT-I9003
Click to expand...
Click to collapse
You'd better get an S3 or an HTC One X if you have money to spend.
Hope i helped
See this thread http://forum.xda-developers.com/showthread.php?t=1004647
unfortunate ......
Skander1998 said:
You'd better get an S3 or an HTC One X if you have money to spend.
Click to expand...
Click to collapse
What if he flashes another wrong firmware on that?
A new Expensive Paperweight :what:
Sent from my GT-I9003 using xda app-developers app
Actually your phone is not void of its warranty for you didn't even root the phone. So warranty is still intact. You just have to come up with an excuse.
Sent from my GT-I9003 using xda premium

Touchscreen not working after root, but S-Pen works fine

I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse

[Solved] Repair a possible brick (Galaxy S 4G) (Bad Flash)

I've flashed quite a few androids with custom ROMs, all successful except one brick was beyond repair. Then my brother asked me to root and flash a custom ROM to his T-Mobile Samsung Galaxy S 4G (Model: T959V). So I gave it a shot. Rooting was successful, but trying to get Clockwork Recovery on the phone, it confused me and I definitely messed up. The screen is discolored like a bad tv reception. One picture is what it's currently stuck on, and the other is showing I can still load it into the yellow download screen. My question is, is this fixable? If so, how?
Problem Solved
Matster239 said:
I've flashed quite a few androids with custom ROMs, all successful except one brick was beyond repair. Then my brother asked me to root and flash a custom ROM to his T-Mobile Samsung Galaxy S 4G (Model: T959V). So I gave it a shot. Rooting was successful, but trying to get Clockwork Recovery on the phone, it confused me and I definitely messed up. The screen is discolored like a bad tv reception. One picture is what it's currently stuck on, and the other is showing I can still load it into the yellow download screen. My question is, is this fixable? If so, how?
Click to expand...
Click to collapse
Problem solved thanks to stephen_w here: http://forum.xda-developers.com/showthread.php?t=1405489 and chadster214 here: http://forum.xda-developers.com/showthread.php?t=1183413. Problem solved with Odin 1.85. Give them thanks if you ran into this problem and these people helped you as well.
Glad that you could get things resolved! I hope that you enjoy your "new" phone, especially as you now know how to recover from things. You might want to look at heimdall as well, especially if you start playing with other custom ROMs and kernels.
When you have a chance, if you change the "[Q]" to "[solved]" or the like, people will easily be able to tell that there is an answer on the thread. Perhaps it will be the one they are looking for themselves!

[Completed] [Q] galaxy s5 soft brick

i had lollipop on my at&t galaxy s5 and tried to download cwm recovery via flash fire , ii soft brick my phone , i flashed stock rom via odin many times but its not working , i get stock on on logo screen and then the screen turns off and the led is on (blue light)
i dont know if this is the problem , but when i go to download mode the reactivation lock is on also a new thing appeared, scure download : enable and below it
udc start
i tried many things like flashing recovery through odin and trying to update through adb but nothing worked
is there any solution for this , and can it be fixed or i bricked my phone ? cuz i dont want to take it to repair shop and take money from me without fixing it
Hi
Thanks for writing to us at XDA Assist. Take a look at this thread:
[GUIDE] Soft-bricked, looking to unroot, or just looking to downgrade, or start over?
i did that
but it didnt work , and i took it to a repair shop and they said that there is problem with the IC!!!
habeebsamawi said:
but it didnt work , and i took it to a repair shop and they said that there is problem with the IC!!!
Click to expand...
Click to collapse
Ok, so you need a hardware repair done?
timmaaa said:
Ok, so you need a hardware repair done?
Click to expand...
Click to collapse
i dont think its a hardware problem because it was running fine , i went to the guy now and he told me that he is trying to download the software but the phone is not taking it , and he told me that he took it to bci samsung so maybe they can fix it
after i flashed the official firmware the (custom ) kept showing when i turn on the device which means the firmware was not flashed , this is letting me to be crazy i have soft bricked my phone many times and fixed it with no problem , i dont know what to do
(I've been trying out new ROMs this week, and I must have bricked my phone at least a dozen times. Boring, waste of time, not a problem, though. I had the long blue light about 3 times.)
Make sure you have the 4.4.2 for the AT&T S5, not some other model S5. Boot to download and flash it again. SamMobile Firmwares has 4.4.2 for the phone. Or I'm sure you can find it on the AT&T S5 forum at XDA Forums.
i did all of the above like using odin or wiping data but nothing worked i think because the reactivation lock is on
is there anyway to turn off reactivation lock so i can flash stock firmware with no problems
habeebsamawi said:
(I've been trying out new ROMs this week, and I must have bricked my phone at least a dozen times. Boring, waste of time, not a problem, though. I had the long blue light about 3 times.)
Make sure you have the 4.4.2 for the AT&T S5, not some other model S5. Boot to download and flash it again. SamMobile Firmwares has 4.4.2 for the phone. Or I'm sure you can find it on the AT&T S5 forum at XDA Forums.
i did all of the above like using odin or wiping data but nothing worked i think because the reactivation lock is on
is there anyway to turn off reactivation lock so i can flash stock firmware with no problems
Click to expand...
Click to collapse
@habeebsamawi,
XDA Assist is not a help desk. Our trained RC's will point you to the right direction to assist you with your problem.
Your device has it's own section located here: http://forum.xda-developers.com/galaxy-s5
You can browse through the current threads available to find a solution to your problem.
If you are unable to find a solution, you can start a thread in the Q&A section for that problem and hopefully someone with the same device as you will offer their assistance.
Please do not open any more threads in the XDA Assist forum as I have directed you to the correct forum for your inquiries.
Thank you,
Thread Closed.
Neo
Forum Moderator

[Q] Need help to update Samsung Galaxy S III I9300

Hello folks,
i am new here, i have a problem with one of my friends mobile Samsung Galaxy S III I9300 Android v4.0.4 (Ice Cream Sandwich), it so happened he dropped the mobile from his hand and from that moment, the device fails to load properly.
I tried to go to Recovery mode, by pressing Power key+DownVol key+Home key. The next screen was all fuzzy, it didn't show anything.
So i tried Power key+UpVol key(this time)+Home key, it showed a warning page, please see images to be more clear.
On continuing with the process, it went to Download mode.
I am little familiar with that process, since it is trying to update the device OS to a newer version of Android.
I did a little research and found out there was Android 4.4.4 Kit Kat available.
I can proceed to download that, but i want to know few things and i.e.,
The device is not Rooted.
CWR is not installed.
Whether it is safe to proceed with the update of Android Ice Cream Sandwich to Android Kit Kat.
I also found Galaxy S III can be updated to 4.3 (Jelly Bean), but i want your opinion which would be suitable for this device.
Thanks.
I do not want to brick my friends device, since i am getting paid to do this stuff. Hence i am requesting any kind of expert advice.
Thank you.
P.S: Any suggestion is welcommed and waiting for any reply impatiencly. Also if the moderator thinks this post must be in some other part of the forum, please do so. :fingers-crossed:
Hello again, i did a little research and found out this site, where it mentions in detail how to install ClockworkMod Recovery 6.0.4.7 on Galaxy S3 GT-I9300
http://trueandroid.com/install-clockworkmod-recovery-6-0-4-7-on-galaxy-s3-gt-i9300-how-to/
I did as mentioned in the tutorial and while opening the Odin, and checking the AP button, and selecting the non touch version of ClockworkMod Recovery 6.0.4.7 ; i am getting this error. Please see the snapshot.
It also say, PIT partition not found, does anyone know how to figure out this problem.
Or
Is it a hardware issue, do i need to change the motherboard or give it to technician to fix it.
First off: Have you tried posting it under the correct category on this forum? its under galaxy core... you have a galaxy S 3
Second, you can update if it stock... custom recoveries and roms do void warranty. That is, if the kitkat is for his phone it is no problem. upgrading wrong rom to your phone will mess with it yes. Boot loops and stuff.
Then again, if it droped I would rather have sent it in for repairs if it was still under the warranty .
canisalbus said:
First off: Have you tried posting it under the correct category on this forum? its under galaxy core... you have a galaxy S 3
Second, you can update if it stock... custom recoveries and roms do void warranty. That is, if the kitkat is for his phone it is no problem. upgrading wrong rom to your phone will mess with it yes. Boot loops and stuff.
Then again, if it droped I would rather have sent it in for repairs if it was still under the warranty .
Click to expand...
Click to collapse
I find it quite difficult to find my way in this forum, just newbie here.
But thank you for your concern. My friend has taken the mobile , he thinks its better to repair it by technician.
Enough of head-ache for a device that can't be repaired through updating, the mobile was trashed. Couldn't be salvaged through
updating.
desktopuser said:
I find it quite difficult to find my way in this forum, just newbie here.
But thank you for your concern. My friend has taken the mobile , he thinks its better to repair it by technician.
Enough of head-ache for a device that can't be repaired through updating, the mobile was trashed. Couldn't be salvaged through
updating.
Click to expand...
Click to collapse
I understand.
On top of the page there are 2 places you can enter stuff, one says "type to find device" and the other for searching all the forums. Writing i9300 - and clicking on the line - will get you the I 9300 forums
desktopuser said:
Hello again, i did a little research and found out this site, where it mentions in detail how to install ClockworkMod Recovery 6.0.4.7 on Galaxy S3 GT-I9300
http://trueandroid.com/install-clockworkmod-recovery-6-0-4-7-on-galaxy-s3-gt-i9300-how-to/
I did as mentioned in the tutorial and while opening the Odin, and checking the AP button, and selecting the non touch version of ClockworkMod Recovery 6.0.4.7 ; i am getting this error. Please see the snapshot.
It also say, PIT partition not found, does anyone know how to figure out this problem.
Or
Is it a hardware issue, do i need to change the motherboard or give it to technician to fix it.
Click to expand...
Click to collapse
Bro you should have unchecked the re partition option
Susan Dahal said:
Bro you should have unchecked the re partition option
Click to expand...
Click to collapse
OOPS! I did not even see that one

Categories

Resources