Hi, I have a Moto One (deen retail) XT1941-3, and I had unlocked the bootloader, but now I want to lock it again, I followed instructions I saw on the internet, rooted it, installed the stock rom, etc. But when I go to the settings, in OEM unlock it appears: The bootloader is already unlocked. and also it is disabled and greyed out. I saw here on the XDA forum that I needed to root, but I already did!! Can someone help me!?
FilipeET said:
Hi, I have a Moto One (deen retail) XT1941-3, and I had unlocked the bootloader, but now I want to lock it again, I followed instructions I saw on the internet, rooted it, installed the stock rom, etc. But when I go to the settings, in OEM unlock it appears: The bootloader is already unlocked. and also it is disabled and greyed out. I saw here on the XDA forum that I needed to root, but I already did!! Can someone help me!?
Click to expand...
Click to collapse
Hi, be careful! Never lock the bootloader if you have a custom rom or root installed! Otherwise, you will block the phone and it will no longer be possible to start it. You have to install stock rom and type
Code:
fastboot oem lock
command. Good luck
Jan Skokan said:
Hi, be careful! Never lock the bootloader if you have a custom rom or root installed! Otherwise, you will block the phone and it will no longer be possible to start it. You have to install stock rom and type
Code:
fastboot oem lock
command. Good luck
Click to expand...
Click to collapse
Thanks, I didn't know I couldn't have root, but I already have the stock rom installed and I removed the root, but it still gives this error. Unfortunately, I couldn't find anything here on the forum about this.
Look:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
FilipeET said:
Thanks, I didn't know I couldn't have root, but I already have the stock rom installed and I removed the root, but it still gives this error. Unfortunately, I couldn't find anything here on the forum about this.
Look:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The error tells you that you have to enable "oem unlock" in the developer settings, otherwise it won't work.
Jan Skokan said:
The error tells you that you have to enable "oem unlock" in the developer settings, otherwise it won't work.
Click to expand...
Click to collapse
Do this and try again
{
"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"
}
I Can't, It's greyed out :
Try this command
Code:
fastboot flashing lock
FilipeET said:
I Can't, It's greyed out :View attachment 5923601
Click to expand...
Click to collapse
Look
Jan Skokan said:
Look
View attachment 5923621
Click to expand...
Click to collapse
Thank you, would you know how long I need to wait to block it again? Because I unlocked the bootloader in January, I tried to block it but it didn't work, so this week I tried again, it didn't work, I already reinstalled the stock rom about 6 times but it never worked and every time I waited more than 7 days but it never worked , I'm starting to think my device is having issues.
When I run "fastboot flashing lock" it gives the same error, but says "(bootloader) This creates a recovery to unlock if Android fails to boot."
I don't have much experience with A/B devices, I started in January, before that I had a samsung so I used odin and it also only had A slot, which was much easier.
Did I do something wrong?
FilipeET said:
Thank you, would you know how long I need to wait to block it again? Because I unlocked the bootloader in January, I tried to block it but it didn't work, so this week I tried again, it didn't work, I already reinstalled the stock rom about 6 times but it never worked and every time I waited more than 7 days but it never worked , I'm starting to think my device is having issues.
When I run "fastboot flashing lock" it gives the same error, but says "(bootloader) This creates a recovery to unlock if Android fails to boot."
I don't have much experience with A/B devices, I started in January, before that I had a samsung so I used odin and it also only had A slot, which was much easier.
Did I do something wrong?
Click to expand...
Click to collapse
Have you been waiting since January? So I really don't know what to do with it.. And why do you want to lock the bootloader?
I also have an unlocked bootloader on my Motorola + I have a custom rom installed and I have root and I don't want to go back to the stock rom
Jan Skokan said:
I also have an unlocked bootloader on my Motorola + I have a custom rom installed and I have root and I don't want to go back to the stock rom
Click to expand...
Click to collapse
Actually I just wanted to remove the unlocked bootloader warning image...
but i was also happy with my android 10 but now that you mentioned not blocking i thought i would not try to block it again!
But, do you know why slot B does not work?
because it is also another reason, I always wanted to install something in slot B but it gives an error.
FilipeET said:
Actually I just wanted to remove the unlocked bootloader warning image...
but i was also happy with my android 10 but now that you mentioned not blocking i thought i would not try to block it again!
But, do you know why slot B does not work?
because it is also another reason, I always wanted to install something in slot B but it gives an error.
Click to expand...
Click to collapse
I'm sorry, but I don't know.
Jan Skokan said:
I'm sorry, but I don't know.
Click to expand...
Click to collapse
No problems. Thank you for help!!
Related
Hey.
So the other day I tried to flash another firmware to my ZU and everything was fine.
Everytime I'm on this, it takes me several times to get what I exactly want(e.g. successfully installing SuperSU, Xposed, flashing busybox and TWRP etc.).
This time I faced a big problem after a few times of playing about: I apperantly can't anymore use fastboot in order to install TWRP. This is what happens when I try to flash it:
{
"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"
}
I sought for similar errors in this forum and everyone seems to believe it's a bootloader problem. Hence, I checked it via Flashtool and this is what I get:
Would anyone kindly assist me on how to fix this issue?
My phone has got useless since this problem was faced.
Thanks in advance.
Try disabling USB debugging
sairaj rane said:
Try disabling USB debugging
Click to expand...
Click to collapse
It did not help sadly.
By the way, should it not be off by default before booting into Android for the first time just after an attempt of firmware flashing?
I used to install TWRP and, using that, SuperSU before the first boot and I would have no problems encountered then. Now I do have.
aliansahere said:
Hey.
So the other day I tried to flash another firmware to my ZU and everything was fine.
Everytime I'm on this, it takes me several times to get what I exactly want(e.g. successfully installing SuperSU, Xposed, flashing busybox and TWRP etc.).
This time I faced a big problem after a few times of playing about: I apperantly can't anymore use fastboot in order to install TWRP. This is what happens when I try to flash it:
I sought for similar errors in this forum and everyone seems to believe it's a bootloader problem. Hence, I checked it via Flashtool and this is what I get:
Would anyone kindly assist me on how to fix this issue?
My phone has got useless since this problem was faced.
Thanks in advance.
Click to expand...
Click to collapse
Use Androxyde Flashtool. Boot into fastboot and select TWRP as the kernel. That should work.
hector67 said:
Use Androxyde Flashtool. Boot into fastboot and select TWRP as the kernel. That should work.
Click to expand...
Click to collapse
Again, the same output:
30/022/2016 15:22:20 - INFO - Device connected in fastboot mode
30/022/2016 15:22:26 - INFO - Now plug your device in Fastboot Mode
30/022/2016 15:22:33 - INFO - Selected kernel (boot.img or kernel.sin): D:\Root\HOWTO\fastboot\twrp-2.8.7.0-togari.img
30/022/2016 15:22:33 - INFO - Flashing selected kernel
30/022/2016 15:22:33 - INFO - sending 'boot' (14018 KB)...
30/022/2016 15:22:33 - INFO - OKAY [ 0.452s]
30/022/2016 15:22:33 - INFO - writing 'boot'...
30/022/2016 15:22:33 - INFO - FAILED (remote: Command not allowed)
30/022/2016 15:22:33 - INFO - finished. total time: 0.455s
30/022/2016 15:22:33 - INFO - FASTBOOT Output:
sending 'boot' (14018 KB)...
OKAY [ 0.452s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.455s
30/022/2016 15:22:33 - INFO - Please check the log before rebooting into system
Click to expand...
Click to collapse
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Sithu Htun said:
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Click to expand...
Click to collapse
Hey.
Thanks for helping me.
Will you elaborate more on '[d]isabl[ing] MyXperia'?
How may I do it?
I've locked and then unlocked the bootloader using Androxyde's many times since. But no change.
Please guide me more because it hurts without phone for more than a week, you can imagine!
Sithu Htun said:
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Click to expand...
Click to collapse
Hey.
Thanks for helping me.
Will you elaborate more on '[d]isabl[ing] MyXperia'?
How may I do it?
I've locked and then unlocked the bootloader using Androxyde's many times since. But no change.
Please guide me more because it hurts without phone for more than a week, you can imagine!
Try unlocking manually using command prompt
fastboot -i 0x0fce oem unlock 0xUnlockCode
Sithu Htun said:
Try unlocking manually using command prompt
fastboot -i oem unlock 0x0fce 0xUnlockCode
Click to expand...
Click to collapse
Error:
Sithu Htun said:
Try unlocking manually using command prompt
fastboot -i oem unlock 0x0fce 0xUnlockCode
Click to expand...
Click to collapse
Error:
sorry my bad.
fastboot -i 0x0fce oem unlock 0xUnlockCode
try minmal app from here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
Sithu Htun said:
sorry my bad.
fastboot -i 0x0fce oem unlock 0xUnlockCode
Click to expand...
Click to collapse
andro971 said:
try minmal app from here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
Click to expand...
Click to collapse
No help?
Finally I managed to partially solve this problem.
Steps:
- rooting my phone using Kingoroot
- restoring TA backup
- unlocking my bootloader
- flashing a ROM excluding TA partitions
No I don't get that error and I can successfully flash the recovery.
fastboot flash recovery twrp-2.8.7.0-togari.img
sending 'recovery' (14018 KB)...
OKAY [ 1.042s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.962s
Click to expand...
Click to collapse
But the new problem is that I can't boot into it. I used to boot into recovery mode by keeping volume down and power button simultaneously until the phone vibrates when I had to release the power button but still keep the volume down key. This doesn't work. I also tried fastboot command to reboot into recovery but no result.
Will anyone help?
aliansahere said:
Finally I managed to partially solve this problem.
Steps:
- rooting my phone using Kingoroot
- restoring TA backup
- unlocking my bootloader
- flashing a ROM excluding TA partitions
No I don't get that error and I can successfully flash the recovery.
But the new problem is that I can't boot into it. I used to boot into recovery mode by keeping volume down and power button simultaneously until the phone vibrates when I had to release the power button but still keep the volume down key. This doesn't work. I also tried fastboot command to reboot into recovery but no result.
Will anyone help?
Click to expand...
Click to collapse
Since your bootloader is unlocked try flashing the new xzu bootloader which Sony provided connect your device to Emma via flash mode and flash the new service
[SORTED OUT]
By fastboot gives the following error
{
"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"
}
and rsd lite
Does anyone know how to fix this error?
Looks like you forgot unblock your bootloader.
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
rodrigofvl said:
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
this flashing_locked
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Defaultnickname said:
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Click to expand...
Click to collapse
rodrigofvl said:
Click to expand...
Click to collapse
Look at this thread:
https://forum.xda-developers.com/2015-moto-g/help/updated-moto-3-2015-stuck-bootloop-to-t3485191
did not work
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
phone doesn't turn on with power button
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
phone doesn't turn on with power button so we can't show it but if it plugs to usb 2 port windows detect as "motorolla ADB interface" in cmd command ,we can detect it as fastboot devices, but we can't do anything because moto z with that condition, it doesn't have any Partitions
is there a problem with no solution ? :angel:
rodrigofvl said:
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
Click to expand...
Click to collapse
my recovery not working.... its damaged. Do you have any solutions?
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be 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"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
iwanttoroot said:
I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
Click to expand...
Click to collapse
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
Do you mean one of those USB extender things like 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"
}
iwanttoroot said:
Do you mean one of those USB extender things like this? View attachment 5724301
Click to expand...
Click to collapse
yes, that's exactly what I mean.
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
Okay thanks I'll try
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
I have now successfully rooted my motorola g6 after 2 years of struggles, thank you.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
You, sir... are a genius! thank so much!
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
alexestanislau said:
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
Click to expand...
Click to collapse
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
WoKoschekk said:
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
Click to expand...
Click to collapse
Actually the cellphone wasnt mine until yesterday.. I dont know if they changed anything previously.. but there is no menu at all, just black screen
Hello!
My goal is to install the last official build of Lineage OS for ANE-LX3 which is version 16 (android 9) that I downloaded from: https://archive.org/details/lineageos20210217 (specifically https://archive.org/download/lineag...lineage-16.0-20210215-nightly-anne-signed.zip)
I did the testpoint method to unlock my bootloader and was trying to follow the Lineage OS guide from here: https://wiki.lineageos.org/devices/anne/install using latest TWRP (3.7.0).
There are issue with the guide, such as mentioning that Volume Down + Power is used to enter fastboot but it's actually Volume Up + Power (as mentioned everywhere in this forum lol) and also to use fastboot flash recovery <recovery_filename>.img but actually one must use fastboot flash recovery_ramdisk <recovery_filename>.img. Also, when I tried to follow the Format Data step, it would always hang after displaying 'done.'. Despite that issue I carried on and it successfully sideloaded the LineageOS zip as per the guide but after rebooting it would not boot into it, it would just hang on the black and orange text screen with 'Your device is booting now...'.
I started deleting more things to try to make it work and I think I deleted too much, because after doing a Advanced Wipe on everything, I started having the TWRP bootloop.
{
"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"
}
Holding Power button to try to turn the unit off only cycles it and boots into TWRP logo screen.
Holding Volumn Up + Power no longer goes into eRecovery, instead it leads to the TWRP logo screen.
TWRP logo screen remains frozen, it does not show the slider nor does any tap or buttons work.
At the TWRP logo, I can see my device with adb as in recovery mode.
Fastboot has no apparent issues, so I tried rewriting TWRP to recovery_ramdisk a bunch of times, which succeeds, but it keeps freezing at the TWRP logo.
Did some searching and found this post which sounded like a similar situation https://forum.xda-developers.com/t/from-locked-bootloader-to-lineage-os-19-0-on-ane-lx3.4414089/ so I tried to follow this guide: https://www.getdroidtips.com/huawei-p20-lite-ane-lx3-firmware/ downloading the android 8 images from there, placing the DLOAD contents (tried both zipped and unzipped) onto an SD card (for example /dload/UPDATE.APP, etc.), however holding Volume Up + Volume Down + Power doesn't appear to do anything, let alone load anything from DLOAD folder.
Have not tried disconnecting the battery yet, more comfortable with a software solution but if that's what it comes down to I can try that.
Any help would be appreciated!
Thank you
Ironsmith9 said:
TWRP (3.7.0).
Click to expand...
Click to collapse
Ironsmith9 said:
Format Data
Click to expand...
Click to collapse
this is a deadly combination on stock EMUI 9 .
It's impossible to install Oreo dload ROM running EMUI 9. The problem is that dload method reguire stock Recovery on EMUI9.
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Btw, what is you region? (Cxxx).
-Alf- said:
this is a deadly combination on stock EMUI 9 .
Click to expand...
Click to collapse
oh man what have i done
-Alf- said:
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Click to expand...
Click to collapse
this worked!!! thank you!
-Alf- said:
Btw, what is you region? (Cxxx).
Click to expand...
Click to collapse
i'm not sure actually, how do i check this?
Ironsmith9 said:
how do i check this
Click to expand...
Click to collapse
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Ironsmith9 said:
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Click to expand...
Click to collapse
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
-Alf- said:
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
Click to expand...
Click to collapse
Woohoo! LineageOS is installed and booting now!
I wasn't really interested in the dload method. I was just trying to use that to reset everything to some good old state so I can go back into TWRP and try to get LineageOS installed.
What I ended up doing was switching my data partition from f2fs to exFAT which seemed to do the trick for some reason?! It was just a wild guess on my part and I wonder if it'll cause issues in the future (I'll create a new thread if it does). But so far so good!
O.K., midnight here
Ironsmith9 said:
exFAT
Click to expand...
Click to collapse
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
-Alf- said:
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
Click to expand...
Click to collapse
Understood, ok I'll try that out! Thanks Alf!