Related
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
RacerBas said:
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
Click to expand...
Click to collapse
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
bp328i said:
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
Click to expand...
Click to collapse
If I had I wouldn't be here
RacerBas said:
If I had I wouldn't be here
Click to expand...
Click to collapse
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
bp328i said:
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
Click to expand...
Click to collapse
That's what I tried but it came up with what's shown in the screenshot
RacerBas said:
That's what I tried but it came up with what's shown in the screenshot
Click to expand...
Click to collapse
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
bp328i said:
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
Click to expand...
Click to collapse
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
RacerBas said:
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
Click to expand...
Click to collapse
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
bp328i said:
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
Click to expand...
Click to collapse
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
RacerBas said:
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
Click to expand...
Click to collapse
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Good luck man, I've got to get back to work.
I know the adb push "ROM/File.zip" /sdcard works because I tested on my phone prior to posting.
One last thought is your SDK might need to be updated as well.
bp328i said:
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
Currently trying it on my laptop which has a fresh reinstall, removing the drivers completely will take too long.
Your driver saw it as a google galaxy nexus adb Interface, when I used adb devices it didn't see it.
EDIT: when I go to reboot it says that there is no os installed so yea...
Another Edit: I will try this driver when I get home and report back. OnePlus adb drivers windows
I managed to fix it using the oneplus one toolkit by manudroid
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.
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.
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
https://drive.google.com/open?id=1HtjdNjdJ3XiSaOAUNVwZ8E-tGv3xr2Ly
https://drive.google.com/open?id=1eFpvFeUe_xLRUFnBbT2ZzKdTgX8-nyYQ
I will try it and see that it breaks this time
Marakas89 said:
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
Click to expand...
Click to collapse
Thanks for share
work fine in me
wirdan.hungkul said:
Thanks for share
work fine in me
Click to expand...
Click to collapse
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
djxpro said:
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
Click to expand...
Click to collapse
I don't have Ota update ..., you should re-flash your device
wirdan.hungkul said:
I don't have Ota update ..., you should re-flash your device
Click to expand...
Click to collapse
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
djxpro said:
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
Click to expand...
Click to collapse
bootloader must be activated ..
wirdan.hungkul said:
bootloader must be activated ..
Click to expand...
Click to collapse
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
djxpro said:
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
wirdan.hungkul said:
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
Click to expand...
Click to collapse
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
djxpro said:
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
Click to expand...
Click to collapse
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Apparently it is an issue of the operator that I do not have the update yet.
I went back to 8.0 while I find out what happened to the ota.
And if it comes out I'll capture it.
wirdan.hungkul said:
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Click to expand...
Click to collapse
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 through recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
djxpro said:
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 thrgough recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
Click to expand...
Click to collapse
:good:
Well.....i thought let me give it a try.....but.....problem started then...
--- adb works fine.....both the commands (adb devices and adb reboot bootloader) gets executed
--- but my device doesn't get detected in fastboot mode
--- thinking that its problem with drivers...i tried every driver (adb and fastboot) out in the internet and nokia drivers...but got no luck
--- hoping that someone could help me i posted here.... thanks in advance
djxpro said:
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Click to expand...
Click to collapse
i found a way to flash the patched boot and unlock the bootloader on pie
Here
NulledRoot said:
i found a way to flash the patched boot and unlock the bootloader on pie
Here
Click to expand...
Click to collapse
actually, i have a rooted phone.
but, i lock the bootloader again, and now, i need connect to usb to start up
without usb, i give a red state
.-.)
my phone stuck at reboot loop can someone help me?
I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?
Pasini said:
I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?
Click to expand...
Click to collapse
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.
SubwayChamp said:
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.
Click to expand...
Click to collapse
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader. I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing. But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.
Pasini said:
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader.
Click to expand...
Click to collapse
Not sure if you are mixing some things there, you are saying that you have "unauthorized device" through ADB commands but ADB works when device is on...but if you flashed a wrong boot image, could you boot to system some way?
Pasini said:
I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing.
Click to expand...
Click to collapse
You can't flash the boot image through recovery.
Pasini said:
But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.
Click to expand...
Click to collapse
Because of a wrong (and also an unsigned image for your device) you have this message.
Which device you have? And have the bootloader unlocked?