When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
Related
A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year
Glad to hear everything worked out for you. Happy New Year to you too.
Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed
Okay everything started when i wanted to go back to stock after having installed CyanogenMod 12 on my VS980. Everything went well with the install but when i finally wanted to go back, i couldnt enter download mode, instead i would get fastboot mode. I looked into that and people said i only had to replace files like Laf.img, boot.img, and aboot.img through command prompt. When i did this and rebooted the phone, the lg logo came out saying "Security Error" and then bootloops. I can enter Twrp Recovery with ease but i cant go into fastboot nor Download Mode. When i connect to the computer while in Twrp though, my computer picks it up as VS980 but says it was not installed correctly. I dont know what happened and im confused on whether is Soft- Bricked or Hard- Bricked. If anyone could help me with this problem please i have a Windows computer btw, not linux, im not sure if i need a linus for this fix though
Just putting out there, everywhere i look, people always send me here: http://forum.xda-developers.com/showthread.php?t=2432476
This just doesnt work for me since i cant enter download mode.
All help is appreciated and thank you in advance.
which TWRP version do you have?
the most simple solution if you have TWRP working is to flash a rom via OTG
I'm in the same boat man. I can get into TWRP 2.8.0.1 and download mode, but I can not get my drivers to install correctly. I have the drivers in a file. I've pointed my computer at that file, rebooted computer, changed usb cables, tried sideload feature in TWRP, tried the LG flash tool. Nothing helps. God I'm so dumb for erasing internal storage. I'm so used to having an sd card and was just thinking, don't erase sd card and you're good. I rushed through it and f'd up really good.
Errors
adb devices-doesn't list device just blank space
sideload or push just yields a list of all the commands, but nothing else
when I plug phone in to computer-drivers not installed correctly. 'MTP USB failed'
flashtool-'failed previous load'
sideload function of TWRP-It just tries to load forever
terminal in TWRP-I ran a command, but then it says you are not rooted install supersu. Not matter what I choose it reboots and sticks at 'LG' screen.
My drivers worked before I wiped internal storage, so I know it's my phone. Drivers just worked to transfer xdabbeb's 2.3 over 3 minutes before I shyt the bed with it.
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.