Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
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.
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
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?
Hi everyone,
Tried getting some help via other sites but no luck, decided to come here to the experts.
My Pixel 7 pro had an issue where if you would push harder on the screen it would restart, it's a HW issue from what I understand.
Pushing the screen in multiple locations trying to find out exactly where is the point it triggers the restart lead to multiple restarts which bricked the phone.
Now my phone goes into fastboot and whenever i try to go into recovery mode or rescue mode it just cycles back into the fastboot.
I have tried multiple suggestions via connecting the phone to PC in order to fix it or rewrite the rom but I always get the error that my bootloader is locked (it's true i never unlocked it from Dev mode, not even sure i have USB debugging on).
Sending the phone to warranty is not an option, i bought it while on vacation and i live in a unsupported country.
If anyone has any idea how to fix this I would greatly appreciate it. I'm adding here a photo of the screen.
Also things that i have tried until now:
-Draining the phone completely and charging it back
-Sideload rom via ADB (Errors out with : Setting current slot to 'a' FAILED (remote: 'command (set_active is not allowed when locked')
fastboot: error: Command failed)
-Chrome flash utility/pixel rescue
Multiple people have pointed out that i don't need the bootloader unlocked to flash OEM ROM but the errors im getting about the bootloader being locked says otherwise.
Thanks again to anyone taking their time to read this post!
geo91 said:
Hi everyone,
Tried getting some help via other sites but no luck, decided to come here to the experts.
My Pixel 7 pro had an issue where if you would push harder on the screen it would restart, it's a HW issue from what I understand.
Pushing the screen in multiple locations trying to find out exactly where is the point it triggers the restart lead to multiple restarts which bricked the phone.
Now my phone goes into fastboot and whenever i try to go into recovery mode or rescue mode it just cycles back into the fastboot.
I have tried multiple suggestions via connecting the phone to PC in order to fix it or rewrite the rom but I always get the error that my bootloader is locked (it's true i never unlocked it from Dev mode, not even sure i have USB debugging on).
Sending the phone to warranty is not an option, i bought it while on vacation and i live in a unsupported country.
If anyone has any idea how to fix this I would greatly appreciate it. I'm adding here a photo of the screen.
Also things that i have tried until now:
-Draining the phone completely and charging it back
-Sideload rom via ADB (Errors out with : Setting current slot to 'a' FAILED (remote: 'command (set_active is not allowed when locked')
fastboot: error: Command failed)
-Chrome flash utility/pixel rescue
Multiple people have pointed out that i don't need the bootloader unlocked to flash OEM ROM but the errors im getting about the bootloader being locked says otherwise.
Thanks again to anyone taking their time to read this post!
Click to expand...
Click to collapse
Are you trying to sideload the full OTA? You can do that with a locked bootloader. Maybe you were trying to sideload the factory image instead?
Lughnasadh said:
Are you trying to sideload the full OTA? You can do that with a locked bootloader. Maybe you were trying to sideload the factory image instead?
Click to expand...
Click to collapse
Hi there! Yes i remember downloading a file from the link you provided. Got it under ""cheetah" for Pixel 7 Pro " file 13.0.0 (TQ2A.230405.003.E1, Apr 2023).
Issue is, following the instructions, it says i should go into recovery mode but recovery mode does not open for me it just goes back to fastboot screen (the pic i provided). It also mentions there that i shouldhave USB debugging turned on and i don't think it's on...
geo91 said:
Hi there! Yes i remember downloading a file from the link you provided. Got it under ""cheetah" for Pixel 7 Pro " file 13.0.0 (TQ2A.230405.003.E1, Apr 2023).
Issue is, following the instructions, it says i should go into recovery mode but recovery mode does not open for me it just goes back to fastboot screen (the pic i provided). It also mentions there that i shouldhave USB debugging turned on and i don't think it's on...
Click to expand...
Click to collapse
Did you double check to make sure it was the OTA file and not the Factory Image file?
You don't need USB Debugging enabled to sideload a Full OTA. Recovery mode allows for a couple of commands without having that enabled, including sideloading an OTA.
Do you see the Android robot when you try to get into recovery mode? If so, do you then press Power + Volume Up and then release Volume Up?
Forget USB-Debugging! You don't need that. Neither in fastboot mode nor in recovery. It's only mentioned to boot from system to recovery via ADB. So, it doesn't effect you. In fastboot mode USB-Debugging isn't recognized by your device/USB port.
If you can't boot into recovery the device must be send to a repair station. Are you really sure that recovery isn't accessible?
If volume button selection isn't working to get into recovery mode, I wonder if executing the fastboot reboot recovery command to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
also, OP confused me at the outset; he mentioned "Sideload rom via ADB" but also "fastboot: error: Command failed)" -- I've only sideloaded an OTA years ago without issue so I can't recall, but as the selection/name implies, isn't it supposed to be an ADB command, not a fastboot command (therefore, why is it a fastboot error?)?
simplepinoi177 said:
If volume button selection isn't working to get into recovery mode, I wonder if executing the fastboot reboot recovery command to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
also, OP confused me at the outset; he mentioned "Sideload rom via ADB" but also "fastboot: error: Command failed)" -- I've only sideloaded an OTA years ago without issue so I can't recall, but as the selection/name implies, isn't it supposed to be an ADB command, not a fastboot command (therefore, why is it a fastboot error?)?
Click to expand...
Click to collapse
adb sideload ota_name.zip
that is
Sébastien.
5.1 said:
adb sideload ota_name.zip
that is
Sébastien.
Click to expand...
Click to collapse
right?
so would that output "fastboot: error: Command failed" in any instance?
I doubt it, but for all I know, when running the "adb sideload" command, it also calls a fastboot command when applying it (sort of how "fastboot update" executes a bunch of command protocols like to automatically reboot after applying)...?
5.1 said:
adb sideload ota_name.zip
Click to expand...
Click to collapse
but OP is stuck in fastboot mode.
WoKoschekk said:
but OP is stuck in fastboot mode.
Click to expand...
Click to collapse
simplepinoi177 said:
If volume button selection isn't working to get into recovery mode, I wonder if executing thefastboot reboot recoverycommand to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
Click to expand...
Click to collapse
thoughts?
simplepinoi177 said:
thoughts?
Click to expand...
Click to collapse
the problem seems to be kernel related since he can't access recovery and/or system. A/B devices only use 1 Kernel for both. The recovery is merged into the boot.img and has no own partition with an own kernel.
Full firmware can't get flashed with a locked bootloader.
Full OTAs need the recovery due to payload.bin which depends on update-engine. So, OTAs need a shell environment.
The mentioned error output "set_active is not allowed when locked" shows that OP tried to flash an OTA. A full firmware won't change the slot by executing fastboot update UPDATE.ZIP. In this case fastboot uses the active slot to flash the firmware.
It's not possible to flash anything in fastboot mode + locked bootloader => device must be send to a repair station.
fastboot reboot recovery: If it's possible to execute this command (not all devices support that) it will do the same as hardware keys do. But it's worth a try.
WoKoschekk said:
Full OTAs need the recovery due to payload.bin which depends on update-engine. So, OTAs need a shell environment.
The mentioned error output "set_active is not allowed when locked" shows that OP tried to flash an OTA. A full firmware won't change the slot by executing fastboot update UPDATE.ZIP. In this case fastboot uses the active slot to flash the firmware.
Click to expand...
Click to collapse
Trying to understand better (don't mean to hijack the thread, but also I'm sure this will be helpful info to OP)...but is "set_active" called when sideloading OTA? I wouldn't think it would from an adb command ("apply OTA via adb")...
You mention "flash an ota" vs. sideload that's why; unless i'm getting confused by semantics...
If so, can it be concluded that the OP was mistakenly trying to flash the OTA instead of "sideloading" like he claimed (which is only done in recovery mode, correct? unless, again, semantics) as fastboot commands were executed instead of adb?
WoKoschekk said:
fastboot reboot recovery: If it's possible to execute this command (not all devices support that) it will do the same as hardware keys do. But it's worth a try.
Click to expand...
Click to collapse
@geo91, looks like if you can figure this, this might we worth a try....
simplepinoi177 said:
but is "set_active" called when sideloading OTA? I
Click to expand...
Click to collapse
My question: Do you find such a command in the flash-all.sh script inside a full firmware? It's not clear what update-engine really does. It doesn't follow any shell script.
simplepinoi177 said:
OP)...but is "set_active" called when sideloading OTA?
Click to expand...
Click to collapse
Here are the corresponding lines in the AOSP from the master branch of update-engine:
Java:
if (!result.success) {
LOG(ERROR) << "Unable to set the active slot to slot " << SlotName(slot)
<< ": " << result.errMsg.c_str();
}
return result.success;
source: https://android.googlesource.com/pl...heads/master/aosp/boot_control_android.cc#127
MOD TRANSLATION
"How can it be solved? I'm having the same problem with Google Pixel 7 Pro"
********************************************
كيف يمكن حلها؟ أواجه نفس المشكلة مع Google Pixel 7 Pro
omar qaissy, Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by Forum Rule 4 (quoted below) -- that you just agreed to when you first registered your account. Please consider this when you are creating a post in the future. Feel free to include your original message under the English message if you wish. If you do not know English, I encourage you to use any of the resources in the quote below. Your post has been translated as a one-time courtesy.
Thank you for your cooperation, and have a good one!
simplepinoi177 FSM (Forum Specific Moderator)
XDA Developers Forum Rules said:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ , https://www.babelfish.com/ or https://fanyi.baidu.com/#auto/en or use one of your choice.
Click to expand...
Click to collapse