my htc one unlocked is hard bricked while i was surfing in phone, suddenly it power offed without warning and never boot again yet, i tried all combinations like power and vol-+, bright light censor, nothing worked.
windows 8 device manager recognize device as "Qualcomm HS-USB QDLoader 9008(com3)"
my phone is in warranty and is unlocked bootloader and rooted with venom rom
will htc know that its rooted or bootloader unlocked, if i give for service????? coz its not booting.
will htc change motherboard in warranty for free????
Mmm it depends. You could be lucky. They may just swap over the entire phone. But if they manage to fix that phone and see it's unlocked warranty is void. You will never know until you try!
slowy77 said:
my htc one unlocked is hard bricked while i was surfing in phone, suddenly it power offed without warning and never boot again yet, i tried all combinations like power and vol-+, bright light censor, nothing worked.
windows 8 device manager recognize device as "Qualcomm HS-USB QDLoader 9008(com3)"
my phone is in warranty and is unlocked bootloader and rooted with venom rom
will htc know that its rooted or bootloader unlocked, if i give for service????? coz its not booting.
will htc change motherboard in warranty for free????
Click to expand...
Click to collapse
Nah, warranty void point blank period. You get nothing at all? Even if you try to power on plugged in to a USB 2.0, have had this work in past don't know why. If you can't get it to do anything at all you are looking at buying a new phone, or insurance claim it.
nateboi81 said:
Mmm it depends. You could be lucky. They may just swap over the entire phone. But if they manage to fix that phone and see it's unlocked warranty is void. You will never know until you try!
Click to expand...
Click to collapse
if they change the motherboard then how they come to know that it was unlocked bootloader???
i have heared that change motherboard is only solution
Was reading another thread, don't know if this works they day it does, try shining a bright light at the sensor while powering on. Hey it's worth a shot.
MrLizm said:
Was reading another thread, don't know if this works they day it does, try shining a bright light at the sensor while powering on. Hey it's worth a shot.
Click to expand...
Click to collapse
already did it, and mention in OP, not working
See that now, sorry. Put my m7 through hell and back never seen it just crap out. At a loss for suggestions.
slowy77 said:
already did it, and mention in OP, not working
Click to expand...
Click to collapse
this is your only hope
http://forum.xda-developers.com/showthread.php?t=2770684
it worked for me and many others
clsA said:
this is your only hope
http://forum.xda-developers.com/showthread.php?t=2770684
it worked for me and many others
Click to expand...
Click to collapse
i tried, but device not conneted error msg appearing.
it shows QDL mode while giving command "lsusb"
slowy77 said:
i tried, but device not conneted error msg appearing.
it shows QDL mode while giving command "lsusb"
Click to expand...
Click to collapse
if that does not work your stuck ...send the phone in for repair
MrLizm said:
See that now, sorry. Put my m7 through hell and back never seen it just crap out. At a loss for suggestions.
Click to expand...
Click to collapse
MrLizm said:
See that now, sorry. Put my m7 through hell and back never seen it just crap out. At a loss for suggestions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2770684
the above is an excellent work to revive the hard brick M7. But in case your M7 shows detected as modem ( its unrecoverable), i had to sell mt bricked phone as it was detected as an QC modem driver. Else the revive.sh should work ok .
Also one more thing. I guess HTC service center don't do a jtag to revive bricked devices in the india service centres. At most they try revive with their flash tools, most likely ( again most likely) they should treat it as a bad motherboard case. And you might get the motherboard replaced without the whole bootloader unlock thing. . Give it a try. If they ain't able to boot it they wont find you had tampered with your device.
I don't know why htc devices just die on the QC S 600 boards just like that. S4 with same hardware doesn't. Their version of S-boot (samsung's boot loader) seems more robust, at least doesn't leave you with unbootable state. . Mine died on a stock build with no tempering whatsoever just the way you told.
Now again it went to the boot loop just like that !!!
Related
i have xz and tried to flash Rom and when i finish(i use cwm recovery) i marked -stop recovery fix-and that's was my biggest problem the mobile is now dead and working when i try to run it its just don't work its can not charge-no led light-and when i connect it to my pc its just not read and nothing happen i have unlocked boot loader
i need help plzz :crying::crying::crying::crying:
alimohmmed said:
i have xz and tried to flash Rom and when i finish(i use cwm recovery) i marked -stop recovery fix-and that's was my biggest problem the mobile is now dead and working when i try to run it its just don't work its can not charge-no led light-and when i connect it to my pc its just not read and nothing happen i have unlocked boot loader
i need help plzz :crying::crying::crying::crying:
Click to expand...
Click to collapse
Flashing your phone can't damage it physically, the problem must be another thing, tro to restore it with Sony Update Service, also i don't understand your charging problem but if it's not charging maybe you damaged your phone or it's not correctly detected on windows. try to reinstall all drivers just in case.
same
QualQuek said:
Flashing your phone can't damage it physically, the problem must be another thing, tro to restore it with Sony Update Service, also i don't understand your charging problem but if it's not charging maybe you damaged your phone or it's not correctly detected on windows. try to reinstall all drivers just in case.
Click to expand...
Click to collapse
thanks for the replay,my mobile is not charging and when i press the power button and vol+ its not working at all
i cant use sus because it cant be recognize and i tried to reinstall the drivers and nothing happen
alimohmmed said:
thanks for the replay,my mobile is not charging and when i press the power button and vol+ its not working at all
i cant use sus because it cant be recognize and i tried to reinstall the drivers and nothing happen
Click to expand...
Click to collapse
Ok so maybe it's your USB cable, have you tried with another one?
If it's the same with another USB cable i have bad news for you...
alimohmmed said:
i have xz and tried to flash Rom and when i finish(i use cwm recovery) i marked -stop recovery fix-and that's was my biggest problem the mobile is now dead and working when i try to run it its just don't work its can not charge-no led light-and when i connect it to my pc its just not read and nothing happen i have unlocked boot loader
i need help plzz :crying::crying::crying::crying:
Click to expand...
Click to collapse
unfortunately similar to hard-bricked
and u cannot easily repair it unless u be so lucky
take to professional service center
:good:
x102x96x said:
unfortunately similar to hard-bricked
and u cannot easily repair it unless u be so lucky
take to professional service center
:good:
Click to expand...
Click to collapse
Even a hard-bricked phone should charge no?
QualQuek said:
Even a hard-bricked phone should charge no?
Click to expand...
Click to collapse
No charge
No LED
No USB connectivity
Hard-Brick (if i m correct) is some problems both in software and hardware
maybe problem on kernel, bootloader, recovery or in hardware part problem in power & etc.
x102x96x said:
No charge
No LED
No USB connectivity
Hard-Brick (if i m correct) is some problems both in software and hardware
maybe problem on kernel, bootloader, recovery or in hardware part problem in power & etc.
Click to expand...
Click to collapse
Yep you're right, brick is a literal term, it turns your device into a paperweight, AKA A brick.
Bricking a device goes beyond the actual components. You can brick ANY electrical device through MANY means. Bricking, in short often relates to some process that will often permanently destroy your device software-wise. It is often unrepairable except for that usual rare method that MAY save the device.
Bricking usually involves the firmware of a device and the very hidden memory that is often carried over through hard resets and such. Think of it like the "Brain" of your device. If it gets ever so slightly tampered with in the wrong way (such as a flash, which would be the equivalent of brain surgery here) it can be permanently damaged forever.
then what should i do
then what should i do
if i send it to sony service center will they know if it unlocked
and i left it for a full night on charging i have tried every thing i know but still not working
what should i do :crying::crying::crying:
alimohmmed said:
then what should i do
if i send it to sony service center will they know if it unlocked
and i left it for a full night on charging i have tried every thing i know but still not working
what should i do :crying::crying::crying:
Click to expand...
Click to collapse
Many stores offer to repair hard-bricked phones for some bucks, jut take a look in google...
http://forum.xda-developers.com/showthread.php?p=40145013
Hi guys, I have the non-lte One running on 2.24.707.3. Today, I restored my stock nandroid (4.2.2) and then tried the rumrunner s-off (rumrunner_m7_2.24.401.1). It worked, and I was successfully s-off, superCID on hboot 1.54. I then flashed a modified hboot(descenpet_HBOOT_1.54_2.24_MOD) to remove the red warning. All went well. Later, while I was recieving a call, the phone got hung up, so I did a reset (holding the power + vol down buttons). The phone got switched off, but never booted back up.. I tried holding the power + vol down buttons but even the buttons aren't flashing.. Connecting it to my pc makes no connection sounds, and again holding the combo makes no difference. The charging light also doesn't light up. Please tell me what I should do, and whether it is a hard brick or soft brick. Thanks in advance.
Just press and hold the power button on it's own and see if anything happens
EddyOS said:
Just press and hold the power button on it's own and see if anything happens
Click to expand...
Click to collapse
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
n1234d said:
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
hapticc said:
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
Click to expand...
Click to collapse
I used a modded hboot to remove the red warning, have a look at this page (http://forum.xda-developers.com/showthread.php?t=2316726)
To do an RUU, I need to reboot in fastboot, but I can't even get the phone to charge.. Of course adb doesn't detect it..
Another point to note is that I rebooted several times after flashing the modded hboot, and it worked all those times, so this is just random... :'(
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
EddyOS said:
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
Click to expand...
Click to collapse
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
If it's not booting up , and you're stuck in that QDLOAD thing, it's usually the mainboard that's fried and HTC replaced the mainboard in my Sensation under the warranty when it happened to me. I was S-OFF at the time as well, and it came back 100% stock and working
n1234d said:
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
good luck buddy btw to remove tampered i just ran indian ruu
n1234d said:
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Ok, thanks for the info.. Maybe I'll make a strong case. My phone was originally replaced with a new one within a week because of battery problems, and scratch marks that I didn't make.. Then the second one had its mobo replaced for that same battery problem, and now I was going to send this in for replacement because my lower speaker is louder than the upper, and my camera has the dreaded pink tint and my phone has a big gap on its side where the service center guys hadn't closed the phone properly..and now this.. Oh boy, am I gonna make a strong case!!
Sent from my iPod touch using Tapatalk
nkk71 said:
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Click to expand...
Click to collapse
Yeah, I haven't got any alarms to save me now ;'/
But mine did get bricked randomly..
Sent from my iPod touch using Tapatalk
How about I try this?
http://unlimited.io/qhsusbdload.htm
As it doesn't mention the One I'd say no
EddyOS said:
As it doesn't mention the One I'd say no
Click to expand...
Click to collapse
Oh well, I went ahead and tried it anyways, but nothing happened.. So back to my good ol Nokia for now.. Btw, does rumrunner work with hboot 1.55??
Sent from my iPod touch using Tapatalk
Not yet, no
I bet we'll be seeing a lot more of these threads now...
Okay, although I've read a lot and I've learnt quite some bit, I want to know that if it wasn't the phone that unexpectedly died, was it my mistake somewhere? So I'll start with what I did, step by step, please have a look and tell me if I did anything wrong
1. Originally on ViperOne, tampered and unlocked on hboot 1.54
2. Restored stock nandroid 4.2.2 (2.24.707.3)(India) unrooted
3. Downloaded rumrunner (the version that I previously mentioned)
4. Started the exe
5. Phone reboots 2-3 times, process completes at pouring(3)
6. Reboot to verify s-off
7. Restore ViperOne nandroid
8. Run Revone to reset tampered flag
9. Flash modified hboot to remove warning.. Succeeds, reboot to verify warning gone
10. Reboot like 5-6 times to admire at the bootloader
11. I got a call and my phone hung
12. Reset the phone by holding power+vol down
Aaand the phone never booted again..
Sent from my iPod touch using Tapatalk
crixley said:
I bet we'll be seeing a lot more of these threads now...
Click to expand...
Click to collapse
Lol yeah.. I wouldn't think of myself as a total douche though, maybe I missed something..
Sent from my iPod touch using Tapatalk
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!
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
linasj said:
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
Click to expand...
Click to collapse
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
wmosquini said:
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
Click to expand...
Click to collapse
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
linasj said:
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
Click to expand...
Click to collapse
But in time to take the assistance, you said what about it? The unit stopped working alone?
wmosquini said:
But in time to take the assistance, you said what about it? The unit stopped working alone?
Click to expand...
Click to collapse
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
linasj said:
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
Click to expand...
Click to collapse
Legal, tomorrow I will even take the guarantee to solve as fast as possible. Really the device not the sign of life at all. I will inform you that the device was carrying at night and just when I catch him in the morning, he was like that.
Thank you for your help. : D
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
bacitoto said:
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
Click to expand...
Click to collapse
hard reset does not remove all traces of root. There is RCT checking. u can be sure that have no traces of root when RCT was reset. On kit kat we have chance to reset it without reflashing. But on 5.0 only reflash
---------- Post added at 11:17 ---------- Previous post was at 11:11 ----------
wmosquini said:
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
Click to expand...
Click to collapse
Did u flash it from 5.0 or 4.4? This problem may have solve without service center. But if u have warranty, it must not worry u.
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
No, I don't think I ever got this message.
Sent from my LG-D405N using XDA Free mobile app.
pick.orion said:
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
Click to expand...
Click to collapse
In my case, the device did not care and neither carried, gave no sign of life. I sent him for assistance in less than one week they made the repair by warranty.
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
LATOKYO said:
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
Click to expand...
Click to collapse
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
alray said:
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
Click to expand...
Click to collapse
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
LATOKYO said:
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
Click to expand...
Click to collapse
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
But why? It was completely fine yesterday. The battery was perfect. Why does it completely fail after I do the RUU?
alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
There needs to be a way to solve this issue. It cannot be coincidental that it just fails now.
LATOKYO said:
But why? It was completely fine yesterday.
Click to expand...
Click to collapse
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
The battery was perfect. Why does it completely fail after I do the RUU?
Click to expand...
Click to collapse
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
alray said:
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
Click to expand...
Click to collapse
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
LATOKYO said:
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
Click to expand...
Click to collapse
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
alray said:
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
Click to expand...
Click to collapse
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
LATOKYO said:
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
Click to expand...
Click to collapse
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on.
Click to expand...
Click to collapse
Yep and in some cases also went back again in dload mode later....
Anyway good luck
alray said:
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
Yep and in some cases also went back again in dload mode later....
Anyway good luck
Click to expand...
Click to collapse
So now when I plug in the device, it says " USB input device"
Good news, bad news?