Database Users

wifi Xoom 3.1 unlocking bootloader error...

I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!

V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.

-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)

okantomi said:
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
Click to expand...
Click to collapse
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)

Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?

V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
Do you know what you did to be able to unlock? I think you really have to be careful to type commands EXACTLY as shown. No extra spaces, but don't leave anything out either. Looks like commands aren't typed in correctly. Take your time. You'll do it.

V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.

eqppwqqep said:
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
Click to expand...
Click to collapse
So is everything ok now?

okantomi said:
So is everything ok now?
Click to expand...
Click to collapse
Yes. I am not rooted. am I supposed to change the thread to solved or something?

different error on trying to flash this recovery
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.

jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
If you haven't already. Delete the .img file. and reinstall it. try the process again.
make sure you're inputting the full command prompt from the beginning. That was my problem. Hope that helps.

jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
fastboot flash recovery(you missed this) recovery-Tiamat-R4c-100611-1150-cwm.im

Nexus 7 - Bricked, Need Help, should be fixable!!

Hello,
Got a Nexus 7 (Wi-Fi), it was running on a CM 4.2.2 custom rom, then I decided to flash the original rooted 4.3 rom + franco kernel, after then, all the problems started - it was restarting all the time, some of the apps were not working, so decided to move to CM 4.3 again. After flashing CM 4.3 (newest), I got stuck in a bootlopp with Google logo
What is working:
- I can boot into fastboot (bootloader) mode
- The device has an unlocked bootloader
- I can boot into recovery (STOCK ONE, custom one disappeared)
-PDAnet drivers installed, so I can use adb sideload function while I am in recovery (apply update using adb option) - no use probably
What is not working:
Tried toolkits, seems like fastboot drivers or mode is corrupted, when I plug the tab to the PC, it says malfunctioned or smth like that
So, what I can do to fix this?
P.S it is not under warranty

Managed to sort out fastboot drivers, any further steps?

Pomperis said:
Managed to sort out fastboot drivers, any further steps?
Click to expand...
Click to collapse
Hi, Pomperis...
Yes... fastboot flash the Jellybean 4.3 factory stock image (see my sig for download link).
Be aware though, you might have problems flashing the bootloader (v4.23).
Go here for instructions, should you encounter that problem.
Rgrds,
Ged.

GedBlake said:
Hi, Pomperis...
Yes... fastboot flash the Jellybean 4.3 factory stock image (see my sig for download link).
Be aware though, you might have problems flashing the bootloader (v4.23).
Go here for instructions, should you encounter that problem.
Rgrds,
Ged.
Click to expand...
Click to collapse
Okay,
Got the stock image
Unpacked everything to platform tools folder and swapped the original bootloader image with the custom one (as advised in the thread)
When I type fastboot devices - it seems like fastboot is al right as I get:
xxxxxxxxxxxx fastboot
However, when I try the following steps:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (No such device or address)
finished. total time: -0.000s
Same with other commands
Any ideas?

Pomperis said:
Okay,
Got the stock image
Unpacked everything to platform tools folder and swapped the original bootloader image with the custom one (as advised in the thread)
When I type fastboot devices - it seems like fastboot is al right as I get:
xxxxxxxxxxxx fastboot
However, when I try the following steps:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (No such device or address)
finished. total time: -0.000s
Same with other commands
Any ideas?
Click to expand...
Click to collapse
That's odd... you clearly have a viable fastboot connection (re: fastboot devices... by the way, for securities sake, you'd be advised not to publicly make known your unique device ID... type some random digits if you wish to illustrate your point).
What happens when you run flash-all.bat?
Rgrds,
Ged.

