Database Info

[Q] I'm pretty sure I'm screwed. HELP!

Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.

Can you access the recovery? If so, format cache partition and then perform a factory reset and try to boot. If it fails, download the factory images and flash it. Factory images are flashed in fastboot mode and doesn't require a working OS or USB Debugging.
Follow the links in my signature and read everything mentioned it those threads. I'm sure your phone will be up and running in no time!

Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
Dumb question, but do you have access to your latest back up on your phone?

Boot into recovery and adb push a rom zip
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
Try changing to TWRP recovery by using - fastboot flash recovery recoveryname.img
Format data, factory reset your devices in TWRP,
Then, install any rom using adb sideload in TWRP

Oh and if you're booting in any way possible, you're never screwed ?
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
First of all you most certainly not screwed.
Now what you have done is oem unlock without google stock recovery.
For the process of wiping userdata to complete , after you type fastboot oem unlock and restart the phone will boot to recovery and execute the wipe.
Because you have cwm recovery the process is stuck and hence the bootloop.
You need to boot to bootloader and type : fastboot -w (press enter) ,it will erase userdata and cache, and restart to system.
You can also try "fastboot format data " and "fastboot format cache" .but if -w worked then no need for that.
If you still stuck in bootloop then you need to flash the stock factory img.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
No need to worry. Download the 4.4.3 factory images and follow the guide "How to flash factory image" which is linked in my signature.
Or, if you want to try out a custom rom, you can push the rom.zip and gapps.zip to your device using "adb push" or sideload it in recovery.

I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.

zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
No, pick it yourself, see below the search for driver software
Sent from my Nexus 5 using XDA Free mobile app

vin4yak said:
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
Click to expand...
Click to collapse
Doing that again. Maybe I missed a step last time but I tried that already a few times. Im trying again.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.

Ok so I uninstalled the drivers from the device manager, went to control panel did it there as well. I have the SDK on my desktop, I installed the google drivers. But I also had downloaded just the google driver manually from their website. Unrared it, plugged my phone in, it detected the phone, I manually updated drivers to the ones I got from the google page. It updated. I was in bootloader mode, and I get that the drivers installed successfully, then it also says Device could not start (error code 10). Anything I type into command prompt still says waiting for device.

Johmama said:
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Click to expand...
Click to collapse
Wow........switching usb ports worked..............Thanks so much! Ok so bootloader unlocked. Now Ill try factory reset, if nothing Ill flash original recovery and do it again. After I sideload the stock zip.

Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.

zeroshift11 said:
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
Click to expand...
Click to collapse
Clear cache and factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app

how to push file to device?

So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?

flash factory image with fastboot.
Tapatalked from my Hammerhead.

Timoooo said:
So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?
Click to expand...
Click to collapse
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

upndwn4par said:
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..

Timoooo said:
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..
Click to expand...
Click to collapse
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.

rootSU said:
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.
Click to expand...
Click to collapse
thanks got everything to work that way!

Timoooo said:
thanks got everything to work that way!
Click to expand...
Click to collapse
No problem. Cool

[Q] Connectivity to PC issue post BOOT-Loop

Hello Lovely people of XDA,
It has been a while since I have requested help here due to the huge library of information available but I am unable to solve this one and I think it should be pretty simple.
For completeness, here is the order of events:
ROOTed One and running stock CM11s with no problems since August 2014.
Wanted a smoother system so flashed vanilla Franco Kernel (very nice) yesterday.
Wanted a bit more so after some searching, found the SlimSaber ROM with TyrV74-Linaro Kernel as a suitable choice.
Now, I followed order of install but stupidly, didnt clear the cache or dalvik cache following install.
I got stuck in boot loop so booted to fastboot to open recovery through ADB.
PROBLEM STARTS
My PC didnt recognise my device and this was confirmed through the blank list returned when using "ADB Devices" in the command window.
I updated the drivers through the ADB interface, restarted computer and tried again. Same thing. I then downloaded the drivers from the Google link in one of the forums (http://developer.android.com/sdk/win-usb.html#top), restarted and connected again. I then tried two solutions (although they both do the same thing) and update the drivers through Device Manager and searching for them using the "have disk" option.
This still didnt work.
From what I can tell this is a driver issue but I have installed several times now the most up to date drivers and from what I can tell, the only difference between my screenshots and the help pages/forum posts is that my Device Manager list doesn't recognise the phone as the A0001, just an "Android Device" (pic attached).
I have searched the forums and all roads lead to either re-installing the drivers or changing the driver settings through device manager, both of which I have tried several times but no joy when I use ADB to check for devices.
Any ideas? I will try anything as I now have a beautifully BOOT-Looped OnePlus!
Also, if anyone knows how to boot to recovery from phone off state then that will also help!

Also tried the Samsung drivers...

OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)

