Database Develop

Anyone being able to access recovery?

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

Phone bricked!

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"
}

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

'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.

Can't unlock bootloader on redmi 9 [SOLVED]

I've already searched for it and can't find anything. The closest I've got is to installing the USB driver. I opened driver_install.exe and still can't find the driver in Device Manager. I have OEM unlocking and USB debugging on. I also have my MI account linked and the unlock folder in C:\.

AlvaroE said:
I've already searched for it and can't find anything. The closest I've got is to installing the USB driver. I opened driver_install.exe and still can't find the driver in Device Manager. I have OEM unlocking and USB debugging on. I also have my MI account linked and the unlock folder in C:\.
Click to expand...
Click to collapse
Check this
{
"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"
}
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html

NOSS8 said:
Check this
View attachment 5737777​
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Click to expand...
Click to collapse
but the latest version on https://en.miui.com/unlock/index.html is 6.5.224.28

AlvaroE said:
View attachment 5738201 but the latest version on https://en.miui.com/unlock/index.html is 6.5.224.28
Click to expand...
Click to collapse
Not important, the path and the drivers are.

NOSS8 said:
Not important, the path and the drivers are.
Click to expand...
Click to collapse
Oh MiUsbDriver.exe is there thanks!
but i get this with or without phone connected in fastboot mode

AlvaroE said:
Oh MiUsbDriver.exe is there thanks!
View attachment 5738207 but i get this with or without phone connected in fastboot mode
Click to expand...
Click to collapse
Just connect the phone but not in Fastboot mode.

NOSS8 said:
Just connect the phone but not in Fastboot mode.
Click to expand...
Click to collapse
I instead used the driver from the driver folder

AlvaroE said:
I instead used the driver from the driver folder
Click to expand...
Click to collapse
Yeap, now edit your thread title by adding [SOLVED].

Cant unlock bootloader with several versionsofunlock tools.
Latest tool v2 alpha builds recognizes phone when it is started mi ui. Then it reboot phone to fastboot , windows gling glang sound and then tool shows no phone connected. Tried wuth 2 cables. Checked devicemanager- when mi note 9 in fastboot it appears as android with esclamation mark.
Tried to reinstall adb drivers and also usb qualcom. Same.
In windows or in ubuntu note 9 is always recognizes and can accesss its internal storage.

dzincha said:
Cant unlock bootloader with several versionsofunlock tools.
Latest tool v2 alpha builds recognizes phone when it is started mi ui. Then it reboot phone to fastboot , windows gling glang sound and then tool shows no phone connected. Tried wuth 2 cables. Checked devicemanager- when mi note 9 in fastboot it appears as android with esclamation mark.
Tried to reinstall adb drivers and also usb qualcom. Same.
In windows or in ubuntu note 9 is always recognizes and can accesss its internal storage.
Click to expand...
Click to collapse
Use the official tool and install the drivers (remove the drivers previously installed before and restart).
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html

Tried version in link- same situation.
Looks like problem is that windows is loosing connection when phone goes in Fastboot.
This is how device manager looks like when phone in fastboot

dzincha said:
Tried version in link- same situation.
Looks like problem is that windows is loosing connection when phone goes in Fastboot.
This is how device manager looks like when phone in fastboot
Click to expand...
Click to collapse
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf

Tried to turn off signature verification, but then bittlocker started to behave strange at boot up/couldnt enter code - 8 numbers.
Then tried to reinstall one of 4 ubuntu laptops. There got boot failure, prepared usb with another tool, then got another boot failure.
Maybe there are tools for Linux to do bootloader unlock?

dzincha said:
Tried to turn off signature verification, but then bittlocker started to behave strange at boot up/couldnt enter code - 8 numbers.
Then tried to reinstall one of 4 ubuntu laptops. There got boot failure, prepared usb with another tool, then got another boot failure.
Maybe there are tools for Linux to do bootloader unlock?
Click to expand...
Click to collapse
I had the case with an Intel W10 PC, as soon as I launched Miunlock the device disappeared, I tried all without success but with an Amd W10 PC, no problem (sometimes it's the opposite).
There are other ways to unlock the bootloader but I don't recommend them (do a search), too risky, anyway if you have a driver problem it won't change anything.
https://forum.xda-developers.com/t/...oader-of-xiaomi-devices-on-mac-linux.3782444/