Database Develop

Returning a bricked phone

So, I have successfully bricked my phone (not by choice). I am a long time WinMo user and I have never even come close to bricking a phone. Today was exactly one week from when I bought my first android phone and I bricked it.(not blaming android, I love android)
I have tried EVERYTHING, to no avail.
My phone is on the phone++!++computer screen.
So, first thing tomorrow morning, I am headed to the AT&T store for replacement (I will act dumb and get the phone).
My questions are -
1.Will my information (contacts,emails,etc.) on the phone be checked or in any way violated?
2.If they do find out that I had rooted the phone, after I have already walked out of the store, can they do anything about it?

1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".

TehDave said:
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
Click to expand...
Click to collapse
I have tried everything. I don't want to return this phone, but there is no option left.
None of the methods work and I am pretty experienced in this stuff. So, its not that I am messing up on the methods, its just that there was a batch of phones that had the key combos disabled.

Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.

ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
I can tell you that by flashing ONLY the pit file in odin another user and myself were able to succesfully make the phone unresponsive to all buttons, all methods and all pulls of the battery. it literally turned into a brick...then again i would call this an illegitimate method after realized how simple it is now. as long as i can get power to the phone thou i have to agree ive been able to save it every time now

ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
Seriously?
I was up for six hours last night trying to fix the damn thing. I don't want to replace the phone just because I want to beat the system. I have never ran into problems when I am modding. I always figure it out, but when the phone is absolutely unresponsive to all keys, what am I going to do?
Anyways, this thread can be closed now.

That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216

seems pretty complicated to flash this phone. My last one-Nokia N900- is very easy to work with. It never get bricked.

alec5216 said:
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
Click to expand...
Click to collapse
I tried that too, nothing. I got it exchanged. No hassle.
AT&T store rep just said the phone will be factory reset and there is nothing to it.
Anyway thanks for the help folks, really appreciate it.
Lets hope, I don't bust this one because the phone I just got is also impervious to key combos. I tried getting into recovery (just for the heck of it), it didnt work with the keys, had to do it with "adb reboot recovery".

[Q] Xperia Tl Bricked won't turn on QHSUSB driver?

Okay, how about this one?
My phone WAS stuck in one of these infamous boot loop/battery thingys, but I just removed the battery and charged it with an external RC Battery charger ($60, charges EVERY type of battery, everyone should have one). When I put it back in, everything was great. I then used Flashtool to unlock the bootloader without problem. Then I went to flash a stock ROM to the thing via flashtool and left it go. When I came back, flashtool had completed the operation without errors, and had last told me to reset the phone. The phone, however, wouldn't turn on or respond AT ALL to anything I did. So I took the battery out and charged it, thinking it must just have run out of power but upon putting the battery back in, the phone remained unresponsive.
No modes, no lights, nothing. The ONLY thing that happens is if I have the thing plugged into the PC and I hold the UP (maybe the DOWN, i don't remember) button, the PC detects and tries to find drivers for something called QHSUSB_DLOAD... qualcomm High Speed USB download drivers, maybe? I've looked around and somewhere someone said that for another Xperia (don't remember which one) THEY had read that you could get the phone into flashboot mode somehow once installing the drivers. They supposedly come with the "gordon's" USB tools or whatever the heck it's called, but I couldn't get xp to accept anything included with gordon's as a proper driver. Yes, I know I had to INSTALL gordons, since an exe sure isn't a driver.
I've also found that, at least for the Galaxy 2, once you're at a point where it's asking for QHSUSB_DLOAD drivers, there's nothing you can do short of JTAG repair. However, as my friend so succinctly put it, "That's not a galaxy, it's an xperia" so I'm still holding onto hope. Anybody have any ideas? Or where I could find a QHSUSB_DLOAD driver and what to do with it then? I AM planning on getting a jtagger soon, so maybe this'll be the reason I finally do.

1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium

xperia
gregbradley said:
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) Are you sure of that? I mean, it even has a BUTTON for it... it just automates the flashboot thingy if I remember correctly... the thing is, when I was writing my post, I wasn't sure if I was confusing this phone with another I was working on right then... but, no I'm pretty certain I did it through flashboot. Maybe not. Anyway, it wouldn't have even let me flash if my bootloader was locked still, right?
2) Haha- I'm afraid that's not really possible, BUT I already have PC companion installed and it was working fine. (Can you unlock your bootloader through PC companion? Maybe THAT's what I did- I KNOW I didn't do it through the command prompt, though...)
3) Okay, I am actually trying this as we speak, though I did take the battery out and charged it fully already
4) PC Companion installed
5) asks for QHSUSB_DLOAD driver, never vibrates
6) I wish
7)done
8) does nothing
9) Okay, so I will allow that perhaps there are things going on that all the uninstalling and reinstalling would fix and so I will try it out on a clean computer here in a little bit, but I don't think I'm gonna have any luck. I'll let you know what happens...

