Database Users

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

Flashed wrong img

Hey guys,
I wanted to flash the factory image KRT160 to my nexus 4 but accidentally flashed the one for the nexus 7.
I nerver had any problems flashing something to any phone I had but I guess just was too excited for KitKat
I can boot into fastboot and already tried to flash older factory images but nothing worked.
I also cannot boot into recovery. When I try it through fastboot or the toolkit it gives me an error (failed data transfer failure unknown error).
I really hope you can help me out because I wanted to debug an app ^^

Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.

Chromium_ said:
Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.
Click to expand...
Click to collapse
I know :/ The site automatically scrolled down to the 4.4 img and I didn't saw it at the top of the page and assumed it was the one for my N4.
But thanks for the fast reply, I will try it!

Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu

SMillerNL said:
Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu
Click to expand...
Click to collapse
Haha, i have to agree. The typical "flashed wrong kernel" post looks something like this:
:crying::crying::crying::crying: HALLPPPP PLZz... .fsdf FlASHeD wRong KerNal. Teh PhOne BrOke.....DeAd androidzz ReD triaNglez. PPlzzz hAlp mee. :crying::crying::crying::crying:

I'm not really new to all of this
But I wish I had looked twice ^^

I keep my fingers crossed for you to succeed. This should be a lesson to all of us to check twice before flashing. I had a hard bricked phone so I know what you feel.

Thanks for all your support! I managed to fight myself trough a whole bunch of (fastboot) commands and now I am able to boot 4.4!

the thread that @Chromium_ linked is your only hope. and i think that it will fix it, if you can get into download mode that is.

the flash-all bat file didn't work for me so I flashed each img individually with Wug's toolkit. I don't know what the best order for flashing all the separate images is, but it's prob not the way I did it.
What helped me was shutting down after flashing an image, vol-down+power booting into flashboot, repeat until each img was flashed. Then I wiped data/cache/dalvik while flashing SU, again with toolkit.

[Q] Bricked Nexus 4

Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.

Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?

audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.

Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.

From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.

audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:

Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.

audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?

This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.

audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.

tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.

nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.

tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service

BLOD also on 8.1???

Hi all,
I always upgraded Factory Images (with fastboot)... always with a unlocked oem and rooted....
Some days ago I upgraded to last FI 8.1 and rooted with SR5-SuperSU-v2.82-SR5-20171001224502.zip
I worked flawless... this morning I was driving (connected with my auto BT) and suddenly my N6P got stuck...
power button for some seconds for hard reboot....
and then bootloop...
Arrived home I tried to flash again last FI... and also the previous one... I tried also to erase userdata... always Bootloop...
any other idea? is it recoverable?
Thank you in advance guys
Davide

I read different topics on this forum but it's not clear to me how it's possible that this happened several days after the upgrade...

TheSgrash said:
I read different topics on this forum but it's not clear to me how it's possible that this happened several days after the upgrade...
Click to expand...
Click to collapse
I think it's probably just coincidence that it happened while on 8.1. It's huge issue that has plagued so many people. It's something to do with the large cores luckily there is a fix but you need your bootloader to be unlocked. You can find out more here.

I'll go to read your link... the strange thing, imho, is that I can't even run twrp recovery (stock neither)
anyway thank you

TheSgrash said:
I'll go to read your link... the strange thing, imho, is that I can't even run twrp recovery (stock neither)
anyway thank you
Click to expand...
Click to collapse
The fix disables part of the CPU, so with it being a hardware issue you will always have the issue on anything you run if it tries to use it (which stock will).

Wow I've seen alot of people with this issue, I have my 128gb still and don't have any issues

I'm back...
I tried following steps:
- flash stock angler-opr6.170623.019 image
- flash Oreo4Cores boot.img file
- flash twrp3_1_1_4Cores.img file
tried to run recovery -> BLOD
tried to start normally -> BLOD

Same problem.
Do you find some solution? Thanks.

Cant flash an OS - "failed to mount partition '/vendor' (invalid argument)"

Hello!
Now, I know this problem is in other threads. But the only reason why I'm posting a new one is if either that thread had died or the solution wasn't applicable to me (it didn't/doesn't work).
So! What happens is when I try to flash a file to the system or vendor I get this error.
Code:
failed to mount partition '/vendor' (invalid argument)
I've tried in TWRP and the bootloader fixes. And now, I currently have no OS.
What I've tried is as follows:
Flashing just the vendor (bootloader/TWRP) - ends with the vendor error.
Flashing .zip ROMs (bootloader/TWRP) - ends with the vendor error.
Trying the usual return to stock procedure - ends with the vendor error.
Repairing partition in TWRP - Says operation completed but the error is still persistent.
Basically. Nothing works because the Vendor partition is unmountable.
What should I do? I have no idea what a fix could be.

Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
Code:
FAILED (data write failure (Too many links))
or
Code:
FAILED (command write failed (No error))
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.

Nexus Radical said:
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
or
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try using Nexus root toolkit, I used that today to fix recovery,

jimbomodder said:
Try using Nexus root toolkit, I used that today to fix recovery,
Click to expand...
Click to collapse
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.

Nexus Radical said:
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Click to expand...
Click to collapse
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.

jimbomodder said:
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
Click to expand...
Click to collapse
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.

Nexus Radical said:
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Click to expand...
Click to collapse
Have you tried wugfresh Nexus tool kit?

Just thought I'd let you know that I have fully restored stock and locked my bootloader, and if I boot recovery I get " no command" too. Seems latest recovery image does f*@k all.

jimbomodder said:
Have you tried wugfresh Nexus tool kit?
Click to expand...
Click to collapse
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.

Nexus Radical said:
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Click to expand...
Click to collapse
O crap, I got 2 "oem" replacement cameras for my 6p from them and both blurry and don't save pictures,. Glad you fixed it yet.