Database Info

Help - this is a difficult one

Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.

If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.

tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.

I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.

grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.

Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.

grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one

The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.

Try flashing it by adb?

Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/

ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One

have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try

Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter

markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?

ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try

markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..

ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread

luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this

I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal

snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.

Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data

I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop

do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.

Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above

rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links

snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..

rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..

snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.

rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.

snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers

rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.

rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.

theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

[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.

Unlocking and Rooting AT&T LG V10 H900?

Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out

T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?

I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.

sharky481232 said:
I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.
Click to expand...
Click to collapse
How'd you manage to do that? I've tried a combination of buttons, but nothing.

RobertVanHagar said:
How'd you manage to do that? I've tried a combination of buttons, but nothing.
Click to expand...
Click to collapse
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.

sharky481232 said:
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.
Click to expand...
Click to collapse
Really hope you find the work around. Alot of people say at&t isnt going to allow rooting of new devices.......if theres a will theres a way!good luck

no updates?

I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?

betovanbuuren said:
I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?
Click to expand...
Click to collapse
I have the same problem with my AT&T H900. I'm on 90009e and wanted 90010f. AT&T Tech support couldn't get it to upgrade either which I find very odd. We really need some phone mastermind to unlock the secrets of the AT&T LG V10 H900. I'm unable to get it into download mode or unlock the boot loader either.
Thanks,
Silver

professorpoptart said:
T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?
Click to expand...
Click to collapse
Hmmm that's wiered because mine has stayed checked since I got the phone,although I don't t think it matters since it isn't unlocked. What's funny is i don't know why you can check it if bootloader is locked, I'm still lost on that one .

kotafoxx said:
Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out
Click to expand...
Click to collapse
This has been asked and answered here

How to get into stock recovery
1) Enable USB dubugging
2) Plug phone into computer
3) Set USB connection type to MTP
-Now the "USB debugging connected" notification should appear.
4) Entering "sudo adb reboot recovery" into the terminal will reboot you into the stock recovery.
Note: Entering "sudo adb reboot bootloader" will only reboot your phone...
Using: at&t LG V10
Model Number: LG-H900
Android Version: 5.1.1
Build Number: LMY47V
Computer OS: Ubuntu 15.10

I was able to root an LG escape2 with this method. You can communicate and push files to your phone through the download mode without technically using adb. Any chance a method like this would work?
http://androidforums.com/threads/gui...2-2015.937446/

in case you are subscribed to this thread go here..... http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317/post65864734#post65864734

Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954

jiggajatt said:
Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954
Click to expand...
Click to collapse
Excuse me, what's flux?

manny18pr said:
Excuse me, what's flux?
Click to expand...
Click to collapse
http://techcrunch.com/2016/03/15/popular-blue-light-reducing-app-f-lux-arrives-on-android/