ssjghost said:
OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)
Click to expand...
Click to collapse
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon

timmaaa said:
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
strangely enough....when I fastboot reboot, it loads to system and as long as I keep the phone connected to PC it loads...when I remove it and boot, it crashes. I know this is the case as I wiped cache and delvik and nothing happened when removed but when I booted to system while connected it started updated gapps.... if that helps anyone....

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon

timmaaa said:
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
I cant move file as, I presume, its down to drivers. Which I am unclear as to why? I can access the device through fastboot but when I go through "MyComputer", I get the icon for the phone but when I enter, no files (See Screenshots). If you want specific screenshots then let me know. When I transfer the backup....

Which drivers do you currently have installed?
Transmitted via Bacon

timmaaa said:
Which drivers do you currently have installed?
Transmitted via Bacon
Click to expand...
Click to collapse
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...

ssjghost said:
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...
Click to expand...
Click to collapse
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Sorry, to clarify, when I say "work" I mean allow fastboot recognition....doesnt recognise files through MyComputer.....

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon

timmaaa said:
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
....or phone (re-read question...)

ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
ssjghost said:
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!
Click to expand...
Click to collapse
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon

timmaaa said:
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?

ssjghost said:
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?
Click to expand...
Click to collapse
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon

timmaaa said:
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon
Click to expand...
Click to collapse
.....nice...it was already installed. Ill remove, restart, install, restart and let you know....:/

[Q] Oneplus won't start anymore...

Hello all,
My oneplus one (64gb black) wont start anymore.
How did this happen?
Well,
yesterday after some trouble on my oneplus i tried an factory reset but my TWRP got stuck,
so i started the phone which was still fully working and wiped this: dalvik cache, system, data and cache
But because of that i didn't had a OS anymore ( i didn't know this was going to happen)
So i tried to install CM11 through fastboot commands but every time i got CRC errors in CMD.
So i tried it again and suddenly my phone wouldn't turn on anymore.
I charged it then for 12 hours but still didn't work.
Fastboot wont work, recovery won't work, it doesn't charge ( or atleast i cannot see it on the screen and on the led)
I tried to powercycle it but that doesn't work either.
Can anyone help me please?
Thanks!
BTW: Sorry for the bad english.

Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.

TriKE27 said:
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
Click to expand...
Click to collapse
Thanks for the answer but that doens't work either.

And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

rtomakov said:
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks

bboy521 said:
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
Click to expand...
Click to collapse
Can you see your phone in modems or ports section of device manager?

rtomakov said:
Can you see your phone in modems or ports section of device manager?
Click to expand...
Click to collapse
Thanks for the answer!
My phone is working again! Jeejj
The problem was the unknown device at device manager, so what i did was disconnecting my phone from pc and then press the power button for 1 min, connect it back and then the device manager recognized it!
I'm now flashing it back to exodus rom!
Thanks all!!

I have this situation before, wiping everything dalvik/cache/system/data and internal storage. So my phone has nothing, just few empty file. Now how do I solve it ?
Simply I boot into TWRP. Luckily the driver detect my phone after I connect to pc so I open internal storage, copy the rom and gapps and put em on TWRP folder. Then just go to install on TWRP and look for the folder and voila, flash and phone back to healthy state.
Never ever ever delete that internal storage again lol.

Indeed man
But with me TWRP wasn't available either so yea...
It wont happen again haha
But thanks bro!

[Q] My One is not booting at all, and does not react when i try to charge it

If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.

One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon

alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.

alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?

Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.

alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.

alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.