Ok, had a slight issue getting everything to work with windows 10. Anyway i was able to get everything going eventually however when I ran "flash-all" i wound up errors all the way and ended with
Getvar: version:bootloader FAILED (command write failed (no error))
Press any key to exit.....
Nothing installed, I'm stuck in bootloader. What can i do from here?
Superman691973 said:
Ok, had a slight issue getting everything to work with windows 10. Anyway i was able to get everything going eventually however when I ran "flash-all" i wound up errors all the way and ended with
Getvar: version:bootloader FAILED (command write failed (no error))
Press any key to exit.....
Nothing installed, I'm stuck in bootloader. What can i do from here?
Click to expand...
Click to collapse
try to flash bootloader v4.23 first and then flash factory image
Having trouble attempting that now as well, laptop doesn't recognize Nexus anymore, it's listed as unknown usb device. Command prompt tells me "waiting for any device" when I try to do anything
Any other ideas? Or do I have a new paperweight on my hands
Related
Okay here's is my story
I have an O2 UK Dell streak which I had originally rooted using the superboot method (fastboot mode and then run the two commands on the mac terminal window)
I then recently installed the leaked 2.1 update on the handset and everything was fine till tonight. I installed an app which needed root access and having not seen the root access icon in the apps, thought that I need to root the phone again after the 2.1 update.
So I plugged in my phone again in my mac and ran the terminal commands. the first one went ok "chmod +x install-superboot-mac.sh" or I assume its ok as the prompt went down without any errors in terminal window.
The second command "./install-superboot-mac.sh" ran but with errors:
"ERROR: could not get pipe properties
sending 'boot' (2520 KB)... OKAY
writing 'boot'... OKAY
ERROR: could not get pipe properties
rebooting... "
The phone rebooted but is now stuck at DELL logo, I have tried removing and reinserting the battery, also ran the commands again in the fastboot mode but still the same errors and still stuck. when going into fastboot mode, the phone pops some error message but not enough time to note the error, also when trying to normal switch on, the display shows a quarter of white screen for a split second with i suspect the same error as before fastboot mode but is even quicker to even notice
PLEASE PLEASE SOMEONE HELP!
From what is sounds, this should help fix your problem. Sood luck!!
http://forum.xda-developers.com/showthread.php?t=754563
I cannot unlock my bootloader. I have a Nexus 16 wifi with 4.2.1 and no other hacks or mods applied. Bone stock.
When attempting this through the Nexus root toolkit or Nexus 7 tool kit or through a fastboot command line device says unlocking now but does not reboot afterwards. When manually rebooting device is not unlocked. I will also add that my device is encrypted through the software provided on the device. Also I cannot factory reset the device through the UI or through the bootloader. Again it says it's doing these tasks but upon boot up I am still asked for my storage unlock password and the device is still back the way it was pre wipe attempts.
Other strange behaviors indicating a wipe attempt are random reboots, Andriod OS process consuming > 40% of my battery. Also device installs the same app updates every time I reboot or if the device reboots on it's own.
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
No dice
duffieldj1 said:
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
Click to expand...
Click to collapse
Unfortunately the only way to un-encrypt device is to reset it to factory spec again which it will not do no matter the method tried. The drivers are correctly installed via the toolkit. The tool kit shows that device serial number. I have installed the SDK and have tryed that method via fastboot 'fastboot oem unlock'. I then follow the directions on device and press the power button. Device is stuck at 'Unlocking now.....' However nothing happens. It does not automatically rebooot or wipe device. When I push the power button the device boots normally as if nothing had happened. Also bootloader is still locked. If I can get it unlocked I think I should be able to wipe it.
Output from command:
C:\Users\Scot\Downloads\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platfo
rm-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 31.029s
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
bftb0 said:
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
Click to expand...
Click to collapse
Wondering too if this is an unintended consequence of encrypting the device. So now that it is encrypted if the device is lost or stolen it's no good to anyone as there is no way to reset it back to a functional device. There has got to be a way to around this. I travel quit a bit for work and that is the only reason I chose to encrypt was in the event it was lost or stolen.
I have an RMA number open with Asus in the event that this cannot be figured out. Really though it is not a hardware issue, it's definitely software related.
Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?
What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2
The title says most of my situation. I've had this since 2012 and some time early last year it just up and stopped booting into android. I have no idea what happened because my girlfriend was using it at the time and she swears she didn't change anything.
Anyways, the bootloader is locked and I have tried to go to recovery and factory reset with no luck. Wiped cache and did nothing as well. I am seeing that windows 7 is sort of recognizing the device. It shows up under device manager as "Android Bootloader Interface"
I've updated the USB drivers and installed ADB as well. When checking the command prompt for ADB Devices, it shows nothing.
I installed Wugs toolkit and it won't even find the nexus either. There has to be SOMETHING that can be done in this situation right?
:EDIT: I was able to unlock it using fastboot but I still can't get it to be found by anything else.
I can get it recognized using the fastboot command prompt, but I can't execute any commands in it. Everything like "fastboot flash boot boot.img" just returns a FAILED message with either invalid argument or no such address or device.
What I am trying to do is just recover it and start using it again. Of course I want to put Android 5.0 on it, but I would be okay with anything as long as it boots, really.
:EDIT: I was actually able to get it to work. I have no idea what specifically had fixed it, but I uninstalled and reinstalled the drivers a few times and ran fastboot and was able to wipe it and install Android 5.0! It was running great!
Hey guys,
Ive been trying to unlock the bootloader on my phone to install TWRP. I have ADB and fastboot installed properly, I have usb debugging enabled on my system and I am my computer's administrator. When I turn off the phone and then open the terminal in platform-tools, I can type in the command to reboot into the bootloader, and my phone will turn off but the screen will stay blank. If I then type in fastboot devices, I can see my phone and that its connected and ready.
However, when I type in fastboot oem unlock I get back 3 dots in the command line, and nothing hapenns. I can wait there as long as I like, nothing will happen. If I unplug my phone, it says
FAILED (status read failed (Too many links))
finished. total time: 4.945s
I'm running an unrooted 7041d on Android 4.2.2. I also have my phones USB drivers installed (or I think I got the right ones)
Does anybody know what to do / how to help?
throwawaytbh123 said:
Hey guys,
Ive been trying to unlock the bootloader on my phone to install TWRP. I have ADB and fastboot installed properly, I have usb debugging enabled on my system and I am my computer's administrator. When I turn off the phone and then open the terminal in platform-tools, I can type in the command to reboot into the bootloader, and my phone will turn off but the screen will stay blank. If I then type in fastboot devices, I can see my phone and that its connected and ready.
However, when I type in fastboot oem unlock I get back 3 dots in the command line, and nothing hapenns. I can wait there as long as I like, nothing will happen. If I unplug my phone, it says
FAILED (status read failed (Too many links))
finished. total time: 4.945s
I'm running an unrooted 7041d on Android 4.2.2. I also have my phones USB drivers installed (or I think I got the right ones)
Does anybody know what to do / how to help?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
To best assist you, I'm going to move this thread to your device's Q&A section.
You should receive expert advice there.
Good luck!
Same problem there.
I have pop 4 plus and I think most of the Alcatel devices are blocked. If I find anything, I will try to help.