Database Info

[Q] stuck on lg screen on my lg g2x

i recently got into rooting and setting up my phone for new roms but im still new at it. i ended up bricking my phone to the lg screen with the blue swipe across the screen. my computer will not register the driver to use recovery flasher. i need help. anyone wanna help out a noob?

Try using nvflash to revert back to 2.3.4 I can't give you a link but it's easy to find in the development section

jj_z1 said:
Try using nvflash to revert back to 2.3.4 I can't give you a link but it's easy to find in the development section
Click to expand...
Click to collapse
i tried to use nv flash but no matter what i do i cant seem to make my phone register in the usb driver. if i could make it register i would be able to flash it then.

Did you try using the kdz updater? it's a tricky method, but if you follow the guide properly you should be able to get it going

jj_z1 said:
Did you try using the kdz updater? it's a tricky method, but if you follow the guide properly you should be able to get it going
Click to expand...
Click to collapse
i dont know how to go about it.

laroacha said:
i dont know how to go about it.
Click to expand...
Click to collapse
Never mind my last post, you need to be able to boot into a rom to use kdz updater, it's been a while since I had to do this kind of thing.
I'm pretty sure you only soft bricked your phone (i.e. it still turns on) and the only way, that I know of, is to use nvflash. I've had the same problem before, there could be many things that are causing the phone to not be recognized by your computer. Follow this guide http://forum.xda-developers.com/showthread.php?p=17258229
when you plug the usb into your phone make sure the audio on you computer is loud enough for you to hear that "usb recognized" sound. If you don't hear it, or it does not get recognized, try using a different usb port on your computer, believe me that actually worked for me a couple of times. Also, make sure you follow the steps very carefully because if you use the wrong button combination, or release the buttons too early, it won't work.
I wish I could help you more, but that's all i've got.
Good luck, and if by any chance you get it fixed, don't try to root your phone using any root tools, simply nvflash cwm recovery and flash your choice of a custom rom, that will automatically give you root privileges.

jj_z1 said:
Never mind my last post, you need to be able to boot into a rom to use kdz updater, it's been a while since I had to do this kind of thing.
I'm pretty sure you only soft bricked your phone (i.e. it still turns on) and the only way, that I know of, is to use nvflash. I've had the same problem before, there could be many things that are causing the phone to not be recognized by your computer. Follow this guide http://forum.xda-developers.com/showthread.php?p=17258229
when you plug the usb into your phone make sure the audio on you computer is loud enough for you to hear that "usb recognized" sound. If you don't hear it, or it does not get recognized, try using a different usb port on your computer, believe me that actually worked for me a couple of times. Also, make sure you follow the steps very carefully because if you use the wrong button combination, or release the buttons too early, it won't work.
I wish I could help you more, but that's all i've got.
Good luck, and if by any chance you get it fixed, don't try to root your phone using any root tools, simply nvflash cwm recovery and flash your choice of a custom rom, that will automatically give you root privileges.
Click to expand...
Click to collapse
every time i look at my apx driver it always tells me to troubleshoot but it always says driver not installed. ive downloaded the same driver in different posts just to make sure but nothing helps. Wireless shops are useless. I live in vegas and there isnt a single store with a person smart enough to figure it out.lol. ive given my phone up for days at a time to shops who brag about "WE CAN FIX ANYTHING" they lied. well i guess im going to search for a few more hours on here to get some kind of lead. thanks for the help. if you kknow anything else or figure something out i would appreciate the help.

Have you tried this stuff?
http://forum.xda-developers.com/showthread.php?t=1619932
It sounds to me like your pc's jacked up the driver somehow. Try plugging in the phone with the battery out and holding all 3 buttons, go into your device manager and uninstall all the USB drivers. Then reboot and try following the apx driver installation procedure again.
Sorry if you tried all this stuff a million times already.

I would say the two things that I would focus on would be to first fix the drivers on your computer. I downloaded mine from the LG website. Next is to flash CWM Recovery so you can flash a rooted ROM to your phone. I would go back to the thread where you got the instructions to start flashing and ask the same questions but only after reading the whole thread. There the orig. developer might chime in and you'll have more specific answers focused on your specific issue.
It's true your phone isn't bricked and have patience and you'll get it fixed.
Sent from my LG-P999 using xda premium

