Database Info

Added line to build.prop....now bricked?

So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running

S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?

Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?

Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things

S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need

Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?

S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?

Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.

Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.

[Q] Stuck in bootloop.

Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?

Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.

rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:

Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...

Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works

BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.

Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it

BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?

Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.

No worries
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff

BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.

rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood

rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?

Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature

rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.

Yup. RMA
Sent from my Nexus 5 using Tapatalk

[Q] Locked Bootloader and no recovery =No hope??

G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers

U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305

ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon

timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.

Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon

Cheers mate.

What build of CM11S are/were you on?
Transmitted via Bacon

timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.

Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon

Will have a crack when i get home, thanks for your help.

No good mate as you said.

Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon

Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.

Brand new OP, O bricked, x-post from OnePlus forums

So I installed CM12S on my device and now i'm just getting a black screen, the phone still vibrates when buttons are pressed and I can get the device into fastboot mode, although I can not see it on screen, I can see it on device manager.
Now I've tried the various methods on this forum using ColorOS and the OnePlus Recovery tool, neither of these change the state of my device.
Currently dealing with OnePlus support at the moment which is awful to say the least, they have booked me in for a remote session which is in 2 weeks ... no appointments before then, ive disputed on PayPal with them currently as I dont think this is good enough, anyone got any other ideas to get my device back up and running?
Thanks

Id say to install adb on your computer so that that way you can reflash the roms manually from your computer. Or at the very least flash stock and then whatever customs from there. Here is a link to the thread with the links in the OP with straight forward step by step instructions. Good luck!
http://forum.xda-developers.com/showthread.php?t=2788632

tinyaznboi said:
Id say to install adb on your computer so that that way you can reflash the roms manually from your computer. Or at the very least flash stock and then whatever customs from there. Here is a link to the thread with the links in the OP with straight forward step by step instructions. Good luck!
http://forum.xda-developers.com/showthread.php?t=2788632
Click to expand...
Click to collapse
I have ADB and can succesfully get into fastboot, although I cannot see it on-screen I can see it listed in device manager in windows, Ive tried flashing several ROMs using the fastboot commands and still cannot get the thing to turn on.
I honestly dont believe the device to be completely dead, to note last time I saw this device on I was at 4% battery. But have also left the phone on charge overnight.

ConEP said:
I have ADB and can succesfully get into fastboot, although I cannot see it on-screen I can see it listed in device manager in windows, Ive tried flashing several ROMs using the fastboot commands and still cannot get the thing to turn on.
I honestly dont believe the device to be completely dead, to note last time I saw this device on I was at 4% battery. But have also left the phone on charge overnight.
Click to expand...
Click to collapse
What do you mean you've tried flashing several ROMs with fastboot? You don't flash ROMs with fastboot. Do you mean the stock images?

Heisenberg said:
What do you mean you've tried flashing several ROMs with fastboot? You don't flash ROMs with fastboot. Do you mean the stock images?
Click to expand...
Click to collapse
Yeah apologies ive flashed CM11S, Color, CM12S, also tried oxygen, cant flash ROMs as I cant even get into TWRP.

ConEP said:
Yeah apologies ive flashed CM11S, Color, CM12S, also tried oxygen, cant flash ROMs as I cant even get into TWRP.
Click to expand...
Click to collapse
What is the outcome when flashing the images with fastboot? Do they succeed or fail?

Heisenberg said:
What is the outcome when flashing the images with fastboot? Do they succeed or fail?
Click to expand...
Click to collapse
All of them seem to be successful (no error messages) but the phone still does nothing afterwards.

ConEP said:
All of them seem to be successful (no error messages) but the phone still does nothing afterwards.
Click to expand...
Click to collapse
You said you've tried this right?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

Heisenberg said:
You said you've tried this right?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Yep, get all the way through till it goes green, but still nothing after phone just vibrates, no LEDs or screen activity.

ConEP said:
Yep, get all the way through till it goes green, but still nothing after phone just vibrates, no LEDs or screen activity.
Click to expand...
Click to collapse
I'm out of ideas then, sorry.