1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium

greg,since 23rd February 2013 you can unlock BL via flashtool.You should know that...
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
Click to expand...
Click to collapse
http://www.flashtool.net/changelog.html

AFAIK that is just for the devices it could unlock before (2012 and before), not the newer devices that it could never unlock such as ours.
Sent from my LT30p using xda premium

gregbradley said:
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) http://news.softpedia.com/news/Sony...ts-Flash-Tool-for-Xperia-Devices-315706.shtml - no wait, that just says it's supported by flashtool. I'll keep looking. I could tell you real easy if my bootloader was unlocked or not, but the thing wont turn on Would flashtool have offered me the bootloader unlock button if it didn't support it for my device? It tells me how to get to flashmode erroneously (for MY model, not most) but I figured it just wanted me in flashmode so I put the phone in flashmode. Hell, maybe I never unlocked the bootloader and just tried flashing a stock rom... would flashtool have allowed me to try and flash a non-stock rom with an unlocked bootloader? Would THAT have bricked the phone? I'm gonna go see what the rom I flashed was called now....
2) yeah, as I said, I'm doing that right now. though I took the battery out and charged it, so I thought it might work... even still, it's not been on for 24 hours yet as I writing this, so waiting... is there something that being on the charger for 24hours does besides ensure the battery is charged? Calibration or something? I can assure you the battery is fully charged to peak capacity.
3) will do, though when it doesn't work, do you promise that we can try to talk about QHSUSB_DLOAD? I promise that when it DOES work, I'll happily thank you and admit that even though you haven't quite given me a reason WHY, leaving it plugged in for 24 hours did something more than charge the battery. I know that sounds sarcastic, but I really think there's a chance it could but as I said, I can assure you the battery is charged to peak capacity
4) so I call "flashmode" "flash boot" mode- I am quite well aware of the differences between flashmode and fastboot mode. Figured since the one said flash and the one said fast it was obvious. Man, I did my "research", I read the all-in-one thread, as well as others... I've done this to dozens of phones over the last 3 years and just recently an Xperia Play which acquainted me with many of the idiosyncrasies of the Xperia line, flashboot, pc companion, etc... so when, after 3 years I finally actually ASK a question, I start to get this particular brand of close- mindedness... the way you keep not even trying to actually answer my question makes me think you didn't necessarily read my post before offering up a standard "cookie cutter" recipe which you don't necessarily understand enough to see how it might not necessarily apply. My REAL question was about QHSUSB_DLOAD device requiring a driver since that's the ONLY RESPONSE I CAN GET AT ALL from a phone WITH A FULLY CHARGED BATTERY. (you see, there I wanted to say QHSUSB_DLOAD driver, but that's not quite correct- QHSUSB_DLOAD.dll would be a possible name for the driver, but it's really a device called QHSUSB_DLOAD which does not have a driver. See how I'm taking pains to watch my words so as to not promote confusion.)
Cause you're RIGHT, really; using the proper terms IS important, but can you tell me that you SERIOUSLY didn't know what I meant when I said flashboot mode instead of flashmode? Or that you knew what I meant, but you thought that I didn't ? Did I ever confuse the two terms flashboot and fastboot? "there's no such thing as a flashboot"... what a silly-sounding thing to say... anyway, I never said there was- just that there was a flashboot mode. )Anyway, I do appreciate the help, just not the attitude, y'know?

The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
What charging for 24 hours does is to make sure there is some charge in the phone. I am no technical expert here, I am just very good at fault finding and knowing a trick or two that helps. The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc) However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
All I am trying to do is guide you through some fault finding techniques and then give you some advice on things that have worked for people in the past.
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
EDIT
There is still no such thing as flashboot....its called flashmode
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.

i also have this problem.
my xperia TL won't response anything. Plug in to PC it searching for QHUSB_DLOAD driver.
now, phone still in my drawer for 4 month

