Database Develop

New to nokia, not android/adb/etc

So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks

jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.

Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse

Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse

Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse

jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.

Xiaomi has auto bricked after update- need help

Hey guys, i have MI A2 cellphone, and after auto update programmed to three hours the smartphone show "AndroidONE" logo and then shutdown, i tried "Fastboot oem unlock", but it is my output:
PHP:
C:\Users\Lucas Daniel>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.000s
. I'm desperate, I do not know what to try anymore, I believe I do not have unlock OEM activated, someone can help me?
Sorry for bad english, i'm from brazilian.

@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.

sas.mar said:
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
Click to expand...
Click to collapse
Thanks, looks that, unfortunately, my unique solution is test-point for activate EBL Mode... I will leave the topic open for the case of i get other solutions... after 3 days, if not get, i will close and the unique solution will really test-point.

Try rebooting it a couple of times and see if it boots. Or plug it to a charger and try booting it once it starts to charge successfully. If all fails, flashing via EDL might be your only option.

Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).

Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?

Tianhe said:
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Click to expand...
Click to collapse
What is it command?

Aerobatic said:
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Click to expand...
Click to collapse
How can I do it? I leave the phone in the charger for a long time? Or do you need the power button for a long time?
I tried to press the power button for 2 minutes and nothing happened.
When i leave the smartphone on the charge, after 50 minutes, show for me 100% percent, so, i pressed power button and the screen stayed lock in "AndroidONE", nothing happened, until try again press power button.
The problem original comebacked to me

LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
I tried, the same ploblem happenned... don't work, unfortunely... :/

LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)

Phil_Smith said:
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Click to expand...
Click to collapse
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).

LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.

LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
Do as tabun1994 said.
This will hopefully get the system up again.
The commands I wrote would unlock the bootloader. What else could I have meant?
If you succeeded with tabun's method, then you probably would only need to enable "USB debugging" and "OEM unlocking" in the ROM's developer options (which you'll enable by hitting "build number" in settings like 10 times or so).
Then you would connect the device and accept the 'trust this device' warning.
After booting to fastboot now, the commands I wrote should work and unlock the bootloader (if you even want that when your system is running again).

tabun1994 said:
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
Click to expand...
Click to collapse
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl

The test point method is actually easy , you have to dissasemble the display , easy procedure , remove the battery and short the two test points with tweezerz or something ,and in the meantime you plug the usb cable into the computer. It should install the Qusb_Hub drivers , and with miFlash you should be able to reflash the firmware . I bought a phone that was in this state and fixed it using these steps.

No more solutions, I will do the test point method, thanks to everyone who tried to help otherwise.

LukeSkyPTBR said:
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
Click to expand...
Click to collapse
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.

tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!

LukeSkyPTBR said:
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
Click to expand...
Click to collapse
I execute bat archive but nothing happens in Mi A2 .-

tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
What is your smartphone?

I can't install twrp, make a hard reset, update by OTA, nothing O.o

SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.

SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.

Alcatel 1C suddenly says "can't load Android system"

I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks

BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.

Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?

BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx

When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?

BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..

It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?

BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.

OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.

I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.

BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.

hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards

Question Blackscreen loop booting

Hi,
I'm stuck with my phone: it still loopbooting every 5seconds, black screen, only retrolight.
Bootloader is unlocked. I wanted to install twrp, but fastboot says partition recovery not existing.
After reboot, i'm stuck with this mod.
Try to press volume - to go again in fastboot : phone is detected by computer, then disconnected because it's rebooting.
Do you have a solution to try for me?
Or what are EDL point? I've tried to make an ELD cable but did not work either.

How long is your bootloader keeps active? If it's about 5 - 10 seconds, you can try paste the command to flash stock recovery. I attached it if it's possible to do so (from the latest global). And by the way - THERE IS STILL NO ANY CUSTOM RECOVERY for our device, sadly. Actually there is some, but only mouse works.
The commands to paste:
fastboot flash boot twrp.img

KastenTop said:
twrp.img
Click to expand...
Click to collapse
Boot.img in this case, doesn't make much difference

Sorry but my bootloader don't stay active long enough. I just ear usb detection from PC , then one seconde later, usb disconnection sound.
Phone is still loop booting.

Can you try then pasting "fastboot oem edl" (emergency download mode). The screen should turn black

After that flash with Xiaomi Flash tool

I'm unable to enter in FastBoot mode.
Phone booting black, and every 5 seconds , reboot.
If i push "volume down " button, i hear it vibrate, but nothing. Reboot and not detected by fastboot.exe
I think i have, with all manipulation , relocked the bootloader.
My only way, will to find a way to boot in EDL mode.

Test points, which are unknown so far. You have to disassemble the phone, tho. And you can try to find these points yourself, at your own risk obviously. If you will succeed, pls tell me. We need to know the test points.

I was exactly in same trouble, use This guide that solve the issue.
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
Press mobile three buttons and connect cable to pc to enter brom mode. Because mtk models don't have test point. So don't need to open mobile.

proxynet said:
I'm unable to enter in FastBoot mode.
Phone booting black, and every 5 seconds , reboot.
If i push "volume down " button, i hear it vibrate, but nothing. Reboot and not detected by fastboot.exe
I think i have, with all manipulation , relocked the bootloader.
My only way, will to find a way to boot in EDL mode.
Click to expand...
Click to collapse
EDL mode in Xiaomi mediatek are called BROM mode. Don't need to disarm the mobile.

Thanks !

I tried, it works like a charm !
You're the best man

Zaiserr2 said:
EDL mode in Xiaomi mediatek are called BROM mode. Don't need to disarm the mobile.
Click to expand...
Click to collapse
nice tip!!!! this is a very helpfull guide for solve hard brick on mtk devices. i have decided never modding this phone, excep root when i need a full backup with migrate. because is much mure complicated than snapdragons. but your post is very very helpfull for who want to try anyway