G3 Bricked/Boot Loop

So I read other threads with similar issues but nothings seemed to work.
Basically my LG G3 (AT&T) started acting odd one day. Resetting every 3-5 minutes, overheating (more than usual), wouldn't connect to Wi-Fi. Eventually I reset it and the problems got worse. I downloaded a boot logger that can't figure out why, there's no physical damage (EDIT: when this first started, I noticed that the little pink water damage sticker on the battery was, well pink, however I never got it wet and could've been pink before but I don't know), I factory reset it again and nothing, swapped the battery and everything. I could've done more but it is still under warranty so I kinda gave up and decided to exchange it.
The new one is on the way and comes tomorrow or Wednesday however now my G3 won't even turn on, or rather it stays locked on the boot screen (the LG logo specifically) it won't go past that. I tried to hard reset it with the power button and it gets to the screen with the android logo with its chest open and just resets again.
I'm not trying to fix it anymore I just want advice on wiping it basically as I can't even wipe it through my computer. With my last phone what I did before selling it, and what I wanted to do again, is encrypt it, then factory reset to just be extra safe and I wanna know if there's anyway I can do this basically with the phone like this, or if I can get it to a state where I can do that again. I'm not all too familiar with android this low level so I want to know if I can basically "hard" wipe it because I can't even connect it to my computer (it keeps resetting).
Also one time on a boot it said the kernel crashed, don't know how relevant that is as it only happened once out of at least 1,000 times by this point.
Any help would be appreciated, super frustrated right now.
Thank you!

dan1229 said:
So I read other threads with similar issues but nothings seemed to work.
Basically my LG G3 (AT&T) started acting odd one day. Resetting every 3-5 minutes, overheating (more than usual), wouldn't connect to Wi-Fi. Eventually I reset it and the problems got worse. I downloaded a boot logger that can't figure out why, there's no physical damage (EDIT: when this first started, I noticed that the little pink water damage sticker on the battery was, well pink, however I never got it wet and could've been pink before but I don't know), I factory reset it again and nothing, swapped the battery and everything. I could've done more but it is still under warranty so I kinda gave up and decided to exchange it.
The new one is on the way and comes tomorrow or Wednesday however now my G3 won't even turn on, or rather it stays locked on the boot screen (the LG logo specifically) it won't go past that. I tried to hard reset it with the power button and it gets to the screen with the android logo with its chest open and just resets again.
I'm not trying to fix it anymore I just want advice on wiping it basically as I can't even wipe it through my computer. With my last phone what I did before selling it, and what I wanted to do again, is encrypt it, then factory reset to just be extra safe and I wanna know if there's anyway I can do this basically with the phone like this, or if I can get it to a state where I can do that again. I'm not all too familiar with android this low level so I want to know if I can basically "hard" wipe it because I can't even connect it to my computer (it keeps resetting).
Also one time on a boot it said the kernel crashed, don't know how relevant that is as it only happened once out of at least 1,000 times by this point.
Any help would be appreciated, super frustrated right now.
Thank you!
Click to expand...
Click to collapse
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk

If the guide don't work. Try this. every guide did not work for me. Look at post 5.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
Sent from my LG-D850 using XDA Free mobile app

hyelton said:
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you sososo much, I'm gonna give it a shot later tonight.

hyelton said:
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So I'm going through the tot method, however when I plug the phone in I get an error that "Windows malfunctioned the last time the device was plugged in" I plugged it in last night to see if I could do anything and it kept resetting. But in device manager it just shows up as an unknown USB device and there is now no ports section.

dan1229 said:
So I'm going through the tot method, however when I plug the phone in I get an error that "Windows malfunctioned the last time the device was plugged in" I plugged it in last night to see if I could do anything and it kept resetting. But in device manager it just shows up as an unknown USB device and there is now no ports section.
Click to expand...
Click to collapse
What's your OS? If windows 8/10 you'll need to unhide. But if your getting a windows malfunctioned the last time error that would be your computer problem.
Sent from my iPhone using Tapatalk