gregbradley;45518226]The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
Click to expand...
Click to collapse
S'okay. Attitude was a big strong for what I meant, but I couldn't think of the right word at the time...
What charging for 24 hours does is to make sure there is some charge in the phone.
Click to expand...
Click to collapse
Yeah, that's what I had gathered... I just got out of a bootloop by charging the battery with a programmable peak charger, so I KNOW its got a full charge.
The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Click to expand...
Click to collapse
See, right- that's what I always hear everybody say on forurms like this... cause it's TRUE. Most people asking a question generally barely know the proper question to ask and when the DO, they don't think to SEARCH for it. (Although I've always found the Xda forum search EXTREMELY lacking; I'd do a search for a term in the xda search and get nothing so I had to go to google and find the proper xda page through IT. It's much better of late, though)
However, it has been my experience that everything everybody always complains about; people asking before even searching themselves, people asking questions but not providing enough relevant information for the questions to be answered, etc... all these "rules of conduct" are based around the avoidance of WASTED TIME/EFFORT. Which I whole-heartedly agree with. I almost never ask about anything on the forums because it's almost ALWAYS faster to find the answer myself. It's usually out there.. so when I DO post a question, I will give a detailed account of my situation, how I got there and where I'm at... so, with all that everybody says about reading BEFORE you post questions why does it always seem like NO ONE EVER READS MY QUESTIONS before answering? For example, this time I was just like- "wow, dude didn't even read the background, gave me a cookie-cutter set of instructions and didn't even TRY to answer my actual question!"
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc)
Click to expand...
Click to collapse
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service... galaxys don't have flashmode, know what I'm sayin? I'm thinking maybe if I get the QHSUSB_DLOAD driver qpst or (more likely) qxdm will communicate with the port and I can do something like getting it into flashmode or rebuilding it or just figuring out what happened.
Haven't had much luck finding the drivers, but I haven't really looked that hard yet...
However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
Click to expand...
Click to collapse
Sure am. Yeah, what led me to post was when every time QHSUSB_DLOAD was even mentioned by galaxy owners, the immediate consensus was that this always means you're bricked and require JTAG repair service. As you say, not much regarding xperia, although the ONE thing I saw was someone who said that THEY heard something about getting the driver and being able to parlay that up into getting it back into flashmode or fastboot mode but that's about it. I'm gonna keep on it...
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
Click to expand...
Click to collapse
No doubt... it is sometimes hard for me to ask questions because most times I only end up having to bring the person supposed to be helping me up to speed simply to be able to ask the question and have the answer be (usually, but not ALWAYS) "you're guess is as good as mine". I don't mean you, just so you know; I'm speaking of "how it usually goes".
EDIT
There is still no such thing as flashboot....its called flashmode
Click to expand...
Click to collapse
oh, for sure. flashboot MODE, however- well, there's still no such thing, but at least it's not as blatantly misleading
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Click to expand...
Click to collapse
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
Click to expand...
Click to collapse
[/QUOTE]
Yeah, I know; I posted that link thinking it said something other than what it did- like there's gonna be a news article about Sony adding support I edited the post and mentioned that and left the link instead of just deleting it. Dunno why.
All that the Sony flashtool can really do is return you back to stock, right? I think I read something like that...
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?

adol.ivxx said:
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service...
Click to expand...
Click to collapse
Yes, but it only happened the once, a fair few years ago before I really had heard of the problem. That's why I can not be quite sure how I fixed it, but it certainly was nothing more than perseverance of trying different things.
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Click to expand...
Click to collapse
Not for Sony Xperia devices.
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
Click to expand...
Click to collapse
Sorry I could not have been more help. I will continue to dig around and ask others I know that might shed more light on this. I will post here again as when I have something you might appreciate. Good luck.

Ur phone is hardbricked

D415 won't turn on

I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.

rft2149 said:
I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
Click to expand...
Click to collapse
Try this

SubliemeSiem said:
Try this
Click to expand...
Click to collapse
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.

rft2149 said:
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
Click to expand...
Click to collapse
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.

SubliemeSiem said:
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
Click to expand...
Click to collapse
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.

rft2149 said:
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
Click to expand...
Click to collapse
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!

SubliemeSiem said:
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
Click to expand...
Click to collapse
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.

rft2149 said:
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
Click to expand...
Click to collapse
They can easily find out is it rooted or not....................?
If u connect ur phone via usb by pressing vol down button..
U'll enter into download mode..
It clearly says ROOTED.........
But instead u have to try to update phone using B2CAppSetup.exe (official software update tool)

I have a lg d415 it just cut off yesterday n won't turn on i have no clue what to do

Which firmware for unlocked AT&T G Flex on T-Mobile?

