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
Related
I'm trying to unlock bootloader. Checked all options in dev options like USB debugging and enable unlock bootloader.
Installed all the drivers. Booted into bootloader.
But when trying to see "adb devices", it doesn't show any devices.
For sometime, it shows some kedacom usb driver. I tried googling and tried to uninstall it and use google driver also. Even in device manager, it shows Android Device - Android ADB Interface, but still it shows nothing in list of devices attached in adb.
Also tried this thread - https://forums.oneplus.net/threads/solved-adb-is-not-working.347296/, but still doesn't work. Can someone help me out here?
{
"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"
}
Do you have TWRP installed? In that case flashing Super Su or Magisk from within TWRP should get you rooted. If TWRP isn't installed, Check for Funk Wizards thread in the official forum https://forums.oneplus.net/threads/...a-help-thread-ask-your-questions-here.477285/
Also, adb doesn't work from bootloader. It's fastboot in the bootloader. Enter recovery and check then
Seems like your phone is in bootloader/fastboot mode instead of in-rom ADB or TWRP ADB mode. This is the mode you're phone has to be in to be able to flash other recoveries like TWRP which however also requires your phone to be OEM bootloader unlocked (which completely wipes your phone), and from there you enter TWRP recovery using bootloader menu or power plus volume down, and there flash the latest 2.79 SR3 SuperSU to archive root/sudo functionality.
Either that or you actually did activate ADB under development options and accidentally installed the ADB device using the fastboot/bootloader driver instead of the ADB device driver.
When your in fastboot, you need to use fastboot devices as the command and other fastboot commands. You use adb devices command when your using adb, and connected with phone in recovery or booted.
I just installed the drivers that are on the phone when you plug it in in windows and minimal adb and fastboot from xda.
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Akhyll said:
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Click to expand...
Click to collapse
Excellent, enjoy.
I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"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"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.
Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.
I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.
My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?
can you put phone in fastboot?
DiesFrae said:
can you put phone in fastboot?
Click to expand...
Click to collapse
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device
Oline1032 said:
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device
Click to expand...
Click to collapse
did you check if fasboot reads your device?
cmd: fastboot devices
DiesFrae said:
did you check if fasboot reads your device?
cmd: fastboot devices
Click to expand...
Click to collapse
i checked command "fastboot devices" but it show blank. no message
Oline1032 said:
i checked command "fastboot devices" but it show blank. no message
Click to expand...
Click to collapse
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
link to adb drivers https://androidfilehost.com/?fid=24686681827312411
DiesFrae said:
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
Click to expand...
Click to collapse
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot
Oline1032 said:
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot
Click to expand...
Click to collapse
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID
DiesFrae said:
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID
Click to expand...
Click to collapse
not working:crying::crying::crying::crying::crying:
Oline1032 said:
not working:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
ask on telegram group then man, i don't know what's going on tbh
Try edl mode
Fastboot oem edl
Oline1032 said:
My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?
Click to expand...
Click to collapse
Hello, I currently have the same problem. Today I was converting my xiaomi mia2 to mi6x. Everything was normal, until at one point of the transfer miflash gave an error and the transfer stopped, checking the logs I find that simply the USB stopped working, the phone now does not signal by the usb. Now we have a paperweight, apparently. I have researched and apparently can try to repair the phone using the "test point method", which forces the EDL mode on the phone for a few seconds that you should take to flash the rom from MiFlash.
Please check this and try to do so, for the moment I have no tools because we have to disassemble the phone. I hope you have appropriate tools and you can tell me if it works! -> https://en.miui.com/thread-3524265-1-1.html
This other guide is for the A1, but it has information that may be able to help you. -> http://en.miui.com/thread-1680467-1-1.html
EDIT: I can confirm that I solved the brick with this method.
{
"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"
}
Hi, today i tried to install MIUI 10 following this video: https://www.youtube.com/watch?v=eD5ftq6lTKo
When i could installed it, i tried to re-lock the bootloader with this other video: https://www.youtube.com/watch?v=9C47rmEKkys
But when i reboot the phone, on screen was this message: The system is destroyed, press power button to shutdown.
I tried to unlock again the bootloader to install the system but i receive this message from cmd: FAILED (remote: Token Verify Failed, Reboot the device
)
I don´t know what to do, i tried with test points to flash with miflash, i tried with miflash unlock but i don´t have an account of xiaomi.
when i use this command: fastboot flashing unlock_critical i receive this message: Command not support: the display is not enabled'
Somebody help me :crying:
Flash stock ROM with mi flash
I tried that but miflash show this message: Mismatching image and device. Only have a success message when i flash the wayne rom but ends on 1 second but doesn't install the system.
On htcmania says because the drivers are wrong but i reinstalled from the tutorial ones, google drivers, and miflash drivers and always says the same.
Now i trying with EMMC dongle program(cracked) and it seems like it´s installing the system, but since yesterday, it looks last forever.
{
"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"
}
Well that program does not did anything, i discover that when the phone is on fastboot mode and plug off the battery, miflash make a process success but it last 24s and don´t do anything, maybe that could be useful for something.
I don´t know what more to do with my phone.
Click to expand...
Click to collapse
If ur bootloader is unlocked try
Fastboot reboot edl
Now try to flash with mi flash in this mode
Note: your phone will look like it's turned off (black screen) in this mode
---------- Post added at 02:35 AM ---------- Previous post was at 02:29 AM ----------
I noticed that you where trying to flash Wayne images in the photo that u attached? Do u own a mi A2 or a 6x?
If you convert your mi A2 to 6x you cannot relock your bootloader
And make sure to delete system update folder and change some Dev conf file to flash miui on your android one device
That command (Fastboot reboot edl) doesn't work, when i send it i get this error: Device is already locked!
The only way my phone can be on edl mode is by Test points, and the miflash says that my phone have a locked bootloader if i try to flash the system.
What is the output of this command
Fastboot oem unlock
hv2002 said:
What is the output of this command
Fastboot oem unlock
Click to expand...
Click to collapse
Araxielfenix said:
Click to expand...
Click to collapse
https://youtu.be/ypDU78c4w_Y
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...