hyelton said:
What's your OS? If windows 8/10 you'll need to unhide. But if your getting a windows malfunctioned the last time error that would be your computer problem.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Windows 10. It seems like it can't recognize the device, it says under USB controllers: " Unknown USB Device (Device Descriptor Request Failed)"

dan1229 said:
Windows 10. It seems like it can't recognize the device, it says under USB controllers: " Unknown USB Device (Device Descriptor Request Failed)"
Click to expand...
Click to collapse
Yeah you would need to try another computer.
Sent from my iPhone using Tapatalk

hyelton said:
Yeah you would need to try another computer.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I just tried it on another computer, exact same error. It says that there could be something wrong with the device.

dan1229 said:
I just tried it on another computer, exact same error. It says that there could be something wrong with the device.
Click to expand...
Click to collapse
Still windows 10? I've never even seen that error before. Try installing drivers from LGs site?
Sent from my iPhone using Tapatalk

hyelton said:
Still windows 10? I've never even seen that error before. Try installing drivers from LGs site?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Do you know where I could find the driver files? Not the executable, I'm gonna try to "force" update the driver cause it just can't recognize the device but I need the drivers and can't find them.
And yea still Windows 10.

dan1229 said:
Do you know where I could find the driver files? Not the executable, I'm gonna try to "force" update the driver cause it just can't recognize the device but I need the drivers and can't find them.
And yea still Windows 10.
Click to expand...
Click to collapse
Just go to LGs website. The executable should work fine. Are you not trying the ones in the Op? You might want to use a different OS. Not that I'm blaming 10 but for a lot of reasons I had to downgrade.
Sent from my iPhone using Tapatalk

hyelton said:
Just go to LGs website. The executable should work fine. Are you not trying the ones in the Op? You might want to use a different OS. Not that I'm blaming 10 but for a lot of reasons I had to downgrade.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I'm using the ones on your guide, they're on oceanhost

dan1229 said:
I'm using the ones on your guide, they're on oceanhost
Click to expand...
Click to collapse
Okay try the ones from LGs site and see what happens.
Sent from my iPhone using Tapatalk

hyelton said:
Okay try the ones from LGs site and see what happens.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I think I figured it out, only issue (and this is the dumbest yet) is I can't find the .tot file? I downloaded the D850 stock image zip and it's not in there as far as i can tell.

dan1229 said:
I think I figured it out, only issue (and this is the dumbest yet) is I can't find the .tot file? I downloaded the D850 stock image zip and it's not in there as far as i can tell.
Click to expand...
Click to collapse
You extract the zip file... All TOT's are placed in zip files due to size to help people who download it.

hyelton said:
You extract the zip file... All TOT's are placed in zip files due to size to help people who download it.
Click to expand...
Click to collapse
I downloaded the wrong zip my bad XD. Also this doesn't void the warranty does it?

dan1229 said:
I downloaded the wrong zip my bad XD. Also this doesn't void the warranty does it?
Click to expand...
Click to collapse
Wait. What are you trying to do? Why are you needing to flash it if you haven't already voided your warranty? Rooting/Custom rom "voids warranty" in itself.
Flash a tot or kdz puts the phone 100% complete back to stock as you bought it.

hyelton said:
Wait. What are you trying to do? Why are you needing to flash it if you haven't already voided your warranty? Rooting/Custom rom "voids warranty" in itself.
Flash a tot or kdz puts the phone 100% complete back to stock as you bought it.
Click to expand...
Click to collapse
I have the warranty replacement device coming, I just wanted to totally wipe this device but I can't even get it to boot properly.

dan1229 said:
I have the warranty replacement device coming, I just wanted to totally wipe this device but I can't even get it to boot properly.
Click to expand...
Click to collapse
Why won't it boot properly? Also keep in mind this is the only method of going back stock. Also the method only requires you to be in download mode.
Sent from my iPhone using Tapatalk