Hello all! I work as a smartphone technician and today a gentleman brought an AT&T model G Flex into the shop where I work because the phone had gone into a bootloop and would only cycle the LG logo on and off without booting fully. He told me that the phone had been flashed to T-Mobile some months ago and had been working been working fine until today.
My dilemma is that I'm not sure how to proceed at this point. My first thought is that an AT&T phone probably wouldn't actually have to be "flashed" (as he put it) to T-Mobile, I'm pretty sure it would just have to be carrier unlocked and then have some network settings changed on it. Thus, my first thought is to try using the KDZ or TOT method to restore the stock AT&T firmware, then go about changing the network settings to T-Mobile's again. But now I'm second guessing myself and wondering if maybe it does actually need the T-Mobile rom or even just the radios flashed to it?? Unfortunately, I'm not much of an expert on GSM networks or even LG software. Generally I deal much more with hardware. Any advice from the LG community would be greatly appreciated!

Oface82 said:
Hello all! I work as a smartphone technician and today a gentleman brought an AT&T model G Flex into the shop where I work because the phone had gone into a bootloop and would only cycle the LG logo on and off without booting fully. He told me that the phone had been flashed to T-Mobile some months ago and had been working been working fine until today.
My dilemma is that I'm not sure how to proceed at this point. My first thought is that an AT&T phone probably wouldn't actually have to be "flashed" (as he put it) to T-Mobile, I'm pretty sure it would just have to be carrier unlocked and then have some network settings changed on it. Thus, my first thought is to try using the KDZ or TOT method to restore the stock AT&T firmware, then go about changing the network settings to T-Mobile's again. But now I'm second guessing myself and wondering if maybe it does actually need the T-Mobile rom or even just the radios flashed to it?? Unfortunately, I'm not much of an expert on GSM networks or even LG software. Generally I deal much more with hardware. Any advice from the LG community would be greatly appreciated!
Click to expand...
Click to collapse
Can you boot into recovery? Save a nandroid back up and reflash?
I think its pretty safe just to reset it and start fresh.
Sim unlock is pretty simple, if it actually needs it....

Supertacomonkeyexplosion said:
Can you boot into recovery? Save a nandroid back up and reflash?
I think its pretty safe just to reset it and start fresh.
Sim unlock is pretty simple, if it actually needs it....
Click to expand...
Click to collapse
Turns out I had it backwards, it is actually a T-Mobile that was being used on ATT but no matter. Turns out I can't get it to boot to download mode or recovery mode anyway. I must have tried holding volume up with the phone off while plugging in the usb 50 times today. No luck. All I can get it to do is bring up the hard reset option, which I have tried to no avail. Any ideas on how to get this thing into download mode? Really appreciate you taking the time bud

Oface82 said:
Turns out I had it backwards, it is actually a T-Mobile that was being used on ATT but no matter. Turns out I can't get it to boot to download mode or recovery mode anyway. I must have tried holding volume up with the phone off while plugging in the usb 50 times today. No luck. All I can get it to do is bring up the hard reset option, which I have tried to no avail. Any ideas on how to get this thing into download mode? Really appreciate you taking the time bud
Click to expand...
Click to collapse
Plug it into your computer, try and get it to show up on your device manager. If you can get it to show up you can use the lg flash tool.
Download mode is holding volume up as you plug your phone into your computer .
Its strange how it would just all of a sudden loop.
I forgot to ad that I think recovery mode has a "black" screen. Not 100 percent sure on this , someone correct me if I'm wrong. Also there may be a better solution over in the LG G2 section of XDA. Software is pretty much the same as the flex.
Wish I could be more help.

Oface82 said:
Turns out I had it backwards, it is actually a T-Mobile that was being used on ATT but no matter. Turns out I can't get it to boot to download mode or recovery mode anyway. I must have tried holding volume up with the phone off while plugging in the usb 50 times today. No luck. All I can get it to do is bring up the hard reset option, which I have tried to no avail. Any ideas on how to get this thing into download mode? Really appreciate you taking the time bud
Click to expand...
Click to collapse
Found this over in the G2 section. Hopefully you don't have to deal with all of this.....
http://forum.xda-developers.com/showthread.php?t=2582142
If you could get your computer to recognize the phone , it will be a ton easier for you.

Ha! It worked! Really appreciate all the trouble you went to finding that for me sir!

Oface82 said:
Ha! It worked! Really appreciate all the trouble you went to finding that for me sir!
Click to expand...
Click to collapse
Sweet. What solved it?
Update your OP in case anyone else is having the same problem. Help has been really rare around here lately.
Glad you got it.

Is there any hope? (hard bricked...)

Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.

My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help

jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change

Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone

Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??

____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.

flash -61