Morelocal2 on my mi8 EE - Xiaomi Mi 8 Questions & Answers

Hey guys!
I have a mi8 EE with the CN-Rom. I have opend the developer mode. Activated the USB-Debugging. All fine.
Then i want install the Morelocal2 app and want to acitvate the grant i get the info "operation not allowed".
After this i want activate "Install via USB" and "USB debugging (security setting)" i get the msg "the device is temporary restricted 3-3".
Can anyone help me?
Best regards
peter

Same here......

Related

[Q] Helpp me , the pc don't recognized my ascend p7 driver!!!!

Hello everyone I ask a big help, for weeks trying to solve a problem I can not.
Practically a few weeks ago I tried to root my ascend p7 l10 but unfortunately it did not work and since then no pc recognizes the calling terminal device unknown ( request descriptor try to contact the supplier of the product ), but even if you do not install the right drivers recognized .
I tried installing drive adb generic either automatically or manually, but nothing .
Most do not know what to do you help me please. : ' (
TAscendp7 said:
Hello everyone I ask a big help, for weeks trying to solve a problem I can not.
Practically a few weeks ago I tried to root my ascend p7 l10 but unfortunately it did not work and since then no pc recognizes the calling terminal device unknown ( request descriptor try to contact the supplier of the product ), but even if you do not install the right drivers recognized .
I tried installing drive adb generic either automatically or manually, but nothing .
Most do not know what to do you help me please. : ' (
Click to expand...
Click to collapse
Is USB debugging enabled? You can turn it on in Settings -> All -> Developer options -> USB Debugging
If Developer options is not available, go to About phone and tap on Build number about 5 times. It will tell you if Developer options is unlocked.
Also, please specify OS version (which Windows or Linux) and ADB version (check with adb version command
I also debugging usb but not recognized by pc, the os is 4.4.2 firmware b619 help
I had the same problem and my phone was also not recognized b windows 7.
When I reÏnsalled the ADB drivers my problems were gone.
Maybe it works for you too.

Bootloader unlock failed: Command not allowed and OEM unlock option not available

Hello guys,
in these days I’m struggling for unlocking my Huawei P9 (Build number EVA-AL00C00B176).
I got the bootloader code, I installed last version of ADB and Fastboot and so on... (by the way I already did with several phones, so I have some experience about this)
The problem is when I launch the fastboot oem unlock ... command, I always get:
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock". In all the guides I found even on this forum I always found that if I cannot find this option I can easily ignore, but now I found I have an "FRP Lock" that I have to bypass in some way.
I really have no idea about how to do... anyone can send me to right direction? Thank you so much!
How to enable OEM Unlock:
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
https://www.youtube.com/watch?v=5AoDVMVlJEU
Thank you hanniSK,
the problem is that I cannot find that option anywhere.
ScareIT said:
..
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock".
...
Click to expand...
Click to collapse
Anyway, accordingly to the link you provided, it seems I cannot find it until I have enabled the PIN/Password/Lock protection.
I'm trying to disable it (and with this kind of Huawei, seems also quite difficult...), then I will report back.
ScareIT said:
Thank you hanniSK,
the problem is that I cannot find that option anywhere.
Click to expand...
Click to collapse
You must unlock Developer options in Menu..
Go to Settings-About device.
In About device locate the build number of your device. Tap the build number for 7 times to enable Developer options.
Problem solved! I've been able to unlock the bootloader.
First of all, I confirm that my smartphone doesn't have the "OEM Unlock" option. Of course I correctly enabled the Developer options menu (otherwise, how could I enable the USB Debugging option?), but the OEM Unlock was simply not visible (take a look to the following picture), anyway that is NOT important.
{
"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"
}
In the guide you posted, hanniSK, I found this sentence: "Custom images will be only flashed on your Android device if the option is enabled, if your device is already protected by some password or pin, no user will be able to enable this option" so, I passed the next 4-5 hours to find a way to disable the password request for the screen unlocking. Yes, you read well: more than 4 hours to do that, because I had to disable options, delete fingerprints, revoke certificates and so on... after every attempt to disable the screen unlock security, I found it "Disabled by administrator, encryption policy or credential storage".
Finally I solved with a soft reset (Advanced settings -> Backup & reset -> Reset all settings) and I managed to unlock the bootloader on the first try (yes, I lost all settings, but in any case is something that must happen when unlocking the bootloader).
Please explain the steps in detail
ScareIT said:
Problem solved! I've been able to unlock the bootloader.
Finally I solved with a soft reset (Advanced settings -> Backup & reset -> Reset all settings) and I managed to unlock the bootloader on the first try (yes, I lost all settings, but in any case is something that must happen when unlocking the bootloader).
Click to expand...
Click to collapse
Hello, Please explain in detail as to how you exactly unlocked because i also tried resetting all settings but nothing happened.
nukman5k said:
Hello, Please explain in detail as to how you exactly unlocked because i also tried resetting all settings but nothing happened.
Click to expand...
Click to collapse
What kind of error you get?
By the way, these is in detail my unlock process:
I obtained the unlock code (I asked it through Huawei support forms on their website)
I downloaded the ADB, Fastboot, drivers and so on, I recommend this post where you can find instructions and download links: http://forum.xda-developers.com/showthread.php?t=2588979
I did the soft reset (Advanced settings -> Backup & reset -> Reset all settings)
I connected the phone, than launched the command "fastboot oem unlock myunluckcodepoint1 "
After the reboot, my phone was unlocked.
Before, when I started this thread, I was stuck on the point 4 because the command didn't succeed and I always got error (I was jumping from point 2 directly to point 4), after I did the setting reset I managed to unlock immediately.
On step 4 my phone just says Waiting For Device. None of the drivers are missing. Also phone does not have OEM Unlock options, even after factory reset. Not sure what to do.
ScareIT said:
Hello guys,
in these days Iâ??m struggling for unlocking my Huawei P9 (Build number EVA-AL00C00B176).
I got the bootloader code, I installed last version of ADB and Fastboot and so on... (by the way I already did with several phones, so I have some experience about this)
The problem is when I launch the fastboot oem unlock ... command, I always get:
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock". In all the guides I found even on this forum I always found that if I cannot find this option I can easily ignore, but now I found I have an "FRP Lock" that I have to bypass in some way.
I really have no idea about how to do... anyone can send me to right direction? Thank you so much!
Click to expand...
Click to collapse
Hey bud I have the same model as you with later firmware. I am unable to unlock my bootloader. It says waiting for device. When I put the phone in fastboot mode I see phone locked at the bottom of the Android robot
GodKingKnight said:
Hey bud I have the same model as you with later firmware. I am unable to unlock my bootloader. It says waiting for device. When I put the phone in fastboot mode I see phone locked at the bottom of the Android robot
Click to expand...
Click to collapse
The fastboot screen you see is right, the "waiting for device" message is usually connected to a missing driver problem, but you also said that no driver is missing.
Anyway, I recommend you to double check the drivers, to check if any device is missing or wrongly marked in your (windows) device manager, finally try to type these 2 commands (from command line):
fastboot devices (then post here the ouput)
and
adb devices (then post here the ouput)
Try to run these 2 commands also with phone booted normally and let's see...
ScareIT said:
The fastboot screen you see is right, the "waiting for device" message is usually connected to a missing driver problem, but you also said that no driver is missing.
Anyway, I recommend you to double check the drivers, to check if any device is missing or wrongly marked in your (windows) device manager, finally try to type these 2 commands (from command line):
fastboot devices (then post here the ouput)
and
adb devices (then post here the ouput)
Try to run these 2 commands also with phone booted normally and let's see...
Click to expand...
Click to collapse
Both those commands return nothing. Drivers are confirmed to be correct. After a lot of research I'm finding this Chinese variant has yet to be rooted or even custom recovery. I'm sad to report my Huawei may just be incompatible and permenantly locked. Bootloader code was also purchased through unofficial app DC unlocker
GodKingKnight said:
Both those commands return nothing. Drivers are confirmed to be correct. After a lot of research I'm finding this Chinese variant has yet to be rooted or even custom recovery. I'm sad to report my Huawei may just be incompatible and permenantly locked. Bootloader code was also purchased through unofficial app DC unlocker
Click to expand...
Click to collapse
Try to post as much information you can about "this Chinese variant" (I thought we have the same one), anyway the adb and fastboot commands must respond something, independently if the phone could be unlocked or not.
What do you get if you run the commands when the phone is switched on normally?
Did you also try to disable/enable the "USB Debugging" option?
Also try to post a screen of your device manager. Can help.
ScareIT said:
Try to post as much information you can about "this Chinese variant" (I thought we have the same one), anyway the adb and fastboot commands must respond something, independently if the phone could be unlocked or not.
What do you get if you run the commands when the phone is switched on normally?
Did you also try to disable/enable the "USB Debugging" option?
Also try to post a screen of your device manager. Can help.
Click to expand...
Click to collapse
I have tried that. EVA-AL00 Huawei P9. Unfortunately I just can't get it to work.
Hi,
I had the same problem, same fault while trying to unlock boot loader. After I disabled “Phone-Finder“ in the Huawei menu or security option, then I could unlock the bootloader.
Also in my dev-menu, the “oem-unlock“ option is not available. Seems, on the EVA-AL versions, those options are linked to each other.
Please check, and reply, if this also worked for you, then we may can mark this topic as “solved“
Please give it a try, good luck
Settings/Advanced-settings/Security/Phone-Finder/ enable Phone-Finder off
raTHiopA said:
Hi,
I had the same problem, same fault while trying to unlock boot loader. After I disabled “Phone-Finder“ in the Huawei menu or security option, then I could unlock the bootloader.
Also in my dev-menu, the “oem-unlock“ option is not available. Seems, on the EVA-AL versions, those options are linked to each other.
Please check, and reply, if this also worked for you, then we may can mark this topic as “solved“
Please give it a try, good luck
Settings/Advanced-settings/Security/Phone-Finder/ enable Phone-Finder off
Click to expand...
Click to collapse
You are genius bro ! Worked for me thanks ! :victory:
This also worked for me, thanks. "After I disabled “Phone-Finder“ "
If you can't see anything after these commands, computer doesn't see your device. Make sure that you enabled USB Debugging in Developer's setting and installed all needed drivers. In some case it's important to use original cable for your device and not to connect other devices while you are working with yours
I ain't getting unlock code from emui
I have a Ascend P7 L07 here with same problem, how i can flash boot.img? My smartphone is bricked and not entering on system
OmegaMotorolaBr said:
I have a Ascend P7 L07 here with same problem, how i can flash boot.img? My smartphone is bricked and not entering on system
Click to expand...
Click to collapse
This is the P9 forum, you need to post in the correct device forum.

Stuck on process of unlocking bootloader

Hello guys, I know there is a LOT of these threads complaining about bootloader unlocking, but I have tried everything that is available on the internet and not being successful. So I have been trying for around months to unlock the bootloader on my mi5 phone. I asked for permission and it was given the next day. After I have the permission, I:
Enabed developer mode
Enabled oem unlock
Enabled usb debugging
I used the old MiFlashUnlock_1.1.0317.1_en, the unlocking process stop at 50%, it tells me to update the unlocker tool, then I decided to download the newest miunlock 2.3.803.10, now I succesfully verify my device and go up to 99% but this time it tells me "Current account is not bound to the device" and ask me to go to Developer Options > Mi Unlock Status. Then I go to "Mi Unlock Status" and it says "Couldn't verify, wait one minute or two and try again". Another error.
Things I have tried:
Tried global stable rom
Tried global developer rom
Wait few more days (even months)
Tried VPN to china
I have tried literally everything, what do I do now? I read somewhere people say you dont need to bother about the "mi unlock status" just keep trying till you succeed.
yoelpro said:
I used the old MiFlashUnlock_1.1.0317.1_en, the unlocking process stop at 50%, it tells me to update the unlocker tool, then I decided to download the newest miunlock 2.3.803.10, now I succesfully verify my device and go up to 99% but this time it tells me "Current account is not bound to the device" and ask me to go to Developer Options > Mi Unlock Status. Then I go to "Mi Unlock Status" and it says "Couldn't verify device please wait one minute or two and try again". Another error.
I have tried literally everything, what do I do now? I read somewhere people say you dont need to bother about the "mi unlock status" just keep trying till you succeed.
Click to expand...
Click to collapse
Probably a stupid question, but after going to the developer options -> Mi Unlock status, have you entered your email address and password that you used to ask for unlock permissions?
It is some time ago i have done this, but you need to connect your account (email and password it was, i think) on that page, and after that you can use the PC program to unlock and there also use the same account settings.
elot01 said:
Probably a stupid question, but after going to the developer options -> Mi Unlock status, have you entered your email address and password that you used to ask for unlock permissions?
It is some time ago i have done this, but you need to connect your account (email and password it was, i think) on that page, and after that you can use the PC program to unlock and there also use the same account settings.
Click to expand...
Click to collapse
After I click the "Add account and device" button, it just directly says "Couldn't verify, wait one minute or two and try again". No chances to enter the account details. But actually I have already entered my mi account at the accounts section in setting. Thank you for trying to help
I am also facing exact same issue on my Redmi 5a (riva). Please let me know if you were able to find any solution
anyone fixed this problem?
Anyone can solved this problem
exact same issue here on Redmi Note 4X -
Can't bind the account to device in Developer Options/Mi Unlock.
Error: "Couldn't verify, wait one minute or two and try again"
Is there anything that could block the connection to Xiaomi servers?
Please check (software) firewall, anti virus and router settings. Also try alternative DNS such as Google DNS or Quad9.

Alcatel 1S 2019 (5024D) ROOT

Hello XDA Developers
I have been running for two days through Internet (including XDA) and try to find any valuable solution how to root my phone Alcatel 1S 2019 (5024D) on Windows 10.
I did:
- unlock developer mode and activated "OEM unlocking" and "USB debugging"
- installed "Minimal ADB and Fastboot" and when i connect the phone and run "adb devices" i can see my device on the list
- found, that in "Device manager" after connecting the phone i get a lot of: "Spreadtrum Phone" devices under "Other Devices" - those not workin properly, sice there is yellow exclamation mark next to the icon
- tried to install the drivers for the case from above - no luck. Keep getting errors while installing the drivers.
- tried: Framaroot https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276 without luck.
I found:
- https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713, but there is no clear information how to get to the fastboot, and the PWR and VOL+ wont work as stated in the post
- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, but here I need to unlock bootloader, but when I am trying to do that by using "Minimal ADB and Fastboot" tool, i receive error:
FAILED (remote: Not implemet.)
finished. total time: 0.000s
I suspect that i should start from the drivers. But now i cannot find any clear information how to do that.
Obviously I tried to install some drivers, but without luck. I found dozens of step by step solutions how to properly implement drivers, but always get the same error (above) and can see in device manager, that after connecting the phone still not all devices has been installed properly.
Is someone from here have an experience in rooting that exact phone and will help me?
Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.
Sorfeus said:
Hi there, have the same issue, is no driver problem. Seems at present this particular phone CANT be rooted Spent days on it too. Hope someone can help. Regards A.
Click to expand...
Click to collapse
Hello @Sorfeus. I am still fighting with that phone, but I am 80% sure, that there is no need anything else than normal Android USB drivers and ADB/fastboot. What I have noticed is when I have used original Alcatel USB cable and install above drivers still all commands you are able to run. I believe, that there is other problem though. Even when you unlock Developer options in Android and then switch on ability to unlock the bootloader actually you are not able to do this from the fastboot sight. The message I receive is that the option not exist. So you cannot even unlock bootloader not mention about running root ROM.
But again. I am not an expert but I think, that you do not need any spreadtrum drivers.
If only I had the boot image for my device Alcatel 1S (2020) 5028D.. then maybe I could have had root with magisk right now. Since no flashable firmware for my device is out there anywhere to be found and backing up boot partition on device requires root or a custom recovery in the first place, I seem unable to root it for now.
I was able to unlock bootloader with simple "fastboot flashing unlock" command though.
If you wanna do that, do the following: (and I assume you know how to type in the commands)
With "OEM unlocking" and "USB debugging" settings activated, connect phone to pc and type in command "adb reboot bootloader".
Next you type "fastboot flashing unlock" and "fastboot flashing unlock_critical".
Press volume up button on phone to confirm.
Now you type in command "fastboot reboot" and thats all.
My device is with Mediatek SoC and I had Mediatek drivers installed by Windows Update but I dunno if it is a driver issue you're having since you at least are able to run "adb devices" and you do see your device being listed there.
If you are able to unlock bootloader however you could proceed to try doing how this article describes on how to do (getdroidtips.com).
I have to also warn about that stock rom getdroidtips links to is for model 5024J not 5024D, flash a boot.img for wrong device model and you'll most certainly brick your device.
I managed to find stock roms 5024D while searching around the web but none that are free download or they require a password to unpack... could be scams, I dont know. Feels sketchy AF...
Anyways here is some of them I found and I guess these are good ones but needs a premium account:
Alcatel 1S 5024D EEA [needrom.com]
Alcatel 1S 5024D TMST [needrom.com]
Alcatel 1S 5024D ALAP [needrom.com]
Alcatel 1S 5024D ALRU [needrom.com]
[Update] found out this rom and is free download so I'll add it in here too:
Alcatel 1S 5024D ALRU
This might also be of interest if you want to know about how to extract and get the boot.img:
https://androidmtk.com/extract-spreadtrum-pac-file
Hello @RavZ75
Thank you for the clear information regarding unlocking. I didn't knew this command until you stated it in the above post.
Unfortunately I cannot check it, since I sold the phone.
Anyway, I believe that it is a good Idea to keep sharing rooting information in this thread since the question has been already asked.
Maybe someone else will use your knowledge to root it's phone.
Here's how I rooted mine: https://forum.hovatek.com/thread-32678.html
It's a long and complicated process, but it works.
FrescoLibra said:
Hi guys,
This is how I unlocked my bootloader and thats all I can do with this phone without Factory Firmware. I can not Root my device in any way. If anyone has a Scatter File for the Alcatel 1s 5024D 2019, please post so we can help each other out with this nasty phone's security
Bootloader Unlock: You need Linux, (eg) Parrot OS or Ubuntu!
Spreadtrum SC9863A - postmarketOS
wiki.postmarketos.org
Click to expand...
Click to collapse
That's only part of the process, but then you need to sign a modified boot/recovery image, edit the vbmeta image and flash both. It's all in the guide I linked above.
Hi all! I'm almost blown it. I don't know English I write through an interpreter. ROOT obtained in Russia.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is a link to the bootloader unlock and firmware instructions with root 01003.
Alcatel OneTouch 5024D 1S - Обсуждение - 4PDA
Alcatel OneTouch 5024D 1S - Обсуждение, Смартфон, 5.5"
4pda.to
This is the forum itself in the header of which there is a lot of useful things. TWRP and Magisk update.
With an automatic translator, everything will be clear.
Good luck with root rights.

Redmagic 3S Device Corrupt, debugging mode is not activated Help

Hello everyone, first of all thanks for your advice,
I have a Global RM3S, I updated to the Chinese version with android 11 with the debugging options activated and of course the active oem unlocking,
but I had errors in some applications for changing from global to Chinese so I did a factory reset and it worked excellent,
but for my work I needed a special application and with the Chinese version it didn't work, so I had to go back to the global version,
but when doing it from the recovery it gave me the error "DEVICE CORRUPT "I read in another thread that I had to unlock the OEM
before loading the rom in order to unlock the bootloader and thus repair my computer, I don't have much experience in this matter so I don't understand what to do, can you help me?
T_T my phone has been like this for two weeks and the local technicians say they can't repair it, I wanted to buy another logic card but I can't find anything,
I urgently need to repair my phone because I don't have another, and I need it to dial from my entry, sales, exits, etc. , from my work, greetings to all.
I tell you, I have the drivers well installed on my pc, fastboot detects my device without problem, also when trying the steps to copy the files from the Chinese or global rom, it does not give any error but it always returns to "DEVICE CORRUPT"
if I try to unlock via FASTBOOT with
fastboot oem nubia_unlock NUBIA_NX629J
no problem but with
fastboot flashing unlock
tell me error
Come pm to can help u
RZaR2001 said:
Come pm to can help u
Click to expand...
Click to collapse
Hello,
I am facing the same problem please help me my laptop is not recognizing my phone while using twrp
please help
ashwin_dutt123 said:
Hello,
I am facing the same problem please help me my laptop is not recognizing my phone while using twrp
please help
Click to expand...
Click to collapse
Can you provide screenshot from drivers?
is it detected by adb driver or not?
sometimes what i am doin on windows is reinstalling adb driver (uninstall and reinstall)
if you cannot do anything, do fastboot and try brick tools that provide in forum to restore anything to global rom, and reflash again on CN ROM
أنا Unlock bootloader but my devices is corrput

Categories

Resources