Related
I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?
hjaxuan said:
I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?
Click to expand...
Click to collapse
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here
muradulislam said:
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here
Click to expand...
Click to collapse
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed
hjaxuan said:
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed
Click to expand...
Click to collapse
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.
muradulislam said:
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.
Click to expand...
Click to collapse
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery
hjaxuan said:
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery
Click to expand...
Click to collapse
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...
muradulislam said:
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...
Click to expand...
Click to collapse
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
And power + vol down also boots to fastboot mode?
If this is the case then I am of no help to you at all. Another user is facing the same problem and no solution there till now.
hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
Phone off, disconnect cable to PC, vol+ and power - enter to recovery
DRUGER said:
Phone off, disconnect cable to PC, vol+ and power - enter to recovery
Click to expand...
Click to collapse
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img
muradulislam said:
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img
Click to expand...
Click to collapse
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed
hjaxuan said:
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed
Click to expand...
Click to collapse
Just try
Fastboot OEM unlock xxxxxx
Followed by
Fastboot flash recovery xxxxxx.img
Many users reported that this worked. Don't do anything in between.
hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
build number your firmware???
druger said:
build number your firmware???
Click to expand...
Click to collapse
nem-l22c636b140
hjaxuan said:
nem-l22c636b140
Click to expand...
Click to collapse
You may put screenshot comand line whith comand flashboot
Also try this TWRP https://drive.google.com/file/d/0B1Ez6wAY1mj6c0xxaTBUWmZVN1k/view?usp=sharing (Chinese)
Huawei E-Recovery is a secondary recovery. Try adb reboot recovery.
Sent from my honor 5X using XDA Labs
DRUGER said:
build number your firmware???
Click to expand...
Click to collapse
U don't have proper drivers installed.
Hi all ! I had exactly the same issue... The problem was solved by using the TWRP-CN image pointed by Druger ! (thank you mate) Any other attempt resulted into a fail. Twrp is of course in chinese language but follow this, and your life will be a bed of roses : youtube.com/watch?v=KOhR92EKD7A
Hope this will help
Note : Chinese NEM-AL10 2gigs ram model.
Huawei honor 5c
Can somebody help me my huawei (5c) i tried to install twrp on phone and it say command is not allowed. Im unlocked bootloader, i writed adb reboot bootloader, adb fastboot flash recovery xxxx.img and then it says command not allowed. Ps my file name is twrp and i try twrp.img on flashing
Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Why lock? Why not just use Magisk? That works fine with Android Pay.
You don't need to lock your bootloader to use Netflix
nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.
mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Yepi69 said:
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Click to expand...
Click to collapse
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
NotCat_ said:
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
Click to expand...
Click to collapse
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Njaiker said:
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Click to expand...
Click to collapse
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
NotCat_ said:
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
Click to expand...
Click to collapse
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Yepi69 said:
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Click to expand...
Click to collapse
will try to do that. all tho i think screen goes off first thanks for your help and sparking some hope into me and my phone <3
It finally booted up! After having some hard time shorting test points i finally did and it booted up just fine! Big thanks to @Yepi69
use custom rom
NotCat_ said:
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
Click to expand...
Click to collapse
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
honey ghumaan01 said:
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
Click to expand...
Click to collapse
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
try other slot
NotCat_ said:
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
Click to expand...
Click to collapse
try on both slots
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
Whats the fastboot command to change slots?
Mtp works fine tho.
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
the command to chang slot with fastboot is
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b not sure can be fastboot set-actve a/b , you should use pitch black recovery instead of simple twrp
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
dm me on instagram hsghumaan01
honey ghumaan01 said:
fastboot set_active a/b
Click to expand...
Click to collapse
That command doesn't seem to work on my pc :/ cmd just gives out all commands when i type
fastboot set_active B (on pc)
And nothing happens :/
Are there any particular adb/fastboot files i need to download?
MarcusMario0605 said:
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
Click to expand...
Click to collapse
Took a screenshot of your comment for later, thanks!
Are there any particular adb/fastboot files i need to download?[/QUOTE]
use this tool; https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this tool,can disable driver signature,Install all drivers,qcom,etc)
https://forum.xda-developers.com/showthread.php?t=2588979
Download SDK Platform-Tools for Windows ; https://developer.android.com/studio/releases/platform-tools
QDLoader HS-USB Driver ; https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU
fastboot edl (useful) ; https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8
See and here how to use adb & fastboot from any directory on pc ; https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
all of these are useful tools,that you must to have on pc
sry for english
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
I already flashed the phone with edl test points. I'm running havoc os +hex
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
Why not use oem unlock?
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?
Hi there,
I just bought a pixel 5 phone and tried to unlock bootloader
After I made the steps described in that post for P5 ... after flasing the magisk img file I wanted to reboot the phone but it is stuck on the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device.
link..."
What can I do to fix that issue? I'm trying to root it and install lineageos after.
Regards,
LE: Most probably I run the command with fastboot installed with apt in ubuntu 20
Version from fastboot from ubuntu: fastboot version 1:8.1.0+r23-5ubuntu2
LEE:
Pfiu ... I was pretty scared ... fixed it with this link: https://flash.android.com/devices
Can somebody let me know please if the issue was because of the bad fastboot version?
Also ... I saw there is a kddi version and without it ... tried without kddi as I don't know exactly to verify if I'm having kddi
I wanted to try again to root the phone. Went to developer options and now oem unlocking is grayed, i cannot change id and it says:
"bootloader is already unlocked".
Click to expand...
Click to collapse
Then I said to go to fastboot mode but when I'm running the command:
Code:
fastboot devices
it cannot see my phone now, I'm seeing an empty output now.
Also ... when I want to start the phone I'm seeing:
"the bootloader is unlocked and the integrity ..."
Click to expand...
Click to collapse
Can somebody please help me? what should I do?
What's the problem? The message appears on some devices that had their bootloader unlocked. So the message alone does not matter.
The problem is that I don't have root access and I want to try again those steps for root
...
I want to make the steps described for how to unlock the bootloader and have root permissions as I want to install then lineageos on the phone
Thank you
LE: so the problem is described above in more details and what exactly I did before coming at this situation
So I was able to see again the device in fastboot (enabled stay awake)
When I tried command:
Code:
fastboot flashing unlock
it said it is already unlocked
Then I flashed magisk img but I can't see it on my phone
Any advice please?
dallas87 said:
So I was able to see again the device in fastboot (enabled stay awake)
When I tried command:
Code:
fastboot flashing unlock
it said it is already unlocked
Then I flashed magisk img but I can't see it on my phone
Any advice please?
Click to expand...
Click to collapse
Pull down your notifications and allow USB debugging after plugging in on your PC perhaps? Also check the box to always allow.
I don't try anymore to root my phone as I don't want to use lineageos custom rom. I already installed one that doesn't need root.
Thanks
LE: What I installed without root required had issue for me with sim manager
I finally rooted my phone and installed lineageos that is working well