Hi internet users,
I would like to solicit your help regarding a quite strange problem with my phone.
As indicated in the title, It is a Samsung GT-S5839I.
In order to create coherent whole i will sum this up with questions and answer.
What is it that, for me, is very likely to be the origin of the problem ?
I think i can say that the origin of the problem might be caused by an installation of a wrong ROM.
In other words, immediately after the installation of this one, the problem appeared.
What happens when i turn on the phone?
If i try to turn it on normally using the power button ; the phone turns on correctly but the screen turns out to be black and backlighted.
I mean by this that i can't see anything, the buttons are enlightened, there is light on the screen (maybe caused by the backlighting), but there is no way to know what is going on.
The only clue i have is the noise that the animation done at boot up.
When the phone ends his booting task, it is likely that it reached the unlocking screen.
If i try to turn it on normally using the volume up, down and the power button ; It happens the exact same thing that when i try to turn it on normally.
If i try to turn it on using the volume up, down, home and the power one ; It happens the exact same thing that when i try to turn it on normally.
In other words, the recovery mode doesn't work.
What can i do ?
I can access to the files on my SD CARD using the Samsung Kies 2.6 software.
I can access to the unlocking screen without visual returns.
What i can't do ?
Use the phone's touch keys .
Access to the ADB module.
Access to the download mode.
Access to the recovery mode
Thanks in advance for the attention you will bring me.
@chikamtsu, You do officially hard bricked your device ( both modes are not accessible ) .
There is so little remained to do mate, you can get a little device called "USB jig" as a last resort to force your phone into Download mode ( may or may not work,even if i provide instructions). As for your LCD blackness/dimness it goes, your symptoms might be caused by water/dust/corrosion damages more likely rather than flashing a wrong firmware ! in s5830i which is very similar to your device, replacing IC light u 503 part will solve problems in most cases ( I am not so sure of IC part of your device). Be cautioned though disassembling your device is not for fainthearted, you need expertise to open such a delicate case; hence I can't ask for critical information such as measuring voltage IC . One more thing mate, for the future record could you kindly provide a link to firmware you did flash from sammobile.com database preferably. Your original CSC/MODEM/PDA , Android version/ Kernel is also needed .
Raakib zargar said:
the symptoms you have told state that you have hard bricked your device
Click to expand...
Click to collapse
Sure, but, what are my options ?
@chikamtsu, Just looking to the pattern he has been posting in this section mate >> indeed typical spammer without proper knowledge/insight of what is really happening under the hood of our Android device
As for your problem, I have already explained all of the possible solutions in details ! ( you may check my comment here too )
P.s: Report his ass for disturbing peace ( Report button ),, Really this dude make assistance impossible by reviving old topics; and such an odd way to increase post count ,, he even quoted my comment ,, pretty Hilarious
chikamtsu said:
Sure, but what are my possibilities ?
Click to expand...
Click to collapse
Well if you can tell me that which rom you had flashed because some roms for Galaxe Ace after flashing need to press the Home button to avoid blacksceen.
Well your possibilities are to give your phone a usb jugg service/Heimdall and after that take it to download mode and flash back using odin.
Related
First of all sorry for my english not good.
Start : with my HD2 have brick after task29 and not success to flash new ROM I'm take USB. cable out and try to open my HD2 in to boot loader by put volum down + power bottom but screen not show any image or 3 color my phone it only long vibration pull battery out waiting 30 minute and put battery in and try to open my phone to boot loader but is same only long vibration.
Now : can not do any think with it when try to plug power in my phone is auto startup and long vibration.
I'm search on google and in this forum not have some one face problem same as me please help me to fix this.
Any body please help me, I'm love it because now we can run both WM. and Android
Upppp waiting for your help
Did you try a long press of the reset-button?
You could try to put the original Stock Image from HTC onto the root-folder of your SD-Card, rename it to LEOIMG.nbh and Push Vol up + Vol down during start and follow the on-screen instructions if it works.
Otherwise use Search-Function in the forum.
ı have jtag HTC for samsung and HTC devices if u want send for repair to me..
www.sevgigsm.net/forum
admin..
I use ORT
Did you check to make sure your radio version was correct before flashing? This is probably the number one reason for bricking.
Check this thread it may help you if you did the flash properly:
http://forum.xda-developers.com/showthread.php?t=668347
i got same problem now...
no screen, no boot, vol down+ power oso same
no screen just a long vibration
anybody help?
I am using the correct radio so don't tell me I am using a wrong radio or something, I have been flashing for 4 months so I know EXACTLY how to flash.
now i can neither get into tri-color or hard reset so don't tell me to flash or smth like that, just tell me how to recover properly
Don't tell us to use search or something because seems like only 2 of us is encountering this problem in the internet
I'm exactly the same problem as TS coz it juz auto go vibrate when plug in battery
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
at the long vibrate, when i plug in to my pc, it will keep on got usb connected and disconnected sound
and dont know what device is connected as not shown in found new hardware and device manager
I also have been searching all possible keywords about what me and TS encountered but all linked to completely UNRELATED results(like search for long vibrations only link to people asking how to make vibration long and 1st result is this thread)
bountygiver said:
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
Click to expand...
Click to collapse
Silly question, but are you holding (and keep on holding) the Volume-Down button while you press the power button?
of course YES
i told you i have been flashing for so long
Leo from T-Mobile. Hi! I've got same problem. After flashing new (next) rom phone definetely died. Phohe is currently simfree and with HSPL. Only one reaction is short vibration after press power button. I searched everywhere. My phone has no bootloader but system see him as Qualcom CDMA Technologies MSM. Thats all, any ideas? Please and thanks for advice.
czaruch said:
Thats all, any ideas?
Click to expand...
Click to collapse
Yes, you flashed a non tmous stock rom that included a ..51.. radio and it destroyed your phone.
What rom? exact filename please.
thank you so much.
I bricked a Leo with the .51 radio. I think I read that is a European or otherwise foreign radio. Since your ROM has Euro in the name.......
czaruch said:
ROM_Leo_HTC_WWE_EastEurope_1-66.
Click to expand...
Click to collapse
The full filename for that rom is
RUU_Leo_HTC_WWE_EastEurope_1.66.479.2_Radio_CRC_Si gned_15.32.50.07U_2.07.51.22_2_Ship.exe
it comes with a version x.xx.51.x radio, and they do Not work on tmous (t mobile us) phones. They kill them
Your phone is dead, sorry. No known fix.
warranty or repair (or JTAG if you are brave and have the money)
a friend of mine bricked his phone. he then tried to microwave it, but that didn't work after that he took a power wire from an old computer, cut it and connected it directly to the phone's parts where the battery would go...this completely f-ed his phone up (he also used a lighter to fake a powersurge of the battery). Then he called htc and a few weeks later he got a new hd2!
GOOD LUCK
lol, he doesnt need to do any of that, its allready as dead as it can be. Loads of epople have had them replaced under warranty with this kind of brick. It wont start, so htc/tmo cant see that its been hacked.
Hi! I understand and realy sad. Somebody know where could I fix it in UK? And how much for this pleasure. Thanks.
i would contact htc, see what they have to say. (dont say you flashed it, it just stopped working")
Urgent help .. my phone is dead !
here is what happened exactly :
- i was running twitter normally as i used to do .. suddenly " Stopped working " error appeared
- tried to open twitter again or facebook app .. it keep says stopped working all the time
- i restarted the phone .. it stuck on the kernel screen .. tried to restart again , it stuck on the kernel screen again
tried to open in recovery mod .. once i opened the recovery mode it says :
Cant amount xxx.log
cant amount xxx.log
i don't remember exactly what the name
- tried to restore old recovery backup .. it keep says cant amount
- tried again to restore the backup .. this time the phone turned off forever !
now i cant even turn it on again
tried with 3 batteries but no way .. i cant turn it on again
tried to charge it .. but the charger light didn't appear
i am using RR JB 3.1.2 and dorimanx kernel v7.8
help please
MamomaN said:
Urgent help .. my phone is dead !
here is what happened exactly :
- i was running twitter normally as i used to do .. suddenly " Stopped working " error appeared
- tried to open twitter again or facebook app .. it keep says stopped working all the time
- i restarted the phone .. it stuck on the kernel screen .. tried to restart again , it stuck on the kernel screen again
tried to open in recovery mod .. once i opened the recovery mode it says :
Cant amount xxx.log
cant amount xxx.log
i don't remember exactly what the name
- tried to restore old recovery backup .. it keep says cant amount
- tried again to restore the backup .. this time the phone turned off forever !
now i cant even turn it on again
tried with 3 batteries but no way .. i cant turn it on again
tried to charge it .. but the charger light didn't appear
i am using RR JB 3.1.2 and dorimanx kernel v7.8
help please
Click to expand...
Click to collapse
Do you cant enter downloading mode?
If not. You phone get hard bricked.
Sent from my WT19i using Tapatalk 2
i cant even turn it on at any mode
no download mode .. no recovery mode !
it seems like i didn't press the power key
MamomaN said:
i cant even turn it on at any mode
no download mode .. no recovery mode !
it seems like i didn't press the power key
Click to expand...
Click to collapse
It's not a hard brick -_- if your phone shows any kind of activity, be it even battery charging animation when it's off.
Try to get a USB Jig, that'll take you to download mode and then flash anything via Odin.
if it is a Hard brick JTAG could be helpful. Also try to contact AdamOutler http://forum.xda-developers.com/showthread.php?t=1236273 He is develpoing a SDCard Recovery for hardbrick devices.
He need a device for it, and if he get it in time it will help you.
No .. my phone didn't show any kind of activity
no light .. no charging animation .. nothing at all
http://www.xda-developers.com/android/explaining-and-advancing-the-unbrickable-mod/
Hard Brick-The device is unresponsive and will not enumerate USB, a hardware based solution is the only method which will recover this type of brick
Soft Brick -The device shows something on the screen or possibly nothing at all, firmware download is possible because this is a “Download Mode”.
UnBrickable-The device has been modified to accept a debug-mode flash which cannot be altered.
Lucky Brick- The device ends up in UnBrickable debug mode and the Ultimate UnBrickable Resurrector can be used without a hardware modification to resurrect the device.
Click to expand...
Click to collapse
pull out the battery and waith 5 minutes. afther try to go on download mode.
Inviato dal mio GT-N7000 con Tapatalk 2
tried to remove the battery for 7 hours .. no way !
so , i should go to the repairing shop ?
no way ?
Seems like something got fried inside
Sent from my GT-I9100 using Tapatalk 2
^ oK , good
any help ?
What kind of help are you expecting ? Tho it's obviously not what you want to hear, it doesn't sound like it's a firmware issue that might mean it's (relatively) easily fixable.
If its under warranty, send it in to Samsung/authorised repairer & hope they don't care or don't notice you've been running non-stock firmware on the phone. You never know, they might fix it under warranty. If they won't, then you can look at having it JTAG'd or repaired locally by a 3rd party repairer given that will probably be cheaper than having Samsung/authorised repairer fix it if they do decide to charge you.
Anything anyone here tells you to try is just delaying having your phone fixed/depriving you of your phone for as long as you delay having it fixed.
i mean i need to make sure there still a hope !
based on a previews experience .. anyone saw this problem before ?
also it's the first time to know about the Hard brick
based on what i said , is my phone having a hard brick ?
so , it will be a software problem or something like that ?
Try this ^^ CLICKY
can't hurt by sounds of things :good: :fingers-crossed:
The repairing shop told me that the mother board burned !
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
saurabh_goyal93 said:
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
Click to expand...
Click to collapse
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
3: If you screwed up the bootloader then you can bring your phone back to life by using JTag. There are people who do this for a little money, so if you don't have warranty anymore, this is the way to go because it's a lot cheaper than replacing the mainboard.
Thanks a lot
Thanks for such an informative reply. Really appreciate it.
Scarface1991 said:
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
Click to expand...
Click to collapse
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Scarface1991 said:
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
Click to expand...
Click to collapse
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
saurabh_goyal93 said:
Thanks for such an informative reply. Really appreciate it.
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Click to expand...
Click to collapse
The Bootloader is the first thing that is loaded when you power up your phone. If you screw up the bootloader your phone won`t boot up at all. This is caused by the user of the phone, that`s why people say: "Your hardbricked your device".
If your hardware fails to function properly because of whatever reason then it`s not a hardbrick but simply a hardware failure. It is in most cases not caused by the user (except if someone would be dumb enough to overclock CPU/GPU to a ridiculous high level)
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
Click to expand...
Click to collapse
Look at the XDA Q&A Threads. There are several cases a day where people have problems flashing something on their phones because Odin fails for some reason. That`s why I would use Odin only when it`s really necessary. When I had my first Smartphone (Samsung Wave) I flashed a lot of stuff on it and one time the flash tool just reported an error and that`s it (bootloader was screwed). I don't know why it failed until this day. So flash a bootloader only if it`s absolutely necessary because this is the most dangerous thing that you can do to your device.
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
fullycompletely said:
I
This is I9300 forum if you do not have I9300 this is the wrong forum and any advice may not apply to your phone .
You say >>>>>
SGH-I747M
Option #1: Pay someone to perform a JTAG repair service.
That may work but it depends upon the actual problem .
Option #2: Attempt to boot into recovery using a JIG.
Dirt Cheapo always worth a try .
Option #3: Play dumb and return my phone under warranty.
It will be either rejected for warranty or repaired .
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself?
YES use GOOGLE search .
I will be more careful in the future but I don't want to be helpless if this ever happens again.
But JTAG is no magic solution .
helpless is a simple fact of reading the faqs and guides after its broken .
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
READ the JTag thread .
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Phone is not old enough for no warranty but warranty refused then you pay .
Click to expand...
Click to collapse
fullycompletely said:
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
try a USB Jig. only a few £ off ebay etc.
Hi,
Yesterday my phone was working fine, today ... It bootloop after 5seconds, even if i start it in download mode, i feel like the "Start" button is stuck, but i prefer to ask first. i tried to get a log from adb logcat, but the phone isn't recognised in 5sec so i have nothing.
EDIT: The phone is comming back from support because of the motherboard "suddent death", they replaced it with a same new one.
Known problem ? Any idea ? :x
Firmware version ????
Read the sudden death syndrome post in general .
recovery ???
jje
JJEgan said:
Firmware version ????
Read the sudden death syndrome post in general .
recovery ???
jje
Click to expand...
Click to collapse
Thanks for the answer
As it reboot after 5second i can't even go in recovery mode,
I don't remember the firmware version, but it's the stock one.
I'm gonna read (again) the post about sudden death
seems like the power button is stuck.
Glebun said:
seems like the power button is stuck.
Click to expand...
Click to collapse
Yea that's what i thought, but i really don't know how to open the phone, any tip ? link ?
Minoui said:
Yea that's what i thought, but i really don't know how to open the phone, any tip ? link ?
Click to expand...
Click to collapse
I add that it also could be this:
rootSU said:
2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.
One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.
Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented
Click to expand...
Click to collapse
But i can't really go into download mode so ... i still think it's simply the button wich is stuck :x
LAST EDIT:
Ok, so after 10min connected to usb (and looping) it suddently ... stopped to loop... and just i started it normaly ...
but
exactly now, when i'm writing this, the phone just restarted and went back to 'loopboot' mode
BUT
when i'm about to send the message ... it stoped to loop and i'm starting it normaly ... >_<
Ok, now 10 minutes it started normaly, 98% percent charge.
No sim inserted,no SD card, if i try to open the parameters, it open for 1/2 second then close and send me back to main menu.
Every other app seems to work normaly. (Text, internet, file explorer).
I'm going to wait a bit more then try to insert SIM and SD and reboot.
EDIT: Trying to open any "Parameter" related thing bring me back to main menu (as "Connected as" or long press the Wi-Fi etc ...).
I can activate wifi and it works ... it seems it's only the GUI xD (Maybe it's normal while not having SIM card, i never tried to run my phone without one :x )
definitely hardware buttons issue.
Ok, so after this it worked like a charm for few days, and now, bootloop again \o/
It seems to happend when the phone is down because of low batery :/
I opened it, and removed the "power" button ... still the same. it seems it's not comming from there :/
Any idea ? :x
3h it bootloops
Any idea please ?
The phone is comming back from support
Return faulty repair
jje
JJEgan said:
The phone is comming back from support
Return faulty repair
jje
Click to expand...
Click to collapse
Ok, thank you, any way the see the phone is rooted ? :x
Minoui said:
Ok, thank you, any way the seey the phone is rooted ? :x
Click to expand...
Click to collapse
Yes see the return to stock for warranty post.
jje
Hi guys. I have seen and read through plenty of the same problems regarding the bootloop issue on the forum. I seem to be stuck somewhere different so I post this question. I hope someone can help.
I have a standard S3 I-9305 LTE in South Africa. Not rooted before or any mods. But somehow it started bootlooping a couple of weeks ago. I read and implemented the Recovery Mode- Cleared the cache and then rebooted, and it worked, plenty of times.
But now it has gone into a solid bootloop and i cannot access recovery mode. So read up about Download mode and installed Odin, Kies and the Cf Root file on my PC.
Now when I enter Download mode on the phone, and continue( press Volume Up) after the warning, the device restarts again. This I have done a hundred times and each time removing battery and waiting a couple of minutes. So essentially I cannot get Download mode to function but I do have access to it.
So this I know, this is a software , possible ROM problem, NOT hardware as the device worked perfectly after bootloop issue started.
I did the latest Firmware Upgrade to Android 4.2( i think, i r noob in this) yesterday. This was done on the phone itself under About-check-firmware. The Phone worked fine afterwards but then went into this never ending tormenting bootloop without yielding.
I live far from a proper service centre and I need my phone for work, thus very urgent.
I also have checked if the power button is stuck but it is not.
I am prepared to root the device and install any other ROM, Flash anything that can get me back on.
Any advice please?
Thanks in advance
Report your own post and ask a moderator to move it to the i9305 q&a forum.
Sounds like the emmc chip is corrupt or damaged, you may require a new motherboard.
Try plugging your phone into pc before you access download mode, remove the battery before you press volume up.
Sent from my GT-I9300 using Tapatalk
Caution and thanks
boomboomer said:
Report your own post and ask a moderator to move it to the i9305 q&a forum.
Sounds like the emmc chip is corrupt or damaged, you may require a new motherboard.
Try plugging your phone into pc before you access download mode, remove the battery before you press volume up.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hi Boom,
I have seen you have diligently answered many queries, please to be cautious saying it is a motherboard or hardware issue, it makes peoples heart sink before trying other avenues first. But don't get me wrong, the fact that you took the time to answer me makes you my hero. :good: And thanks.
I will try the other option you gave as I know the phone is fine the answer is just a few tries away.