Related
Good evening all. I am hoping for some help before I try and exchange my Nexus 7.
The Nexus 7 was running Rasbeanjelly fine on a trinity kernel.
I flashed a new kernel motlry kernel.
I am now stuck with access to fastboot, no access to recovery, the 7 wont boot up.
So I cant get to recovery (which was TWRP). I cant flash a new rom because the computer (windows 7) doesnt see the device. I have downloaded the Nexus 7 tool kit but it doesnt see the device even if I refresh the drivers (before the issue I had no problems with the 7 being seen on the computer). I dont see how I can use adb as the device cant be seen by the computer.
Any last thoughts before I return?.
Many thanks one and all.
Matt.
This may help you blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Yeah but adb uses command line? Just because it is not showing up doesn't mean you are without a fix. Don't give up. Did you try using a toolkit? I had a similar problem but got it to work. I am trying to remember how I got it to flash. Thinking......
Sent from my Nexus 7 using xda app-developers app
fastboot you say that you have? try fastboot booting your recovery. also, when you get this sorted, your gonna want to flash the newest bootloader, it fixes the issue of not being able to get into recovery from your bootloader.
put the recovery file into the same folder as fastboot on your computer. open fastboot/open the command window. type..
fastboot devices(press enter)(this should give you your devices id number if fastboot sees your device)
fastboot boot recovery yourrecoveryname.img(press enter)(this should boot the recovery)
Thanks guys for the advice. I will give it another go this weekend and come back for a bit of help or let you know resolved. Last day at work!.
Thanks again.
Matt
I had mine stuck with no bootloader and managed to get it flashed. I do not see the point in spending hours with command line unless you would want to learn. Why spend hours on something when you don't have the time? Some say not to use toolkits but I guess they always want to make things harder for themselves. Granted, we need to understand exactly it is what we are doing, many of tutorials are like one of big riddle. I recommend using this toolkit.... http://forum.xda-developers.com/showthread.php?t=1809195 Make sure you are at page 1.
Sent from my Nexus 7 using xda app-developers app
Thanks all got it fixed with Nexus Root Tool kit. I have now update the bootloader to 3.41.
Matt
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
THIS IS OLD OUTDATED METHOD AND WILL HAVE NO SUPPORT.
SEE AUTOPRIMES THREAD FOR CURRENT METHOD.
https://forum.xda-developers.com/showthread.php?t=3308227
**************
Here's my "One Click" method to get TWRP onto the G4 H811.
Special thanks to the following:
**Originally script written and tools by avicohh, modified by MicroMod777 to work only on H811.
**Special thanks to Manh_IT and RenaKunisaki for help getting correct flash commands.
**Special thanks to Unjustified Dev for TWRP.
**Special thanks to Team Codefire and vn_mobile for root.
PREREQUISITES:
**Must be on T-Mobile USA LG G4 H811 10H. WILL NOT WORK ON 10N. DO NOT DOWNGRADE TO 10H OR YOU WILL BRICK.
**Must have LG drivers installed and USB debugging enabled
**Windows computer
**OEM Unlocked in Developer Options.
Instructions:
Step 1: Plug phone to computer.
Step 2: Unzip H811-One-Click.zip
Step 3: Press CLICK-HERE-LG-G4-H811-UNLOCK-TWRP.bat to begin
Step 4: Phone will reboot a few times
Step 5: Pull battery after 1 minute only when on screen instructions say so.
Downloads:
****WARNING****ONLY FOR USA T-MOBILE G4 H811****YOU WILL BRICK****WARNING****
---->H811-One-Click.zip
****WARNING****ONLY FOR USA T-MOBILE G4 H811****YOU WILL BRICK****WARNING****
MD5: 7640484c4842cb883a702d0e09d89c9e
Issues: This might take a few tries to run if the LG drivers don't fully install in download mode.
***If you still can't get it to work, uninstall all LG Drivers, reboot and install drivers from here: LG drivers
MANUAL MODE:
Step 1: Copy recovery.img to your internal storage.
Step 2: Pull battery, put back in. Press and hold Volume up and plug cable in. (Enter Download Mode)
Step 3: On your computer open up your Device Manager and look for:
**Ports (COM &LPT)
****LGE Mobile USB Serial Port (COM?)
Look for the port number in COM#! ?=#.
Example:LGE Mobile USB Serial Port (COM3). So mine is port 3.
Step 4: In your One-Click folder press Shift/Right-Click-Mouse and press "Open Command Window Here".
Step 5: Type Send_Command.exe \\.\COM? Make sure the ?=Port number from Step 2.
Example. Mine is Send_Command.exe \\.\COM3
Step 6: Type "id" without quotes and make sure this comes up: uid=0(root) gid=0(root) context=u:r:recovery:s0
Step 7: WARNING, IF YOU GET THIS PART WRONG OR DON'T USE H811 YOU CAN BRICK!
*****Type Flash command only for H811:
dd if=/data/media/0/recovery.img bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
Step 8: Type: LEAVE
**Phone will reboot
DONE.....
Enter TWRP:Must be OEM Unlocked in Developer Options.
**In ADB: adb reboot recovert
or...
**Pull battery, put back in. Press and hold volume down/power. When LG Logo appears only let go power for a second and then press again till factory reset screen appears. Do factory reset to boot into TWRP. If you don't see TWRP run program again.
******************************************
To get root flash from TWRP:
Root SuperSU.zip
http://forum.xda-developers.com/showthread.php?t=1538053
Very Nice. Are you using the same TWRP that is in the Original Development forum? Just curious to see if there are any changes such as time fix.
Awesome sauce! First thing I'll do when I get my G4 tomorrow.
for your coffee fund[emoji6]
Transaction ID:38Y91835CE493025B
Sent from my Nexus 5 using Tapatalk
lancemoreland said:
Very Nice. Are you using the same TWRP that is in the Original Development forum? Just curious to see if there are any changes like maybe time fix.
Click to expand...
Click to collapse
Same one, just repackaged for one click!
mawells787 said:
Awesome sauce! First thing I'll do when I get my G4 tomorrow.
for your coffee fund[emoji6]
Transaction ID:38Y91835CE493025B
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sweet! Thanks so much!
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
buckless said:
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
Click to expand...
Click to collapse
No, you don't need low effort root. This is essentially the Nexus way. Just follow instructions and it will flash TWRp. Once you successfully reboot into TWRP. Download SuperSU.zip and flash it and you have root, it's very easy.
Sent from my Nexus 5 using Tapatalk
buckless said:
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
Click to expand...
Click to collapse
If you want TWRP to flash rom's then you want this!
But you can also use this to get root, by flashing the SuperSu.zip from TWRP. This is way easier than having to download a 5gb system.img, and manually running all the commands for root in the other root thread.
mawells787 said:
No, you don't need low effort root. This is essentially the Nexus way. Just follow instructions and it will flash TWRp. Once you successfully reboot into TWRP. Download SuperSU.zip and flash it and you have root, it's very easy.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for that good explanation! Guess you posted just before I did!
I just hope no non-H811 person tries to flash this and bricks their device. I put a big warning on OP. But as always somebody always doesn't read OP.
MicroMod777 said:
Thanks for that good explanation! Guess you posted just before I did!
I just hope no non-H811 person tries to flash this and bricks their device. I put a big warning on OP. But as always somebody always doesn't read OP.
Click to expand...
Click to collapse
Anytime. You can only lead a horse to water...
Sent from my Nexus 5 using Tapatalk
thank you both for the quick response.i downloaded the twrp zip ,and opened it with 7 zip,i do have drivers installed and adb enabled and the computer sees the phonealso on t-mo 811h.so was i correct toput the phone in download then open file and click on start?don't need to extract files etc?just don't wanna mess up then be back on here needing help, really want to be able to flash extreme.thx again
buckless said:
thank you both for the quick response.i downloaded the twrp zip ,and opened it with 7 zip,i do have drivers installed and adb enabled and the computer sees the phonealso on t-mo 811h.so was i correct toput the phone in download then open file and click on start?don't need to extract files etc?just don't wanna mess up then be back on here needing help, really want to be able to flash extreme.thx again
Click to expand...
Click to collapse
Just follow OP steps. It will go into download mode on its own.
Sent from my LG-H811 using Tapatalk
micromod...thx again.really appreciate your patience with me and your hard work putting this together, just one more question....dore or after i need to go into developers options and check bootloader unlock and if so before or after?
Do I put the zip file on the phone or the computer? I'm assuming the computer.
buckless said:
micromod...thx again.really appreciate your patience with me and your hard work putting this together, just one more question....dore or after i need to go into developers options and check bootloader unlock and if so before or after?
Click to expand...
Click to collapse
I checked it but not really sure its required.
Uncle Lizard said:
Do I put the zip file on the phone or the computer? I'm assuming the computer.
Click to expand...
Click to collapse
Computer.
Sent from my LG-H811 using Tapatalk
when I do one click recovery does't install and try to boot into to it and it says error
throonis said:
when I do one click recovery does't install and try to boot into to it and it says error
Click to expand...
Click to collapse
Were do you see error? Please explain more.
Sent from my LG-H811 using Tapatalk
"SOLVED" IT WORKED ,on boot screen left hand corner in white lines it says error
throonis said:
on boot screen left hand corner in white lines it says error
Click to expand...
Click to collapse
Do you have H811 and did the md5 match and did you get to the end of the program that said to pull battery?
Sent from my LG-H811 using Tapatalk
I had to run it twice on my phone and five times on my lady's phone, but after erasing data on both phones, trying to get into the recovery that wasn't installed, both are rooted and restored. Don't know why it went that way, but it doesn't much matter now that everything is well. Thanks again.
Uncle Lizard said:
I had to run it twice on my phone and five times on my lady's phone, but after erasing data on both phones, trying to get into the recovery that wasn't installed, both are rooted and restored. Don't know why it went that way, but it doesn't much matter now that everything is well. Thanks again.
Click to expand...
Click to collapse
I think it was the drivers needing to load in download mode. Each time you ran it did it say to pull battery when it finished?
Sent from my LG-H811 using Tapatalk
Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!
Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb
Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
or fastboot wipe user data and cache.
nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.
simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.
simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......
paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....
FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!
BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk
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.