GedBlake said:
That's odd... you clearly have a viable fastboot connection (re: fastboot devices... by the way, for securities sake, you'd be advised not to publicly make known your unique device ID... type some random digits if you wish to illustrate your point).
What happens when you run flash-all.bat?
Rgrds,
Ged.
Click to expand...
Click to collapse
Got this badass sorted out
Just kept reconnecting it to various usb ports and typing the commands till they worked.. Probably my drivers and fastboot was temperamental Got various errors, but now, the tablet has powered on and seems like fully functioning
I will blag it on eBay for a hundred or trade it in in any Cheetham Hill shop lol
Thanks for the help, that tutorial really helped

Pomperis said:
Got this badass sorted out
Just kept reconnecting it to various usb ports and typing the commands till they worked.. Probably my drivers and fastboot was temperamental Got various errors, but now, the tablet has powered on and seems like fully functioning
I will blag it on eBay for a hundred or trade it in in any Cheetham Hill shop lol
Thanks for the help, that tutorial really helped
Click to expand...
Click to collapse
Great you got it sorted... it's always the same with tech; lots of sophisticated software, but often the problem just boils down to a bad USB cable connection, or as you say, some other temperamental aspect... usually hardware!
Hope you get a good price for it.
Rgrds,
Ged.

Will not boot after root

So I followed the XDA guide on rooting. After getting back to the setup screen, I constantly got:
Unfortunately, the process com.google.process.gapps has stopped.
It was literally constant to the point where I could only type one letter at a time. Okay, so I tried factory reset via TWRP. No good. So I downloaded a factory image and tried to flash it, and now my phone sits at the Google/padlock screen forever.
What do I do? I still have fastboot and TWRP access. I'm not sure the images are completely copying to the Nexus when I try to put them directly on the phone. Using Google's image and flash-all command ends in:
writing 'system'...
FAILED (remote: unknown command)
I don't understand this. Please help me. I can't use my phone at all.

Are you unlocked? Can you fastboot flash?

I can, yes. I figured out at least part of my problem - the USB 3 port on my laptop is misbehaving somehow. The USB 2 port works. I was able to fastboot flash. It remains to be seen why I had the gapps issue originally...

Essential Ph-1 softbricked and possibly corrupted

Hey everyone,
Earlier today I was able to successfully root my Essential Ph-1 running Oreo 8.1, using Magisk and twrp-mata_11.img . Later on I tried to install Xposed framework, but found myself caught in a bootloop, when the flashed TWRP did not recognized my phone PIN and I tried to reboot the system and take the PIN out. I am able to access the bootloader and use the TWRP when I flash it, and that's it.
I do realize that it fixing it is not really a complex process, but I have been having trouble with flashing with fastboot. Every command I try to run ends up in failure, except the "fastboot devices" one. For example, when I tried to run the "fastboot -w" command, I received the following:
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))".
And all others commands showed the "FAILED (command write failed (No error))" message, including when I tried to run the "flash all" file as system admin.
Also, I have only tried to do it in Windows, to no avail, while I am still inexperienced with Linux and cannot connect fastboot to my device.
This is not the first time that I have rooted the device, I did it twice a couple months ago but lost the root because of updates. The difference is that I used my Nintendo Switch Pro Controller cable, which for some reason was the cable that worked the best, instead of the phone's factory cable with a Syntech USB - C to USB adaptor. this time. I found out later on that this cable had issues with this kind of process.
Also, when flashing TWRP in my oldest attempt at rooting, I got the message "system mount fail" when installing the magisk zip, but it never progressed beyond that and my at-the-time rooted phone worked perfectly.
This is my first Android phone after years of Apple(also my first thread here), and I have been excited and experimenting with it a lot, though I've only had it for less than 3 months. I would be really grateful if you guys could help me.
Thank you for the collaboration.

Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip

crixley said:
Do not turn it off. Seems that ends in instant brick. Try flashing the return to stock zip
Click to expand...
Click to collapse
All right, will try. Thanks for the tip

Make sure you have a good cable and good fastboot in your computer
Sent from my PH-1 using XDA Labs

So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.