superhero7 said:
I would say the two things that I would focus on would be to first fix the drivers on your computer. I downloaded mine from the LG website. Next is to flash CWM Recovery so you can flash a rooted ROM to your phone. I would go back to the thread where you got the instructions to start flashing and ask the same questions but only after reading the whole thread. There the orig. developer might chime in and you'll have more specific answers focused on your specific issue.
It's true your phone isn't bricked and have patience and you'll get it fixed.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
well i have all the drivers needed. and the computer is fine but the phone is not. i mean the pc doesnt quite read the phone right. with that being said i dont know how to flash cwm recovery to a phone my computer cant read. im running windows 7 64bit and all my usb drivers work fine.

CWM = Clockworkmod Recovery (everyone remember this is a newbie).
Important question: Did you do a backup before making any changes to your phone?
Also, try this: remove your phone's battery for 30 seconds. Put the battery back in. Press and hold the volume down button, then press and hold the power button. Hold both buttons. First you'll see the white LG screen, then wait, when you next see the blue LG screen wait ONE second (no longer) then release the buttons. Tell us what the phone does then and what the screen says.

Have you tried taking out your SIM card and micro SD card?
Usually right after I take them out and plug in my phone while holding volume up and volume down... it usually works after that.
Yup, that's my problem. No matter how many USB ports I tried it still wouldn't read it until I took out the SIM card and micro SD ;p.

Try this on for size...
laroacha said:
well i have all the drivers needed. and the computer is fine but the phone is not. i mean the pc doesnt quite read the phone right. with that being said i dont know how to flash cwm recovery to a phone my computer cant read. im running windows 7 64bit and all my usb drivers work fine.
Click to expand...
Click to collapse
Sounds like you are having the same the issues i was having with my phone why dont you try this..... First you have to flash a custom recovery image for your phone, follow all the procedures exactly then once you have flashed your CWM Recovery ( i. e. Clockworkmod recovery) Once you have installed that properly, you can now flash your new custom ROM and that should help to fully reboot your phone back to recovery for you to start using again....... hope that works for you.......just as it did for me have a good one!!... :fingers-crossed:

RVD1 said:
Sounds like you are having the same the issues i was having with my phone why dont you try this..... First you have to flash a custom recovery image for your phone, follow all the procedures exactly then once you have flashed your CWM Recovery ( i. e. Clockworkmod recovery) Once you have installed that properly, you can now flash your new custom ROM and that should help to fully reboot your phone back to recovery for you to start using again....... hope that works for you.......just as it did for me have a good one!!... :fingers-crossed:
Click to expand...
Click to collapse
He can't flash anything to his phone -__- that's the problem we are all trying to solve.

May sound stupid, but have you tried different cords? Maybe your USB cord is bad. Just a thought.
Sent from my LG-P999 using xda premium

@op can you give us screenshots of:
A: what your device manager looks like when you plug your phone in not in apx mode.
And
B: When it is in apx mode.
To do this: right click on my computer>properties>on left hand side, click on device manager. Hit print screen, open paint and tell it to paste. Save and upload here.
Sent from my LG-P999 using xda premium

EEngineer said:
CWM = Clockworkmod Recovery (everyone remember this is a newbie).
Important question: Did you do a backup before making any changes to your phone?
Also, try this: remove your phone's battery for 30 seconds. Put the battery back in. Press and hold the volume down button, then press and hold the power button. Hold both buttons. First you'll see the white LG screen, then wait, when you next see the blue LG screen wait ONE second (no longer) then release the buttons. Tell us what the phone does then and what the screen says.
Click to expand...
Click to collapse
well i brought it to two shops and were both unsuccessful. wireless toyz and smart fix. i have it back and it goes to the lg screen. and instead of the second it flashes from black to a very dim gray back and forth. when i hold the power button along with the volume down it does a master reset and i can press the home button then it takes me to a screen to delete cache partition and what not and you move up and down with the volume keys but i cannot select anything. i think i really messed my phone up.

Somehow you got stock recovery. Google for howbto do a master reset, on devices like the nexus tablet at my work there's a series of steps needed to do a full reset/restore. Just booting into stock recovery may not give you the option. As well, please post those screen shots as I said earlier, this way the issue with the USB can be troubleshot and maybe we can get you a fully working phone with CWM.
Sent from my LG-P999 using xda premium

Волк said:
Somehow you got stock recovery. Google for howbto do a master reset, on devices like the nexus tablet at my work there's a series of steps needed to do a full reset/restore. Just booting into stock recovery may not give you the option. As well, please post those screen shots as I said earlier, this way the issue with the USB can be troubleshot and maybe we can get you a fully working phone with CWM.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
idk how to post screenshots of my phone without a camera.lol. im about ready to give up. its been way too long with not having a phone.

