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
Related
[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?
in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
{
"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"
}
Please help.
Thanks
+1, same thing happening to me, halp
shraga1 said:
in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
Please help.
Thanks
Click to expand...
Click to collapse
So we could not be able to root this tablet?
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
simone81 said:
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
Click to expand...
Click to collapse
which drivers have you installed?
pabloluih said:
which drivers have you installed?
Click to expand...
Click to collapse
I did connect the tablet to the pc, the problem was in the cable, now i can enter in fastboot but i dont know wich command to use to unlock the bootloader, i tried fastboot oem unlock and it give me as a result failed because unknown command. I hope there will be a way to root it because its very good device. The drivers i used are available online here https://www.getdroidtips.com/root-teclast-p80x-4g/
Go on youtube and find "Teclast Root Process for Android Tablet"
I haven't found a solution but thought this might help.
I thought this might be of some use - however on their website putting in the P80X ID doesn't yield any firmware.
Perhaps you guys can make heads and tails of it.
How do you even get in the developer menu? The usual build number clicking doesn't seem to work on the P80X
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
few__ said:
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
Click to expand...
Click to collapse
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
delete
null
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
Click to expand...
Click to collapse
how did you unlock the bootloader?
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message.
Click to expand...
Click to collapse
That's great and all, but HOW?
Remember, forums are not only for you, but for others too. Share your knowledge!
Hello all together,
i´ve got an Xiaomi Redmi 4 Prime (3G/32GB) FullHD Smartphone which i was very happy the last 3 years. It worked smooth and i had a great experience. Every evening when i go to bed, i shut down the phone and reboot it in the morning. So i did one week before. But on next morning phone does not boot any more. It was stuck on MI Logo.
{
"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 could not do ANYTHING.
Could not even remove battery because it is not removable. All i could do is to wait until fully charged battery did go down to 0%.
So i tried rebooting many time without success. Looking at the internet i found some users reporting same problem, but most did have problems after an update or flashing or something. My Phone is Stock, i ordered it from china and never flashed anything. I did have Google Play Store and good working OS (Android 6.0 and MIUI 8). In the phone itself i often tried to look for updates but all time it told me i am up to date. i didn´t care about having an old OS. It was working and ok for me.
Ok so i did do alot of searches in google and found some instructions like how to boot into recovery mode or how to boot into fastboot mode.
As a software developer, i already had Android Studio on my machine and i did try to use the platform-tools from the SDK (adb.exe and fastboot.exe)
After some drivers update i can tell if iam in recovery mode, adb is listing my device
so when i type "adb devices" i get
List of devices attached
e0991c307d03 sideload
Click to expand...
Click to collapse
i did try a "adb pull /sdcard" but i get error: connection failed: closed
so i tried with fastboot
i found some information like booting twrp like a live cd with fastboot boot twrp.img (i did download a twrp version from the internet)
but i had no success and got that message
downloading boot.img OKAY [0.119s]
booting FAILED (Status read failed(Too many links))
Finished. Total time:
Click to expand...
Click to collapse
i tried fastboot erase cache, this seem to be worked, but my phone does not boot
fastboot oem device-info is giving me this info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY...
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) battery-soc-ok:yes
(bootloader) variant: QRD eMMC
(bootloader) secure: yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
Click to expand...
Click to collapse
So now WHAT I WANT!!!
I want to boot my phone to like it was WITHOUT loosing ANY DATA.
or at LEAST, recover the FILES from the internal 32GB storage.
I have WhatsApp Conversation and Media Files from near 4 years which i don´t want to miss.
I´ll be thankfully for every help i get from you. Please, before that trouble i have now, i never used adb, fastboot, twrp or anything like that before.
But why does it not boot any more, i just powered it off
Maybe the internal storage is near full, that is the only reason i could think. so erasing some files might help
For this guy who can help me to reboot my phone without loosing any data in it i will even donate some bucks via paypal to you.:fingers-crossed:
did you try to just press the Power down for 10-15 seconds to force the Redmi 4 to reboot back into Android manually?
Hi, pressing and holding the power button for more than 10 seconds simply does reboot the phone, but it is still locked on the boot screen (MI Logo)
I did now try and read many things.
I am successfully able to enter fastboot mode, but i see no fastboot command to access (and recover) any files from the internal storage.
i WAS able that the devices was listed unter adb devices in sideload mode?? but unfortunatelly in sideload mode, the adb pull command seems not to work?
there seems to be other adb modes besides adb sideload mode??
3. Mode i can enter is in download mode, i had to install some qualcomm drivers and the QPST. It contains a lot of tools and it seems to offer also a backup software, but i does not seem to work. also i found a EFS Explorer which also does not seem to work.
IT MUST be possible to at LEAST READ and BACKUP any files from the internal storage. I don´t care if the phone will remain dead, but at least i want to access and read the internal files. It can not be possible that so many members do not have any solution, even if i offer some money on a successful solution
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!!
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!