Shiro744760 said:
So I was able to pass through some problems from before, but one still persists. When I run the command "fastboot flash-all" on my command prompt, it shows all the options for fastboot, while only "flash-all" shows that there is no such command. I have also tried "fastboot flashall", but that shows the message:
error: neither -p product specified nor ANDROID_PRODUCT_OUT set.
Sorry, I know this is not the fastboot thread, but I'm really lost here.
Click to expand...
Click to collapse
flash-all is a batch/script file, its not a fastboot command. You simply need to run on Windows
Code:
.\flash-all.bat
or Linux/MacOS
Code:
./flash-all.sh
Just open up a terminal/command prompt, type flash and then hit tab and it will autocomplete the full path.

It worked!
Thought it was already gone for good, I can barely believe it
Thank you very much for all of you, it really meant a lot your help!

Can´t boot twrp.img!

Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66

I ran into this when I was looking to replace HavocOS 2.7 on Moto G6 plus and fix a few issues after a failed update using the tutorial here.
Did you disable lockscreen?
Even though this did not fix this issue for me it is well documented that it can have an effect on adb/fastboot use.
Did you see the notice on your phone to trust the connecting device?
I missed it the 1st time I tried using adb and it didn't prompt me again after that.
Have you tried adb/fastboot on another (older) machine .
I could NOT use fastboot on my Ryzen 7 linux machine w/ native USB 3.0 (or the 2.0 ports) and was getting the same type of results as you, although "adb reboot bootloader" worked fine.
I ended up usng an old HP Celeron laptop booting FWUL (bootable linux dev enviroment, Search for it here on XDA) on a USB stick which recognized the phone no problem and allowed me to "fastboot boot twrp-3.2.3-42-evert.img" (although I did copy/rename it to boot.img to save typing time), use it to backup to sdcard, format data, and install "new" ROM.
WARNING:
The tutorial I used above also has directions for installing (Open)Gapps and Magisk which, even after 2X attempts had lawnchair crashing continuously.
The 3rd time I just installed the ROM and Magisk and it's working fine.
This will be a test to use the phone w/o any g00gle at all (g00gle is EVIL).
HTH!

i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.

àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
d_g_m_2000 said:
i know this is not a solution, but this kind of issue is solve by using a different pc.
i got the same "bug" with my current pc (ryzen 5 + motherboard asus b450m-a)
but my wife's pc (intel+asus mb) have working fastboot commands like usual
also try (if you can) using a usb hub... in my case it did not work but i read some users do.
Click to expand...
Click to collapse
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.

àutowert66 said:
Hi,
I follow this Tutorial to root my Moto g6 Plus.
I could unlock my bootloader, but i cant boot twrp-3.2.3-42-evert.img.
When I try "fastboot boot twrp-3.2.3-42-evert.img" , I get
Code:
Sending 'boot.img' (31100 KB) OKAY [ 0.878s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am using Windows 10, 64 BIt.
I use cmd in WIndows Terminal.
I used the ADB and Fastboot Installer for Windows to install adb and fastboot.
Can someone help me please?
autowert66
Click to expand...
Click to collapse
In my case fastboot got stuck at sending boot.img forever until I removed the cable and then I got a similar or the same error. I solved this problem by disconnecting the cable, then typing in the command and pressing enter and after that putting in the cable again. Then it sent successfully and booted. I hope this helped someone.

If you have ryzen get a usb hub. If you have intel, run the command and wat for the "<wating for device>" and plug in the phone there. Also use usb 2.0

Diego_992 said:
What is your pc specs? Are you using a Ryzen CPU? Idk why but this phone won´t pick fastboot commands with a Ryzen CPU. Get any Intel and you will be able perform the booting.
You are tottaly right. It is a bug or a known issue but this pc won´t pick fastboot commands from Ryzen pc.
Click to expand...
Click to collapse
this is exactly why i didnt chose ryzen for my latest build. i know ryzen is dominating rn, and i really wanted an amd cpu, but need fastboot commands to work since im a regular modder on my oneplus 6T and moto phones