You hit the print screen button, open paint, and tell it to paste/paste from clipboard.
Sent from my LG-P999 using xda premium

[Q] Newly rooted phone stuck at T mobile Screen.

I completely followed all instructions on how to root the 4g blaze, after Odin, does a reboot the phone stays at the boot up screen? Any ideas, did I over look something?
R/S
Patrick

huwilerp said:
I completely followed all instructions on how to root the 4g blaze, after Odin, does a reboot the phone stays at the boot up screen? Any ideas, did I over look something?
R/S
Patrick
Click to expand...
Click to collapse
ALL questions in General Section.
To answer you.. try wiping data & cache in CWM.
If you don't have CWM, then you did do something wrong cause you needed to have that prior to rooting.
Sent from my Unicorns' Dust.

huwilerp said:
I completely followed all instructions on how to root the 4g blaze, after Odin, does a reboot the phone stays at the boot up screen? Any ideas, did I over look something?
R/S
Patrick
Click to expand...
Click to collapse
Did you install k0nane's root kernel over ICS? If so that's where you went wrong. There's a few threads here where others have done so and have been helped. Check those threads.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

This is why I "thought" you needed 10 posts or thanks to even post in Dev.
Sigh..Oh well. Guess the search button is too hard to use.

chjema said:
This is why I "thought" you needed 10 posts or thanks to even post in Dev.
Sigh..Oh well. Guess the search button is too hard to use.
Click to expand...
Click to collapse
I have a question.... I used odin3 v 1.85 to root my gs blaze... after i went into a boot loop. after researching i found a thread on site that said to flash siyah??? well i did that and my phone went died..... wont turn on, tried every three button combo i can find, took battery out put it back in, held the volume buttons while putting the battery in and hooking it up to computer... nothing. so im gonna make an assumption that i hard bricked my phone... my question is: will a jig help me get to the download screen or recovery mode?
also i posted this here because it was the best match for my problem

laknbawill said:
I have a question.... I used odin3 v 1.85 to root my gs blaze... after i went into a boot loop. after researching i found a thread on site that said to flash siyah??? well i did that and my phone went died..... wont turn on, tried every three button combo i can find, took battery out put it back in, held the volume buttons while putting the battery in and hooking it up to computer... nothing. so im gonna make an assumption that i hard bricked my phone... my question is: will a jig help me get to the download screen or recovery mode?
also i posted this here because it was the best match for my problem
Click to expand...
Click to collapse
JIG will not help hard brick. PM me and I can offer some help

[Q] Help: BRICK'd. can't boot into anything (recovery, download, etc)

background: rooted and was running 4.1 stock and CWM 10.0 on verizon gs3. i wanted to bump up to jelly bean 4.2 with CWM 10.1.
first i tried using Rom Manager and Rom Toolkit to flash a new rom. from Rom Manager, i rebooted into recovery and got stuck on the CWM boot screen.
After 30 minutes or so i pulled the battery and tried flashing the stock .tar.md5 using Odin and ended up with this:
"System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help."
now i can't boot into download or recovery. i just have this screen with the yellow exclamation point and the above message.
how screwed am i? i've tried reading everywhere and from what i can gather i didn't wipe my cache sufficiently, but all the other threads just say 'use Odin to get back to stock', but i can't get into download mode so i can't use odin.
please help.

You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have noticed that a lot of people have not unlocked the bootloader are posting on here that they have "bricked" their phones.

jmxc23 said:
I have noticed that a lot of people have not unlocked the bootloader posted on here that they have "bricked" their phones.
Click to expand...
Click to collapse
Ha, I agree although I think its occurred in decreasing fashion since August. Being "bricked" is used overeagerly by folks not wholly understanding their situation. You really have to try to brick this device before that word can be used correctly.

Your phone has not been bricked. You will know that you have bricked your phone when you can't turn on your phone at all. No download mode and no recovery mode also no pulling of the battery just a dead phone.

ClockworkMod
When you fix your phone, root then unlock the bootloader... You can try RM again but I believe that it is best to use ClockworkMod (or the Touch version) for flashing instead of ROM Manager - old fashion, maybe, but it works!
NOTE: Once you start flashing it becomes addictive - you have been warned

thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?

jondotwoz said:
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
Click to expand...
Click to collapse
youll need to put the battery back in......lol

