hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!
Try flashing 8.0 then flashing 8.1.
yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
What was you trying to do before bootloop?
Daandofreak said:
What was you trying to do before bootloop?
Click to expand...
Click to collapse
root
Duhman72 said:
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!
Click to expand...
Click to collapse
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error
yunghunter said:
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.
cntryby429 said:
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.
Click to expand...
Click to collapse
how would I go about doing that what would my next step be I'm sorry just dont where to go next
yunghunter said:
how would I go about doing that what would my next step be I'm sorry just dont where to go next
Click to expand...
Click to collapse
what do you get when you type the below commands?:
adb --version
fastboot --version
Duhman72 said:
what do you get when you type the below commands?:
adb --version
fastboot --version
Click to expand...
Click to collapse
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option
yunghunter said:
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option
Click to expand...
Click to collapse
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe
Duhman72 said:
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe
Click to expand...
Click to collapse
adb version is 1.0.32 fastboot I cannot find the fastboot version
yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.
Duhman72 said:
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.
Click to expand...
Click to collapse
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a
yunghunter said:
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a
Click to expand...
Click to collapse
are you sure you don't have an old installation of the tools somewhere else on you computer? That error sounds to me like it is an old version of fastboot.
can you run the adb version by pointing it to that actual path you have installed the new one you downloaded? I am not real familiar w/ Linux, but in windows it would be something like this - straight from my computer where i have adb.exe installed in 2 different paths:
--OLD VERSION OF TOOLS
C:\Users\UserName>c:\adb\adb.exe version
Android Debug Bridge version 1.0.26
--CURRENT VERSION OF TOOLS
C:\Users\UserName>c:\adb\platform-tools\adb.exe version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as c:\adb\platform-tools\adb.exe
I made sure to set environment variable to always reference the one in path c:\adb\platform-tools\, so i get the newer version and don't have the errors you are seeing. (again I use windows, so I have very little Linux knowledge)
It really sounds like you are using old version of the tools.
yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
Saw that you mentioned you were using Linux; it appears that the latest Ubuntu binaries are not up to date. After I finally tracked down the version number installed on my laptop I realized I wasn't on the latest version and downloaded them from Google. You should ultimately end up with fastboot version 0.0.1-4500957. As it turns out this is the only version of fastboot that actually returned a valid version number for me.
Related
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.
check the attachments... i can't get past this spot
stackz07 said:
check the attachments... i can't get past this spot
Click to expand...
Click to collapse
check your adb version. is it Android Debug Bridge version 1.0.39? i had the same problem before and updating adb fixed it. try "fastboot set active_a" as well before flashing flash-all.bat
I tried and failed to flash-all November Factory image - see attached.
Before this I was running problem-free on Havoc 10 rom, Magisk rooted, then decided to return to stock as I was missing Active-Edge.
Now my unlocked Pixel bootloops at G logo.
Any ideas how to fix please?
-----
Edit: Oh, now it boots into Havoc once more, LOL
Question remains: How do I install Factory Image please?
I had this problem too
Try https://forum.xda-developers.com/pixel-3/development/tool-tool-one-driversunlocktwrpfactory-t3877486
100% working with tool.
goon-heaven said:
I tried and failed to flash-all November Factory image - see attached.
Before this I was running problem-free on Havoc 10 rom, Magisk rooted, then decided to return to stock as I was missing Active-Edge.
Now my unlocked Pixel bootloops at G logo.
Any ideas how to fix please?
-----
Edit: Oh, now it boots into Havoc once more, LOL
Question remains: How do I install Factory Image please?
Click to expand...
Click to collapse
Do you have the latest SDK platform tools (fastboot)?
Thank you for your suggestions.
---
I thought to re-install the tools : Minimal ADB and Fastboot tools:
adb: 0.0.1-4500957
fastboot: 0.0.1-4500957
Symptoms persist
Installed latest SDK platform tools. Completed flash-all without any apparent error and booted into Stock. Thank you - lesson learned.
goon-heaven said:
Thank you for your suggestions.
---
I thought to re-install the tools : Minimal ADB and Fastboot tools:
adb: 0.0.1-4500957
fastboot: 0.0.1-4500957
Symptoms persist
Click to expand...
Click to collapse
I get why "minimal" was of some value in the past, but since Google now releases platform-tools without the rest of the Android SDK there is NO NEED for anyone to ever use minimal again. It is not going to work for anything but the most basic of ADB/Fastboot commands anymore.
I downloaded the latest January Update. I did my reboot to bootloader, flash bootloader/radio, did update image.zip.
This failed with: failed (remote: variable not found).
Google says it's because not updated fastboot. I updated now i'm getting:
error: failed to load 'image-blueline-qq1a.200105.003.zip': Not enough space
When I google this error, it mentions doing a complete manual install of a and b slots, but fastboot flash system system.img doesn't work anymore. Anyone know how I can update?
Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.
dardack said:
Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.
Click to expand...
Click to collapse
Different driver versions perhaps?
dcarvil said:
Different driver versions perhaps?
Click to expand...
Click to collapse
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.
dardack said:
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.
Click to expand...
Click to collapse
The official source for fastboot is platform tools at https://developer.android.com/studio/releases/platform-tools
You should always check for a new version if you run into problems. Actually, I always check for a new version before I try to do an update.
And never use the version from the Linux apt repository for anything but setting permissions. After that, use a ./ to run the current version downloaded (or installed with SDK tools or Studio) separately with the folder opened directly in terminal. Probably off topic, but that version of fastboot is old AF and there have been a handful of new commands like "fastboo reboot fastboot" to get to fastbootd.
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone. Reason is I want to try it out and also tweek som files but not necessarily rooting it.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot I get the fast boot menu with the options but when I connect it to the computer it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried this from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such. It's basically in the fastboot menu that it doesn't seem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Ps: Posted this a few days ago in the general Q&A as a suspect it's not necessarily a specific One Vision problem but it didn't get any replies so I'll try here. Sorry if it's a bit of a double post. ds-
I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus
Cardinal_Vice said:
I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus
Click to expand...
Click to collapse
Did you flash the patched vbmeta image?
ttomovcik said:
Did you flash the patched vbmeta image?
Click to expand...
Click to collapse
No, I can't get that to work. I'm not sure if I understand where I should place it.
Appreciate that you pitch in.
I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe
mjraogr said:
I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe
Click to expand...
Click to collapse
No, my phone works perfectly fine. I just can't flash the vbmeta image and I can't run the .bat file.