Anyone being able to access recovery? - Nokia 8 Questions & Answers

I haven't found any way to access to stock recovery. Only success I had has been entertaining safe mode.
There are several suggestions that says to hold volyme up and power buttons while being plugged in and stuff... But nothing really seems to work. Anyone that actually accessed recovery?
Sent from my TA-1004 using Tapatalk

How about through ADB?
ADB reboot recovery...
I have tried button combos but no recovery.
I am currently on vacation, so can't access pc, will try as soon as I get to home.

Adb reboot recovery works, but idk what to do then...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Powered by Nokia 8

From the first picture it looks almost like there is no recovery installed on the recovery partition. Or it's locked behind some specific button combination.

Now this is getting really really sad... There are no usb driver for Linux. Even talked with support after I couldn't find it on their web site..

Now this is getting weird, I cannot get the ADB to see my Nokia 8 even on windows... Although I installed the driver.
Edit. Never mind, just haven't used windows in a while..
---------- Post added at 09:49 PM ---------- Previous post was at 09:11 PM ----------
Ok so, I can get the device to boot into bootloader(download mode) and somekind of a recovery, trough ADB in windows.
But no luck on "fastboot oem unlock" command. --FAILED <remote : flashing unlock is not allowed

lorditler said:
Can't you just plug it in and use MTP? Or are you talking about a driver for ADB?
Click to expand...
Click to collapse
Yes, I mean driver for ADB to work.
Mtp works just fine!

after "adb reboot recovery" it is in download mode.
pressing power and volume up is getting it into recovery mode.
so far i found no way to get it into bootloader.

Alttu said:
Now this is getting really really sad... There are no usb driver for Linux.
Click to expand...
Click to collapse
Hmmm... I just enabled USB debugging in the developer options, connected the Nokia 8 to my Linux machine, typed
Code:
adb devices
, and it worked right away.

shredzone said:
Hmmm... I just enabled USB debugging in the developer options, connected the Nokia 8 to my Linux machine, typed , and it worked right away.
Click to expand...
Click to collapse
Really?!
I tried many times, must be something on my end then