ddurandSGS3 said:
youll need to put the battery back in......lol
Click to expand...
Click to collapse
obviously. i've tried this a million times. It shows the download screen green android robot and the text in the top left for about 4 seconds. then it goes black and the yellow triangle comes back telling me unauthorized software is on there.

check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin

ddurandSGS3 said:
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
Click to expand...
Click to collapse
thanks that's a very helpful thread. However, i still can't get into download/Odin mode. i'm guessing if/once the USB jig can force the phone into download mode, this is where i'll start.
thanks for everyone's help and patience.

[Q] Random rebooting does not stop

Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas

majorcrampas said:
Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas
Click to expand...
Click to collapse
Hello, take a look at this thread http://forum.xda-developers.com/showthread.php?t=2513701

Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app

sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3

kboya said:
Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Well IMHO it is a well known issue (see for example the wikipedia page or just have a look in tech forums). Directly before, I was writing an SMS and put it in my pocket (everything seems fine at that moment). 10 minutes later I just want to check my SMS and then it was already rebooting all the time. This was not the first time, I had this issue 2 todays before, but after approximatley 20 reboots it started correctly.
So far I was not able to use fastboot commands, since I can't enter fastboot. I didn't use a toolkit.

32299564
Madpiercing said:
sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3
Click to expand...
Click to collapse
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.

majorcrampas said:
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.
Click to expand...
Click to collapse
no problemi, i hope you can unbrick it!

Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.

mistahseller said:
Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.
Click to expand...
Click to collapse
If the wall charger is plugged into the phone, the nexus just starts rebooting. I see the white Google logo and after one or two seconds it reboots. Sometimes you see the boot animation (4 circles) but after a short time it restarts the phone not able get to the point where you unlock the SIM. Trying to get into fastboot mode is also not possible. The fastboot mode appears but after half a second the phone reboots again. If the nexus is not connected to a charger it repeats rebooting for about four times after that just a black screen appears. If I'm not able to get into fastboot mode I can't unroot the phone, right? So the links you shared are not useful in my case
I have the nexus now over a week and the phone worked perfectly fine the first week.
I have uploaded two films of the problem to youtube, see this link. One film is with the nexus plugged into the chrager and one where it isn't.

That is very strange.
I would definitely use Madpiercing's post and link to http://forum.xda-developers.com/showthread.php?t=2521691&page=3 to try and fix it.

Madpiercing said:
no problemi, i hope you can unbrick it!
Click to expand...
Click to collapse
I tried the method described in your link without success. Still the same behavior. See my last post, there I add a youtube-link where you can see what exactly happens.

Saw your video that is very strange

mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
The very strange thing is, that it worked well over a week. the random rebooting starts two days ago, first time it starts again correctly after 5 min. Now it seems to hang in a loop.

mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just starts working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happened while to rooting the phone?

majorcrampas said:
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just startes working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happend due to rooting the phone?
Click to expand...
Click to collapse
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.

jd1639 said:
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.
Click to expand...
Click to collapse
I set it up again and give it another try. If something similar should happen again, I will rma it.

majorcrampas said:
I set it up again and give it another try. If something similar should happen again, I will rma it.
Click to expand...
Click to collapse
make sure you unroot and relock the bootloader and do this now while it is working.

mistahseller said:
make sure you unroot and relock the bootloader and do this now while it is working.
Click to expand...
Click to collapse
And triangle away or reset the flag or whatever.
Sent from my Nexus 5

Nexus 5 won't boot, no charging icon, nothing

So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??

I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.

THE_KINGDOM said:
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
Click to expand...
Click to collapse
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe

Wakamatsu said:
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
Click to expand...
Click to collapse
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
joecool666 said:
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Click to expand...
Click to collapse
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.

THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
how's it going any news?

joecool666 said:
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
how's it going any news?
Click to expand...
Click to collapse
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.

THE_KINGDOM said:
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
Click to expand...
Click to collapse
yeah sound's like it could be hard bricked, hope toolkit work's for you tho.

just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird

THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
strange that, not getting detected by p.c, yeah look's like a trip to the service station.sorry i coulden't be of more help. hope you get it back to life.kind regard's joe

THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
All bricks are hard bricks. As much as people use the term "soft bricked", believe me - it isn't a thing. A brick is irreparable. If it was repairable, it isn't a brick.
If it is irreparable, its because its been affected beyond the software layer. Messing up the NAND partitions or NAND death are the most common. This can happen during a flash or even seemingly random - its not unusual for bricks to be random. Flash memory in my opinion, is still pretty unstable. Send it for repair /RMA.
Sent from my Nexus 5 using Tapatalk