Good day, Devs. So, I have been trying to unlock my Vivo Y22s' bootloader recently and tried every which method; from fastboot to modified binaries. However, after looking into some threads, some Vivo phones have what's called an lk.img. My phone's firmware doesn't have that but after looking into one in particular, I found one interesting command: "fastboot oem reboot-edl". Maybe this was my ticket. But, after inputting that into fastboot mode on my phone, the bootloader returns "emmcid=xxxxxxxxxxxxxxxxxxxxxxxxx&extra=UNKOWN&key=chocolate&op=edl0&ver=Alpha0.lk1" (note: I censored the emmcid). Basically, I don't know what that string means and if it even leads anywhere near entering EDL mode on my phone.
Phone: Vivo Y22s
Chipset: SD680
Model: V2206
OS: Funtouch 13 (Android 13)
Related
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Not really sure what it is, but have you tried to launch SDK Manager and update platform-tools and google driver?
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Its likely cause your tablet is booting into the OS and not fastboot...
Use this AIO_scripts_R.A.H._TWRPv2.6.3.zip - 12.00 MB
Ive created that for installing twrp recovery but also included tools to unlock your boot loader.
under the windows folder and click the runme.bat and simply folliw the prompts for what you want to do...cant get any easier.
Sent from my SCH-I605 using Tapatalk 2
Thanks guys for the reply.
@mikecore - SDK manager, platform-tools and drivers were up to date. @runandhide05 - I made sure I was in the fastboot mode. And thank you so much for the link but it wasn't that I was doing wrong, the problem was the bootloaders were very old from the very first built or probably even before the xoom was released to public (when it was in manufacture trial or something). So whenever I tried to check the software update it said it was uptodate but it was running froyo (2.5 or something). What I did was I got the imgs of the latest built available from motorola and pushed that in fastboot mode. After that I got like 5 software updates OTA and it updated the bootloader to the latest version and now I am running android 4.1. Also I was able to unlock the bootloader now.
Can someone with a global phone please reboot into bootloader and dump the output of the following command here?
Please remove your token value and your serial number lines.
fastboot getvar all
What I am interested in here is what the model number, hardware revision, etc are. I am hoping to find something we can use (even if it's only for BL unlocked phones) to use the global software, still have root, and not have broken/missing features.
BLU has released these identical phones for various vendors. They are all rebadged G6.
A7 is for Best Buy, Vivo X5 is for Amazon.
X5 is a new release which was recently on sale for $80.
3GB ram, 64GB rom.
OEM unlocking, bootloader is available.
Would it be difficult to root this phone?
https://bluproducts.com/devices/vivo-xl5-x5/
https://bluproducts.com/devices/g6/
Need help with BLU VIVO X5 to install lineage os / custom rom
Hi,
I just bought a Blu Vivo X5 and would like to install a custom rom, namely lineage os, but I am not sure how to do it. This is my first foray into the Android world and I bought this inexpensive phone from Amazon as a second line/phone just so I could mess around with the software and root it or whatnot. I guess it is kind of new because I can't find any tutorials specifically on this particular Blu phone.
Could anyone please point me in the right direction to load a custom rom on this BLU Vivo X5 phone??
Thanks!!
There is no TWRP for the phone so the best way is to install custom roms are through fastboot. Try flashing Evolution X or Pixel Experience which already include gapps (search XDA for treble roms, make sure you have a back up firmware if the roms don't boot so you can always go back to stock). Download the correct architecture for your phone. Hope this helps
.
Rob4226 said:
Hi,
I just bought a Blu Vivo X5 and would like to install a custom rom, namely lineage os, but I am not sure how to do it. This is my first foray into the Android world and I bought this inexpensive phone from Amazon as a second line/phone just so I could mess around with the software and root it or whatnot. I guess it is kind of new because I can't find any tutorials specifically on this particular Blu phone.
Could anyone please point me in the right direction to load a custom rom on this BLU Vivo X5 phone??
Thanks!!
Click to expand...
Click to collapse
This phone seems pretty locked down.
When running the command "fastboot oem unlock" you get an unknown command error, and the command "fastboot flashing unlock" you get a "remote: Not implement" error. in fact it seems that just about every fastboot command results in an error, besides the reboot commands of course.
running the command "fastboot erase system" results in "FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)" so it certainly comes locked...
I think we're out of luck here, unless you figured something out, but my research indicates that the phone probably needs some sort of unlock code from the OEM, and that'll probably never happen.
EvergreenMetal said:
This phone seems pretty locked down.
When running the command "fastboot oem unlock" you get an unknown command error, and the command "fastboot flashing unlock" you get a "remote: Not implement" error. in fact it seems that just about every fastboot command results in an error, besides the reboot commands of course.
running the command "fastboot erase system" results in "FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)" so it certainly comes locked...
I think we're out of luck here, unless you figured something out, but my research indicates that the phone probably needs some sort of unlock code from the OEM, and that'll probably never happen.
Click to expand...
Click to collapse
I am running into this exact issue today. I tried so many things but this is the ultimate stopping point for me. It is not drivers, fastboot detects it, but I cannot run this command to unlock it. I contacted Blu over Facebook and they told me I needed to unlock the bootloader. Lol. I sent them your post and told them this is the issue.
I have a Blu G6 and need the stock recovery image. Does anyone know where I can find that?
So I've been trying for about a week trying to get the Blu Vivo x5 bootloader to unlock. I've even found specific unlock commands to the blu phones, but none worked. So I emailed BLU about the Vivo x5 and this is the response:
JackTraits said:
So I've been trying for about a week trying to get the Blu Vivo x5 bootloader to unlock. I've even found specific unlock commands to the blu phones, but none worked. So I emailed BLU about the Vivo x5 and this is the response:
Click to expand...
Click to collapse
You can get the phone's bootloader unlocked using this method, probably. I'm on a BLU G5 which has the same SOC & the guy on Reddit was using a BLU Vivo X5. So far though I haven't been able to actually flash anything, but my bootloader is definitely unlocked at least. Apparently he got AOSP 10 running on his though.
One And Done said:
I have a Blu G6 and need the stock recovery image. Does anyone know where I can find that?
Click to expand...
Click to collapse
This (admittedly very sketchy looking) website has the stock firmware which you can extract the recovery.img from using this tool.
I just recieved my phone and before I installed anything, I was going thru it and saw that it has the option to enable oem unlock? Anyone else get this or able to further a rooting process since it has it enabled?
OEM unlock in the settings just sets a bit in frp partition.
This would allow you to unlock the bootloader IF you could
1) access the bootloader in the first place
2) it would have the necessary commands available
2a) fastboot oem unlock (android standard)
2b) fastboot flash unlock unlock.bin (or so, for LG) with the unlock.bin provided by lg, generated by device id and imei (aka needs to be whitelisted by them)
on the sd845 devices, those that flash an engineering bootloader from someone with an octoplus box, use 2a because thats available there (after they had to wipe laf to enter fastboot)
but for that to try you would need
1) someone with an octoplux box, capable of flashing to sd855 LG devices
2) some leaked engineering bootloader (or create your own via reverse engineering, but one wrong step here, and brick basically)
I appreciate the return and detailed response. I am moving from the samsung galaxy s8 active to this V50. So I got excited about seeing the enable oem switch in developers mode, being that the s8 doesnt even display it. I miss being able to tinker with a device since the nexus 5x. This one is a beaut tho. So we'll see if life can adjust to it. the S8 was good, overall, for what it was. But having a secure, or at least ipi68+mil std, is not for one who enjoys to tinker. You mentioned about LG whitlisting it. Is there such a way to have that requested, or is it a result of a form of consequence?
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
V0latyle said:
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
Click to expand...
Click to collapse
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
observingman said:
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
Click to expand...
Click to collapse
What soc in that device?
observingman said:
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
Click to expand...
Click to collapse
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
V0latyle said:
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
Thanks again... it didn't work:
C:\WINDOWS\system32>fastboot -i 0x1bbb oem unlock
fastboot: unknown option -- i
The model is the alcatel 3 2019 5053Y
PizzaG said:
What soc in that device?
Click to expand...
Click to collapse
For the device (alcatel 3 2019 5053Y), the soc is the Qualcomm SDM439 Snapdragon 439 (12 nm):
alcatel 3 (2019) - Full phone specifications
www.gsmarena.com
Google didn't help much, so you might be SOL with this device.
V0latyle said:
Google didn't help much, so you might be SOL with this device.
Click to expand...
Click to collapse
Ouch ! Yep, it's sad... Anyway, thanks
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
observingman said:
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
Click to expand...
Click to collapse
Unfortunately no, without root access it is not possible to dump partition contents, with the exception of /data.