Alttu said:
Really?!
I tried many times, must be something on my end then
Click to expand...
Click to collapse
Could be the distribution (I'm using Fedora)... Maybe all you need is to add an udev rule for HMD Global (vendor id 2e04).

shredzone said:
Could be the distribution (I'm using Fedora)... Maybe all you need is to add an udev rule for HMD Global (vendor id 2e04).
Click to expand...
Click to collapse
Thanks mate, will try.
I am using Ubuntu...
Strange thing is, I haven't got any problems with other phones before...

Got the adb command working by simply installing the adb from the repo in Sabayon. What remains is a problem... What if the phone does not boot or is locked with a bugged unlock pattern without having adb debugging enabled?
Send to service?
If it does not boot I assume there is some kind of failsafe using the a/b partitions... But besides that I don't see how the user can recover if a big problem comes
Sent from my TA-1004 using Tapatalk

2WildFirE said:
Adb reboot recovery works, but idk what to do then...
Powered by Nokia 8
Click to expand...
Click to collapse
Press and hold power key, then press volume up.

Here's my experience using Ubuntu (make sure adb tools are installed)
1. Connect the phone to PC via USB
2. Ensure debugging on the phone is turned on
3. Set USB mode to "File Transfers" via the notification shade on the phone
4. From the PC terminal run "adb reboot recovery", without the quote marks
5. The phone will reboot to an image of Android robot with red exclamation mark and the words "no command" on screen
6. Now hold the power button down and then press Volume Up
You should be in recovery menu

Related

Xiaomi Mi 5 Needing Root Guidance

Hello there and sorry if this was something asked 100 times. I haven't found quite something up to date.
So I've had my Mi 5 for some time now and I've decided to Root since I do need quite some features. Problem is I'm pretty scared of doing this since I've never done it before and I'd like to ask here if everything that I'm about to do is correct and if it's not I could get some steps into the right drections.
I'm on Global 9.1.1.0 (NAAMEI).
I'll be able to unlock my bootloader in exactly 10 hours since I had to wait for that stupid 72 hours lock so here's what I prepared.
From what I understand I need to flash TWRP Custom Recovery and download the specific one for my device. Their sites lists twrp-3.2.1-0-gemini.img as the latest for Mi 5 so this one I'm guessing is good to go?
I've also installed fastboot adb drivers installed, the TWRP mentioned above and I also renamed it to ''twrp'' to make things easier later on. That's how my curent folder looks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable USB debugging from developer options, turn off my phone into fastboot my pressing volume down and the power key then connnect it to my PC via USB.
So I'm to shift right click into this very folder, open up cmd and type fastboot devices to see if my device is properly reconized it shoud show up some numbers. After that type fastboot flash recovery twrp.img then it shoud do it's thing and after that type fastboot boot twrp.img to load up TWRP.
I've put into my phone's storge the following to be ready:
- lazyflasher-no-verity-opt-encrypt.zip
- Magisk-15.3.zip
-Magisk uninstaller
After the recovery boots up I am to flash the lazyflasher and Magisk and hope my phone isn't bricked. Is this all that I need to make sure my phone will not bootload or anything like that? Thank you
Zardax said:
Hello there and sorry if this was something asked 100 times. I haven't found quite something up to date.
So I've had my Mi 5 for some time now and I've decided to Root since I do need quite some features. Problem is I'm pretty scared of doing this since I've never done it before and I'd like to ask here if everything that I'm about to do is correct and if it's not I could get some steps into the right drections.
I'm on Global 9.1.1.0 (NAAMEI).
I'll be able to unlock my bootloader in exactly 10 hours since I had to wait for that stupid 72 hours lock so here's what I prepared.
From what I understand I need to flash TWRP Custom Recovery and download the specific one for my device. Their sites lists twrp-3.2.1-0-gemini.img as the latest for Mi 5 so this one I'm guessing is good to go?
I've also installed fastboot adb drivers installed, the TWRP mentioned above and I also renamed it to ''twrp'' to make things easier later on. That's how my curent folder looks.
Enable USB debugging from developer options, turn off my phone into fastboot my pressing volume down and the power key then connnect it to my PC via USB.
So I'm to shift right click into this very folder, open up cmd and type fastboot devices to see if my device is properly reconized it shoud show up some numbers. After that type fastboot flash recovery twrp.img then it shoud do it's thing and after that type fastboot boot twrp.img to load up TWRP.
I've put into my phone's storge the following to be ready:
- lazyflasher-no-verity-opt-encrypt.zip
- Magisk-15.3.zip
-Magisk uninstaller
After the recovery boots up I am to flash the lazyflasher and Magisk and hope my phone isn't bricked. Is this all that I need to make sure my phone will not bootload or anything like that? Thank you
Click to expand...
Click to collapse
You only choose 1, either fastboot flash (replace ur existing recovery) or fastboot boot (just temp boot to twrp)... I suggest the latter...
You don't need lazyflasher with magisk, what's that for?... [emoji6][emoji6][emoji6]
Sent from my MI 5 using Tapatalk

Fastboot isnt working..?

Hey guys
I just bought a new Mi 9 Lite and instantanously wanted to unlock it.
so i did all the steps and then tried to connect with mi unlock the first time to see how long the waiting period is
After i booted into fastboot with volume down + power i connected the phone to the computer and it suddenly went black.
Only in the upper corner it showed a cut off text saying: "any key to shut down" -> see attached photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mi Unlock didnt detect it, and neither did Adb fastboot...
Do you know a fix? i really dont want to send it back...
And im pretty certain this was not my mistake, as i tried it multiple times
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
the reason is windows 10, on 7 it works
k3lcior said:
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
Click to expand...
Click to collapse
Thanks for your fast answer!
I just tried it again, and adb as well as fastboot devices do recognize the phone.
The blackscreen from fastboot only appears upon opening the mi flash unlock tool... In the exact same moment...
As you said i tried "adb reboot bootloader", but the same happened upon opening the tool.
I couldnt find the qualcomm ones though, didnt know where to install them from...
Btw. if it helps i have Windows 8.1
But havent had Problems with the Mi9 or Redmi 4 Prime unlock (which just now worked fine)
Romancier said:
I couldnt find the qualcomm ones though, didnt know where to install them from...
Click to expand...
Click to collapse
https://androidfilebox.com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
k3lcior said:
androidfilebox....com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
Click to expand...
Click to collapse
Installed it, and even re-installed all the usual drivers. Still, the black screen pops up as soon as i open the unlock tool...
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
arvarobert said:
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
Click to expand...
Click to collapse
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Romancier said:
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Click to expand...
Click to collapse
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
k3lcior said:
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
Click to expand...
Click to collapse
Indeed it is recognizes in adb as well as in fastboot.
It's an old Thinkpad im working on, so its an Intel. I still only have simple Usb-ports.
But im surprised as it has worked with the Mi 9 also a few weeks ago...

Yet another unlock bootloader question

I have a Nokia 8 model TA-1052 (this is NB1, correct?). It has a locked bootloader and is running Android 9.
I understand the HMD service for unlocking the booloader is no longer available and the only option now is using a Hikari's website.
Before I try Hikari's method I want to make sure that fastboot is working (I understand it is required?).
With the phone connected, the command "adb devices" show the phone listed but any fastboot command seems to not being able to find the phone (e.g. "fastboot devices" returns nothing).
Am I missing anything?
Thank you.
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
dt_matthews said:
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
Click to expand...
Click to collapse
I don't have any specific Nokia drivers installed. The only USB driver showing (that seem to be related) is "ADB Interface".
I know that for some people the Nokia driver comes on the phone but mine isn't. Where can I get the driver from?
EDIT: in download mode the Win10 Device Manager shows an unknown "Android" device under other devices
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
Thanks that worked
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
This is an essential part of unlocking the bootloader.
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
i just unlocked my phone with this tool and somehow it's back to android 8.1 oreo, is that the normal behavior?
Hi, i used the methode in the link above but now my phone is stuck on the Nokia logo and won't boot to OS.
I can let the batterij drain and power it on but then i get this message in the picture.
Manually getting it into download mode is impossible (holding combo keys volume down and power looks like that doesn't work)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some idea how to fix this? Luckely its not my daily driver but a testdevice.
I have it working again, let battery fully drain, then i could get into download mode (holding vol- while plugging usb) then I could run the tool again (had to request new OTP) and now it just boot normally

SOLVED --redmi note 9, blinking redmi logo, not starting, cannot switch off, can't enter fastboot mode also

I tried to root my redme note 9 using magdisc from pc. after completing all steps, I have given command to boot recovery through minimal adb, after that phone automatically moved from Fastboot mode and started blinking REDME on screen, a few moments later it goes black and again appear. it keeps continuing now. I tried long press on the power button for restart/switch off, but no use, it will vibrate and ON with redme logo, and will go black after few moments. i tried to enter into fast boot mode, but result is same, it will vibrate and go OFF, when I tried to connect pc, pc is not recogonizing this phone anymore. nothing is working, cant even switch off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, i have the same issue here, but just after trying to update pixelUI official.... infinite bootloop on miui logo, no fastboot, no recovery and not detected on the PC. Installed MTK drivers but nothing more... THX
Did you try to flash something?
Yep! upgrade from pixelUI official 3.7 to 3.8, had some intempestive reboot, so i swype and re-install and seen that, infinite boot loop, no recovery, no fastboot and phone isn't recognize by PC...
So i can't use SPflash tool to install stock rom...
Sometimes PC see the phone realy realy fast son i don't have time to verify in device manager..
Thanks for your fast response!
Install usb drivers and then force flashing using spflashtool.
thrasholiv said:
Hello, i have the same issue here, but just after trying to update pixelUI official.... infinite bootloop on miui logo, no fastboot, no recovery and not detected on the PC. Installed MTK drivers but nothing more... THX
Click to expand...
Click to collapse
i was trying to root my phone by magisk, but now the issue is solved, I tried SP flash tool
VD171 said:
Install usb drivers and then force flashing using spflashtool.
Click to expand...
Click to collapse
yes I tried this, now issue is solved
SP flash tool give me an error message "STATUS_BROM_CMD_FAIL", so i must use EDL but when i try "
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE"​Even after install and uninstall many version of python, when i try to execute "cdc-acm.inf" as administrator a prompt tell my python is not found...
THX for your answers!
guys i have the same issue. do anyone help me to recover. Please join with my on any screen sharing platforms so i can solve my issue. thanks
VD171 said:
Install usb drivers and then force flashing using spflashtool.
Click to expand...
Click to collapse
How can I do that, to force flashing using sp flash tool? something similar happens to me only that it does not turn on and when I connect it to the pc comes out the following error that I will attach an image and translate:
'usb device is not recognized
the last device you connected to this computer did not work and Windows does not recognize it.'
what can i do in that case?
afyjaslam said:
I tried to root my redme note 9 using magdisc from pc. after completing all steps, I have given command to boot recovery through minimal adb, after that phone automatically moved from Fastboot mode and started blinking REDME on screen, a few moments later it goes black and again appear. it keeps continuing now. I tried long press on the power button for restart/switch off, but no use, it will vibrate and ON with redme logo, and will go black after few moments. i tried to enter into fast boot mode, but result is same, it will vibrate and go OFF, when I tried to connect pc, pc is not recogonizing this phone anymore. nothing is working, cant even switch off
View attachment 5387173
Click to expand...
Click to collapse
hey man did you fixed it and how pls tell me thanku
ahmadLiaqat2839 said:
guys i have the same issue. do anyone help me to recover. Please join with my on any screen sharing platforms so i can solve my issue. thanks
Click to expand...
Click to collapse
hey did you fixed the problem bro and how
hey i have the same problem with my redmi note 9 pro please help
VD171 said:
Install usb drivers and then force flashing using spflashtool.
Click to expand...
Click to collapse
hello there, my redmi note 9 just got updated to miui 13 and for some time it sudenly freezes and not its in bootloop and i cant go to recovery mode nor fastboot, what do i need to do to fix this?
br
pembasherpa01 said:
hey did you fixed the problem bro and how
Click to expand...
Click to collapse
man did you get it fixed? please I would like to know
Any news on this?
I briked my phone.. cycling boot logo, cannot get to fastboot, cannot get to recovery, EDL does not work and the phone does not even show up in computer...

'fastboot devices' command not working

Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!
D0CT0RFATE said:
Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!
Click to expand...
Click to collapse
Enable oem unlock in developer options
and does your phone show when you do " adb devices "
flairepathos.info said:
Enable oem unlock in developer options
and does your phone show when you do " adb devices "
Click to expand...
Click to collapse
Hey, I'm unable to locate the "oem unlock" option under developer options. However, i tried unlocking the bootloader yesterday with help of USB debugging. That didn't initially work, so i did the bootloader unlocking through the Asus app that i downloaded externally, which was successful (without PC).
That aside, adb seems to be working fine as the command "adb devices" results in showing my phone as connected. But 'fastboot devices' command simply does not work, so now I'm just left with a Bootloader unlocked phone.
Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D0CT0RFATE said:
Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
View attachment 5400501
Click to expand...
Click to collapse
It's probably something in the boot partition or tee partition, this is first time i see this but i did some research and found that it's not a hard locked device and releases with the developers proprietary engeneering drivers and user drivers
so the commands must be done in succession when enter fast boot using a bat script : here is the guide
[GUIDE][UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
DATA WILL BE WIPED SO MAKE A BACKUP (instructions are there in rar too) Unlocking 1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows 2. Install the drivers according to your OS and go the unlock...
forum.xda-developers.com
Thanks man, will try it sometime and give an update. As of now, this is my sole phone, so i'll work around with all this once i get a replacement. Until then, stock ROM it is
Quick update! 'Fastboot devices' command worked fine on my old PC with Windows 7 on it. Didn't require any extra steps nor did I go through any hassle like on the newer Windows 10. And ofc I was also able to install the custom recovery as well.
This clearly looks to be a Windows 10 issue.

Categories

Resources