Related
Hey Guys, All of a sudden after flashing a couple of roms my back button spontaneously starting acting weird. It randomly "activates" and takes me back and vibrates whenever the phone is turned on. Has anyone seen this before? I've tried flashing a bunch of firmwares, and doing factory resets but nothing helps. Any ideas on how to clear the phone and reset it fully?
foxfire235 said:
Hey Guys, All of a sudden after flashing a couple of roms my back button spontaneously starting acting weird. It randomly "activates" and takes me back and vibrates whenever the phone is turned on. Has anyone seen this before? I've tried flashing a bunch of firmwares, and doing factory resets but nothing helps. Any ideas on how to clear the phone and reset it fully?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=798461
Click to expand...
Click to collapse
Go to the last page, there should be someone commenting on flashing the Touch HW again; basically you just use SGS's tools with your original firmware and then flash the Touch HW drivers again.
Check that topic and read throughout it.
foxfire235 said:
Hey Guys, All of a sudden after flashing a couple of roms my back button spontaneously starting acting weird. It randomly "activates" and takes me back and vibrates whenever the phone is turned on. Has anyone seen this before? I've tried flashing a bunch of firmwares, and doing factory resets but nothing helps. Any ideas on how to clear the phone and reset it fully?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=798461
Had the same problem, this seemed to fix it
Sent from my GT-I9000M using Tapatalk
Nope.... tried messing with the buttons in recovery mode and even flashing the firmware inside SGS tools. Nothing works. I still think it's a software issue because If I do a key test in CWR the button works like it should. =/ Hoping for some other ideas. Thanks for your help though.
foxfire235 said:
Nope.... tried messing with the buttons in recovery mode and even flashing the firmware inside SGS tools. Nothing works. I still think it's a software issue because If I do a key test in CWR the button works like it should. =/ Hoping for some other ideas. Thanks for your help though.
Click to expand...
Click to collapse
Hmm. Just out of curiosity what are the versions of "phones touch key" and "parts touch key" in SGS Tools?
Sent from my GT-I9000M using Tapatalk
I already boxed up the phone and sent it back to the seller for warranty replacement but I think it was something like 0x02, and the version to update was 0x2. Does that make sense? I tried updating both, and SGS tools said the update was successful, but it didn't fix the problem.
Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!
KoolKid98189 said:
Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!
Click to expand...
Click to collapse
Can you enter download mode?
robintjeuuu said:
Can you enter download mode?
Click to expand...
Click to collapse
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.
KoolKid98189 said:
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.
Click to expand...
Click to collapse
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.
robintjeuuu said:
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.
Click to expand...
Click to collapse
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(
KoolKid98189 said:
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(
Click to expand...
Click to collapse
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.
robintjeuuu said:
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.
Click to expand...
Click to collapse
And I don't think Samsung will repair it as my warranty is void and I doubt if my parents would get me a new phone as this phone is only 3 months as well! And I have seen an unbrick thread and I tried it and it didn't work :'(
Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk
robintjeuuu said:
Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
My dad took it to the service centre and they said they can't fix it as it's rooted so I'm screwed :'(
sunny296 said:
thanks,this index help me out very much.
Click to expand...
Click to collapse
What do you mean?
Zamoro1 said:
it is not samsung galaxy problem. it was your problem. you must close your downloading and other working while it is on charging.
Click to expand...
Click to collapse
It wasn't downloading anything?
Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.
Mine also dead
KoolKid98189 said:
Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.
Click to expand...
Click to collapse
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?
PelosBi said:
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?
Click to expand...
Click to collapse
Well mine was dead for a day then I plugged it into the charger (this was after a day and I left it on charge all night and it wouldn't start) and I held the power button for 10 seconds while it was on the charger it showed offline charging so I let it charge for a bit and then I powered it on and it seemed to be bricked so I sent it to a phone repair shop (not Samsung as my warranty is void). If it doesn't show any signs of life then it's bricked. If it comes to life then it is also probably bricked. I tried flashing many recoveries, ROMs, kernels and params and nothing happened.
In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.
james.faction said:
In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.
Click to expand...
Click to collapse
I tried to flash stock ROM and recovery but nothing actually worked!
1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.
james.faction said:
1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.
Click to expand...
Click to collapse
I tried those solutions and they didn't work.
Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.
james.faction said:
Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.
Click to expand...
Click to collapse
I read all instructions, and when I flashed it via Odin, nothing actually changed even with the params!
Guys,
I have flashed 2 or 3 times my lt30p with different lt30p official roms but i still cant pass trough the green led (flash mode).
for a minut or 5 i have a red led and than it is going in flash mode.
I have already reset the memory chip and try every thing in the first post from http://forum.xda-developers.com/showthread.php?t=1849170
Can somebody help me to get out of this?
cheers
samm000 said:
Guys,
I have flashed 2 or 3 times my lt30p with different lt30p official roms but i still cant pass trough the green led (flash mode).
for a minut or 5 i have a red led and than it is going in flash mode.
I have already reset the memory chip and try every thing in the first post from http://forum.xda-developers.com/showthread.php?t=1849170
Can somebody help me to get out of this?
cheers
Click to expand...
Click to collapse
so you have tried using flashtool in flashmode to flash a stock ftf file? if so I think its a sony repair my friend.
bruce1x said:
so you have tried using flashtool in flashmode to flash a stock ftf file? if so I think its a sony repair my friend.
Click to expand...
Click to collapse
Not. Exact, first i had problems with the rom i could not use ti without a charger.
Then i wasnt at home zo THE battery was drain to 0% and i could not. start iT up.
Zo i tried other Roms to solve My problem, now im still stuck on THE same problem
THE Phone is stuck in flashmode. Of someone knows à trick to help me pls.
samm000 said:
Not. Exact, first i had problems with the rom i could not use ti without a charger.
Then i wasnt at home zo THE battery was drain to 0% and i could not. start iT up.
Zo i tried other Roms to solve My problem, now im still stuck on THE same problem
THE Phone is stuck in flashmode. Of someone knows à trick to help me pls.
Click to expand...
Click to collapse
so is your battery dead, wont charge at all, will it hard reset.
bruce1x said:
so is your battery dead, wont charge at all, will it hard reset.
Click to expand...
Click to collapse
I have try hard reset but i can only do that when the phone is on charger.
I dont know if that make some difference?
samm000 said:
I have try hard reset but i can only do that when the phone is on charger.
I dont know if that make some difference?
Click to expand...
Click to collapse
I'm not sure about this one but if the phone was mine I would try to flash a stock kernel ftf with flashtool. it might be you flashed something bad and things got corrupted. and if the phone is stuck like this your phone will probably not charge, so the battery is dead. in which case you cannot flash an entire rom. try to flash only the kernel from this using flashtool. .
http://forum.xda-developers.com/showthread.php?t=2647207
if this works then place your phone on charge for a few hours.
then reflash the entire stock ftf.
if none of this works I'm not sure what else you can try. good luck!
bruce1x said:
I'm not sure about this one but if the phone was mine I would try to flash a stock kernel ftf with flashtool. it might be you flashed something bad and things got corrupted. and if the phone is stuck like this your phone will probably not charge, so the battery is dead. in which case you cannot flash an entire rom. try to flash only the kernel from this using flashtool. .
http://forum.xda-developers.com/showthread.php?t=2647207
if this works then place your phone on charge for a few hours.
then reflash the entire stock ftf.
if none of this works I'm not sure what else you can try. good luck!
Click to expand...
Click to collapse
thnx i already have try that, it didnt help me out.
But i have solved my problem now with bypassing the protection in the circuit of the battery link
problem solved phone is working and battery too
cheers
samm000 said:
thnx i already have try that, it didnt help me out.
But i have solved my problem now with bypassing the protection in the circuit of the battery link
problem solved phone is working and battery too
cheers
Click to expand...
Click to collapse
good news, nice to now how to fix this, happy modding my friend.
bruce1x said:
good news, nice to now how to fix this, happy modding my friend.
Click to expand...
Click to collapse
thnx bro
i hope i can help others to solve there problem to
cheers
samm000 said:
thnx i already have try that, it didnt help me out.
But i have solved my problem now with bypassing the protection in the circuit of the battery link
problem solved phone is working and battery too
cheers
Click to expand...
Click to collapse
I have had this exact same problem for months now and thought I tried everything. But I guess not.:good: Just wondering what you did after you completed the wiring on the battery. Did you charge it for a certain amount of time,before turning it on? Did you have to flash a stock rom? Any input would be very helpful. Thanks
WarSupport said:
I have had this exact same problem for months now and thought I tried everything. But I guess not.:good: Just wondering what you did after you completed the wiring on the battery. Did you charge it for a certain amount of time,before turning it on? Did you have to flash a stock rom? Any input would be very helpful. Thanks
Click to expand...
Click to collapse
I have first charge the battery till it wass fullcharged and than i have flashed a new rom
Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)
Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse
Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.
alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?
Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia
akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.
Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Nevermind, I got it backed up and restored it.
rodolfoakira said:
Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Click to expand...
Click to collapse
If anyone had the same problem, I hope you guys had a backup file on TWRP, which restores almost everything but the bootloader logo from the other kernel.
Good news, the problem was solved just with the Recovery Mode. It needed to get into the bootloader, which was only possible after the battery died.
rodolfoakira said:
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
Click to expand...
Click to collapse
Holding the power button for 20 seconds or so didn't work?
No it didn't. Unfortunatelly. D:
unwired said:
Holding the power button for 20 seconds or so didn't work?
Click to expand...
Click to collapse
No it didn't. Unfortunatelly. D:
No commands were working at the time. Just the frozen bootloader screen from the wrong kernel. When the battery died, after some 5 minutes or so of charge I managed to turn it on on the bootloader and put it on recovery mod. Wow, I killed all my nerves, thinking I lost my close-to-new phone. Then backup saved my day!