How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it.
Currently with many trial and error I got LiR-ROM to boot.
The first step is to unlock the Bootloader so I thought I will share the process here.
Your data will be deleted while unlocking, try it at your own risk.
Unlock Bootloader manually
Requirement: PC with ADB Fastboot
1. Go to Settings -> System -> About Phone, tab on it until developer settings are enabled.
2. Go to Developer Settings and enable "USB Debugging" and "OEM Unlocking".
3. Open Console and enter "adb devices". Allow USB-Debugging if tablets asks.
4. Enter command "adb reboot bootloader".
5. Write down the serial number shown on the bootloader screen
You can either get the unlock image via this link "http://cdn.zui.lenovomm.com/developer/tabletboot/[your sn number]/sn.img" or via the webseite
5. Go to the ZUI Unlock Website and request the unlock image
{
"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"
}
6. You should get a mail where you can download a file called "sn.img".
7. Flash the image with fastboot "fastboot flash unlock sn.img"
8. Enter command "fastboot oem unlock-go", bootloader will unlock now.
9. Restart with "fastboot reboot".
Done, your bootloader should be unlocked now.
Lock and Unlock Bootloader with Batchscript
I recently found a batch script for lenovo devices in an chinese forum and translated it.
It's easy and convenient to use. For unlocking you still need the sn.img from the ZUI Unlock Website.
Download BatchScript
Thanks a lot for your contribution! Mine was unlocked when I received it but it's good to see some guides here.
What is the opposite process, to close the bootloader? Does Widevine L1 recover after closing the bootloader? In the case of doing so, can the bootloader be opened again?
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Tropaion said:
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Click to expand...
Click to collapse
Thank you very much, I hope you can install a custom rom and this tablet will not be forgotten, since it is one of the most powerful compact tablets.
@sakun-ice I got LineageOS to run on it today, but it still has 2-3 bugs.
Helloi received one unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper
I'm able to flash back to China stock rom but i can't lock the bootloader.
i have placed the sn.img in both the batchscript folder and platform tools
Tried the batch script :
"
Please select your device status:
1. Fully booted
2. Fastboot mode
Status: 2
Start locking bootloader, don't disconnect device from PC!
FAILED (remote: Command not supported in default implementation)
Finished. Total time: 0.016s
FAILED (remote: Unrecognized command flashing lock)
Finished. Total time: -0.000s
If prompt says "OKAY", locking was successfull.
Use the volume keys to select "LOCK BOOTLOADER", press power key to confirm.
Done!
Press any key to continue . . .
"
Powershell :
"
PS C:\Users\weeteck\Downloads\platform-tools_r31.0.3-windows\platform-tools> ./fastboot flash lock sn.img
Sending 'lock' (5 KB) OKAY [ 0.000s]
Writing 'lock' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
"
@zeroflame15 Did install the driver correctly? For locking you don't need the sn.img, only for unlocking. And did you use the LockBootloader Script?
hmm..i'm not sure if i install the driver correctly. what should be shown in device manager? i did follow PHRS guide and installed the ADB driver but there is this !Android under Other Devices.
Any other driver that i need to install?
And should i be in bootloader mode or fastboot mode to run the command? I run the command at fastboot moder i will get the error above. If i run at bootloader mode will stuckedd at <waiting for device>
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Tropaion said:
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Click to expand...
Click to collapse
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Try to connecting in another usb port with other usb cable.
zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Check out this post:
Post in thread '[Solved] Re-locking bootloader - no fastboot commands working' https://forum.xda-developers.com/t/...stboot-commands-working.4330019/post-85755663
It can be a bit tricky to get the commands working because it's not always clear if you need to be in fastboot or bootloader.
This worked for me:
Reboot to bootloader by entering "adb reboot bootloader"
After that try "fastboot flashing lock"
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
zeroflame15 said:
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
Click to expand...
Click to collapse
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
fazioso said:
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
Click to expand...
Click to collapse
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Saw some chinese video for those who wanted the rooted status and also to perform OTA updates, they are using magdisk to hide the root.
zeroflame15 said:
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Click to expand...
Click to collapse
thanks!
its seems most difficult to lock/unlock bootloader that flash rom.....
but you need ZUI Unlock Website also for lock? cause seems need only for unlock...right?
No need for lock. Like what others have mentioned. Just a single line command and it works as long you got the right drivers installed.
Tropaion said:
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
5. Go to the ZUI Unlock Website and request the unlock image
View attachment 5432885
6. You should get a mail where you can download a file called "sn.img".
Click to expand...
Click to collapse
my friend ....i have a unlocked bootloader ,cause for now i have the fake global....want to change in china stock....
but i ask anyway to the zui unlock website the sn.img in case i need in future.....
just a question.... after many hours or days i will receive the sn.img file? pass 10 minutes and nothing yet
Related
{
"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"
}
The European H850 can now be officially unlocked through LG's developer unlock program page.
Yes, only the European version. Your H850 is from the Middle East? Won't work. You have an AT&T G5? That's not an H850, move along.
LG Developer Unlock Site Here
Prerequisites:
1. European LG G5 H850
2. Computer w/ADB & Fastboot. ADB/Fastboot for Windows here. ADB/Fastboot for Linux/OS X here.
3. Basic knowledge of ADB, Fastboot and Windows command prompt or Linux/OS X terminal.
4. Device IMEI. This 15-digit code can be found on your box, the back of the phone or by dialing *#06#
5. LG developer account (free, click here then click sign in at the top of the page to make an account.)
Directions:
LG's official bootloader unlock directions can be found in the big link at the top of the page..
but I've still rewritten the steps out below while adding some for root and TWRP.
1. Enable USB-Debugging on your phone. USB-Debugging is required for the commands “adb” and “fastboot” to work. To enable USB-Debugging, go to Settings >> About phone >> Software info and tap Build number 7 times. Return to the previous screen, select Developer options and enable USB-Debugging.
2. Enable OEM unlock on your phone. Activating the "Enable OEM unlock" is necessary for the bootloader unlock. To enable OEM unlock, go to Settings >> Developer options and check Enable OEM unlock.
3. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP.
4. Once in the bootloader, use the following fastboot command to obtain Device ID:
Code:
fastboot oem device-id
Fastboot command will return a string. This is the Device ID which is needed to generate your unique unlock key.
Example :
Code:
$ fastboot oem device-id
(bootloader)-----------------------------------------------------------------
(bootloader) Device-ID
(bootloader) CD58B679A38D6B613ED518F37A05E013
(bootloader) F93190BD558261DBBC5584E8EF8789B1
(bootloader)-----------------------------------------------------------------
To generate your unlock key, you will need to paste together the 2 lines of output into one continuous string without "(bootloader)" or white spaces. In the example above, the Device ID would be:
CD58B679A38D6B613ED518F37A05E013F93190BD558261DBBC5584E8EF8789B1
5. Copy Device ID and IMEI into the LG developers unlock site and hit the confirm button. In a few moments the unlock.bin will be emailed to you. Download unlock.bin to computer.
6. While the phone is still in fastboot enter the following command to unlock the bootloader:
This will unlock your phone AND factory reset your device wiping all data!
Code:
fastboot flash unlock unlock.bin
7. You can now reboot the phone and boot into your unlocked device! Enter:
Code:
fastboot reboot
8. Want root or TWRP? Before moving forward I suggest getting a microSD card and putting the SuperSu 2.65 zip on there. Do not set the external SD up as adoptive storage. Download this TWRP image too.
Reboot back into the bootloader (you'll have to first re-enable USB debugging):
Code:
adb reboot bootloader
9. Flash TWRP:
Code:
fastboot flash recovery twrp-3.0.2-0-h850.img
For TWRP to "stick" you must first boot directly into TWRP and not back into Android, until after flashing the SuperSU zip.
After flashing TWRP unplug the USB cable and pull the battery. Plug battery back in then boot into recovery which should hopefully load TWRP.
To boot into recovery:
a. Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.
b. As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
c. Keep holding until you see the Factory Reset screen. Click thru the factory reset screens.. Yes.. Yes...
10. You will not be able to decrypt your internal data while in TWRP (unless performing a full /data wipe in TWRP and you will lose encryption!) but you can manually mount your external SD card to view the SuperSu zip. Feel free to back up first.. but otherwise.. time to install SuperSu. Click the Install button and navigate to the external_sd, select the SuperSu zip then swipe to install. Now you're rooted and TWRP'd! Reboot into system...
Have fun and be careful.
FAQ:
Q: I have an H850Q from Israel.. can I unlock the bootloader?
A: No, this official unlock program is ONLY for the H850 model for countries in Europe just like LG did for the LG G4.
But... for about a 10 day span last year G4 devices from SE Asia worked with the official site and users received unlock.bin files. :good:
Q: Will more devices be added?
A: While there is no "official" word.. most likely no. Unless another mistake happens where another region's H850's are allowed for a week.
Other than then EU H850 and possibly the T-Mobile H830... no other variants have a shot at being bootloader unlocked officially.
Q: I can't get my phone to show up with ADB or Fastboot, watdo?
A: Make sure USB debugging is enabled and try changing the phones USB modes.. from maybe charging to MTP.. or MTP to PTP.
Make sure drivers are installed if using Windows. Learn2Computer.
Q: Where can I get drivers and things?
A: A good start is my G5 Info thread found here. Google and this very website are good places to search as well.
Q: What happens to warranty if I unlock or root?
A: YMMV I suppose. The official LG site claims that warranty is void if damage is caused by the unlock. Not sure how they could prove such things. I thought there was some EU law that gave everyone warranty coverage even if unlocking the phone. Not sure if that is enforced or even still valid at this time... maybe someone knows for sure?
Q: Can I re-lock the bootloader?
LG does not support re-locking the bootloader... so once unlocked you remain unlocked.
Thanks to @Loggsie for the heads up... the previous statement above is confirmed not true.
It IS possible to re-lock the bootloader with the the command: fastboot oem lock
I wrote a bit more about it in this post HERE... and in the post under that.. @wolfgart shows off some examples.
DO NOT re-lock the bootloader if you have a modified boot/system img... restore them to stock first or you will not be able to boot into android after the lock and need to flash a KDZ in download mode.
Q: So many words... yudodat?
A: Here is a video on how to unlock the G4... up until the 6minute mark it is step-by-step 100% the same as G5. Only slight difference is when you get to the TWRP/root steps. https://www.youtube.com/watch?v=O64GfQORCaE
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Feel free to contribute to my LG G5 fund...
click my name at the top of any post and hit donate or click here.
Awesome!
This is Fire Baby ! ??
Can't wait to get my Hands on my H850... My first LG Device ?
Thanks for sharing Prime!
As for G4, will this void the warranty?
Envoyé de mon SM-G925F en utilisant Tapatalk
@misteurz
Once your phone is unlocked, it will no longer be covered by LG warranty.
Thanks for your tutorial!
I'm having a problem with the last step "fastboot boot twrp-3.0.2-0-h850.img"
downloading 'boot.img'...
OKAY [ 0.412s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.454s
Click to expand...
Click to collapse
Any ideas?
kerniger said:
Thanks for your tutorial!
I'm having a problem with the last step "fastboot boot twrp-3.0.2-0-h850.img"
Any ideas?
Click to expand...
Click to collapse
odd.. not sure where it's getting "boot.img" from.
try: fastboot flash recovery twrp-3.0.2-0-h850.img
if flash and boot dont work then sounds like fastboot is broken and LG is really screwing with all of us. :laugh:
Tried that, but entering Recovery shows red triange error...
Sent from my LG-H850 using XDA-Developers mobile app
kerniger said:
Tried that, but entering Recovery shows red triange error...
Sent from my LG-H850 using XDA-Developers mobile app
Click to expand...
Click to collapse
are you booting back into system first after flashing it by any chance? because if so, booting into system runs a patch to restore stock recovery. so after flashing twrp while in the bootloader/fastboot it'd be easiest to unplug the usb cable... pull the battery then put it back in... then boot into recovery. hopefully TWRP works like that. if so, then you'd just need to flash the supersu zip for root.
autoprime said:
are you booting back into system first after flashing it by any chance? because if so, booting into system runs a patch to restore stock recovery. so after flashing twrp while in the bootloader/fastboot it'd be easiest to unplug the usb cable... pull the battery then put it back in... then boot into recovery. hopefully TWRP works like that. if so, then you'd just need to flash the supersu zip for root.
Click to expand...
Click to collapse
did work like a charm! Thanks!
kerniger said:
it doesn't boot into recovery with power+vol down, any other suggestion?
Thanks again for your help
Click to expand...
Click to collapse
check step #9 in the OP.. I have edited the TWRP/root steps to now use fastboot flash instead of fastboot boot.
After flashing and booting its stuck at loading as u can see at the picture
D:\android\sdk\platform-tools>fastboot flash revovery twrp-3.0.2-0-h850.zip
target reported max download size of 536870912 bytes
sending 'revovery' (16377 KB)...
OKAY [ 0.530s]
writing 'revovery'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.569s
What did i wrong?
STUPID me. i should use img not zip.....
ok still same error....
doncompadre said:
D:\android\sdk\platform-tools>fastboot flash revovery twrp-3.0.2-0-h850.zip
target reported max download size of 536870912 bytes
sending 'revovery' (16377 KB)...
OKAY [ 0.530s]
writing 'revovery'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.569s
What did i wrong?
STUPID me. i should use img not zip.....
ok still same error....
Click to expand...
Click to collapse
Check the command, maybe is because you wrote "revovery" again instead of "recovery"
What is the easiest way to backup and restore the apps&data before rooting?
Never had the situation that I used a phone before root was available
Helium backup is not working
Killua96 said:
Check the command, maybe is because you wrote "revovery" again instead of "recovery"
Click to expand...
Click to collapse
thanks man thats it... to blind to see
but now after flash twrp i cant come into it. after the step with 2 yes it reboots normal...
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
i got the same now... how easy things goes on my old HTCs
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
I have the same problem - recovery hangs on its splash screen
Horgul123 said:
What is the easiest way to backup and restore the apps&data before rooting?
Never had the situation that I used a phone before root was available
Helium backup is not working
Click to expand...
Click to collapse
Helium backup seemed to work fine for me. You could try LG Backup but i'm unsure if it backs up app data.
duckysempai said:
Helium backup seemed to work fine for me. You could try LG Backup but i'm unsure if it backs up app data.
Click to expand...
Click to collapse
Thanks for the hint. Will check it
okgnew said:
I have the same problem - recovery hangs on its splash screen
Click to expand...
Click to collapse
Same, knew it go smoothly :laugh:
aehm2k5 said:
After flashing and booting its stuck at loading as u can see at the picture
Click to expand...
Click to collapse
LBensley said:
Same, knew it go smoothly :laugh:
Click to expand...
Click to collapse
u mean now it goes ??? tell us what u did please
I just got my razer phone today and set off on trying to unlock the bootloader. There's no documentation on the process but it wasn't too hard to figure out.
1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked.
zipxavier said:
I just got my razer phone today and set off on trying to unlock the bootloader. There's no documentation on the process but it wasn't too hard to figure out.
1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked.
Click to expand...
Click to collapse
Any idea if the latest TWRP and Magisk work with the phone?
@zipxavier How did you get fastboot to work? ADB Drivers work, but I do not have a driver for fastboot. I've downloaded the latest Google USB Drivers and it still will not detect it or take the new drivers even when pointed to them while the phone is in Download Mode.
nikitis said:
@zipxavier How did you get fastboot to work? ADB Drivers work, but I do not have a driver for fastboot. I've downloaded the latest Google USB Drivers and it still will not detect it or take the new drivers even when pointed to them while the phone is in Download Mode.
Click to expand...
Click to collapse
I had to manually browse the to the ADB drivers inf and use the "have disk" device manager driver install method to point it to the ADB Bootloader Interface driver.
Quashhh said:
Any idea if the latest TWRP and Magisk work with the phone?
Click to expand...
Click to collapse
Doesn't look like it.
Glad to see bootloader unlock is easy. Anyone get root yet?
The instructions above are a little more complicated than they need to be.
I was able to unlock my bootloader with just "fastboot flashing unlock"
{
"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"
}
Unfortunately, it seems the 'fastboot boot image.img' command was disabled. So until I get actual system images for the device, I have no way to return the device to stock in the event of a bad TWRP flash as I can't use the boot command to test images.
twelfth said:
The instructions above are a little more complicated than they need to be.
Click to expand...
Click to collapse
For me, fastboot would not work without -i 0x1532 and really it doesn't complicate anything.
twelfth said:
The instructions above are a little more complicated than they need to be.
I was able to unlock my bootloader with just "fastboot flashing unlock"
Unfortunately, it seems the 'fastboot boot image.img' command was disabled. So until I get actual system images for the device, I have no way to return the device to stock in the event of a bad TWRP flash as I can't use the boot command to test images.
Click to expand...
Click to collapse
did you ,make sure you followed step 3?
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
Click to expand...
Click to collapse
Buddyjohn said:
did you ,make sure you followed step 3?
Click to expand...
Click to collapse
I wouldn't have been able to unlock the bootloader AND take a picture of the yes/no screen if I didn't go into developer options and enable OEM Unlock.
I assume to lock the bootloader you just flip the setting in developer options?
kungpaoshizi said:
I assume to lock the bootloader you just flip the setting in developer options?
Click to expand...
Click to collapse
Typically, the fastboot command "fastboot oem lock" is required.
Perhaps someone who has unlocked their bootloader can verify this....
Sent from my Samsung SM-N935F using XDA Labs
KOLIOSIS said:
Typically, the fastboot command "fastboot oem lock" is required.
Perhaps someone who has unlocked their bootloader can verify this....
Sent from my Samsung SM-N935F using XDA Labs
Click to expand...
Click to collapse
to relock do fastboot oem lock
to unlock do fastboot oem unlock
the_rooter said:
to relock do fastboot oem lock
to unlock do fastboot oem unlock
Click to expand...
Click to collapse
Not for this phone.
"fastboot flashing unlock" is the command.
twelfth said:
Not for this phone.
"fastboot flashing unlock" is the command.
Click to expand...
Click to collapse
Have you attempted to relock using the same command (fastboot flashing lock) ?
I cant find the google usb drive please help
Hello Razer family
Having come from Sony for many years now, unlocking BL on Sony was always a ball ache with the DRM malarky.
Can I ask is there any such requirement on the Razer as such to protect any DRM keys or TA Partitions as such before unlocking the BL (like that of the Sony)?
I suspect not, however I would like to become accustomed to the ecosystem of the Razer before the day I do eventually unlock BL/Root etc.
(Where on Sony if you hadn't backed up the DRM/TA partition, certain functionalities of the phone would be forever lost.)
dillalade said:
Hello Razer family
Having come from Sony for many years now, unlocking BL on Sony was always a ball ache with the DRM malarky.
Can I ask is there any such requirement on the Razer as such to protect any DRM keys or TA Partitions as such before unlocking the BL (like that of the Sony)?
I suspect not, however I would like to become accustomed to the ecosystem of the Razer before the day I do eventually unlock BL/Root etc.
(Where on Sony if you hadn't backed up the DRM/TA partition, certain functionalities of the phone would be forever lost.)
Click to expand...
Click to collapse
Sony is probably the only major name I have never owned a phone from, and I never had to do anything like that before.
ADB doesn't recognize the phone
Hi! I need help with ADB, I think. It doesn't recognize Razer phone, but it recognize OnePlus, without any problem at all. And I don't get a prompt on my Razer, when I connect it to PC. I've tried the most I think, but nothing helped. I'm on w10. Thankful for all help.
zam666 said:
Hi! I need help with ADB, I think. It doesn't recognize Razer phone, but it recognize OnePlus, without any problem at all. And I don't get a prompt on my Razer, when I connect it to PC. I've tried the most I think, but nothing helped. I'm on w10. Thankful for all help.
Click to expand...
Click to collapse
Google xda adb drivers.. There is an all in one package that installs adb and Fastboot system wide..
Once you install that, plug in your phone, it should be detected then the adb commands should work. Unfortunately it didn't install the Fastboot drivers automatically and once my phone rebooted to bootloader it wasn't detected. To fix that I had to go into Device manager on w10 and select android device, properties, update driver, and manually find the driver from the list for bootloader driver. After that was installed it ran fine after I unplugged and re plugged it in and I was able to continue
This May Work With Other Devices As Well.
Prerequisites:
Starting from Bootloader Locked Stock Verizon.
CrossFlash to G710ULM11g.kdz: LG G710U | LG G7 ThinQ | Version: G710ULM11g_01_NAO_US_OP_1112 | Firmware for Region: BPT from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
Fastboot works on the G710ULM11g.kdz no need to erase laf.imgs.
See the 2 links below for crossflashing threads.
(There are 2 ways to crossflash).
1. Use LGUP, Partition DL and Refurbish is you want the kdz on both a and b slots: https://mega.nz/#!kCpHBaia!xZmico6MYL1T07ffuc8z6cCbs5oU4pKEz5VG-AwfvV0
2. Power Shell Command line Crossflashing thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Files required to unlock bootloader while crossflashed to the ULM11g.kdz V35eng file and firehose file for Qfil. https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Zip contains Stock G710VM21b stock boot_a and boot_b img and Magisk patched boot_a and boot_b imgs. https://www.androidfilehost.com/?w=files&flid=322268
Latest Verizon kdz LG G710VM | LG G7 ThinQ | Version: G710VM21b_04_0812 | Firmware for Region: VRZ from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
NOTE: Some links are from other helpful threads so thank whoever wrote them.
To successfully unlock the bootloader while on the crossflashed 11g,
Setup Device then go into Developer options and Enable the OEM Unlock toggle and enable usb debugging in the phone.
Now Let's Begin:
1. Switching the phone to EDL modeopen device manager):
Turn off the phone, then hold the vol- and power buttons together and repeatedly press the vol+ button until you see device in device manager as "Qualcomm HS-USB QDLoader 9008". then release buttons. If you don't succeed at first keep trying.
2. Using QFIL:
Install the QPST package, launch Qfil, in the program window select:
(1) Select port to which the device is connected
(2) Storage type UFS
(3) select build type: Flat
(4) Select programmer: prog_ufs_firehose_Sdm845_lge.elf
Click to expand...
Click to collapse
{
"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"
}
3. Load v35eng.img to abl_a partition:
in the upper left menu, select Tools, then partition manager , look for abl_a in the window that opens , Right click abl_a, select manage partition data, then use the V35eng.img overwrite the abl_a with load image.
4. Reboot into Fastboot to Unlock the bootloader:
Leave EDL mode by holding the volume down and power for about 10 seconds. Phone will restart. Turn off phone disconnect usb and hold vol- and plug in usb. (phone should boot into fastboot like the picture).
Now we need platform tools unpacked to any folder convenient for you, launch the shell by pressing the shift + right mouse button and choosing to open the power shell window here .
Use the command : "fastboot oem unlock" without quotes
Use the command: "fastboot reboot" without quotes
That's Everything the bootloader is unlocked.
Crossflash back to Stock G710VM21b.kdz and root or crossflash to android 10 kdz to install custom roms.
To Root stock 21b use EDL mode for Qfil to load the magisk patched 21b boot.imgs to boot_a and boot_b reboot and install magisk.apk then it should update to latest magisk zip.
***NOTE***
Only use this part of the guide if you are relocking bootloader. This locking bootloader procedure may work for other devices use at your own risk.
***Do not uninstall magisk with the magisk uninstall button. Just go into download mode and crossflash to ULM11g. If you use the uninstall button in magisk manager you will brick your device.**
To relock bootloader:
Cross Flash back to ULM11G, setup phone, enable Developer options, enable USB debugging. (Enable OEM unlock) should be greyed out don't worry).
Platform-tools and issue powershell commands:
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
To confirm locked bootloader:
Enable developer options again and you will see (Enable OEM Unlock) Unchecked.
***Profit Bootloader is locked***[/QUOTE]
I just cross flashed and rooted the G710ULM20d for my LG710VM Verizon. This method should work on any phone that is cross flashed. I only used Qfil no twrp.
Can someone write this up in a more noob friendly way?
Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Dishe said:
Can someone write this up in a more noob friendly way?
Click to expand...
Click to collapse
Yeah, totally lost me at
When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away (if it don't work just let the phone boot up and go into adb and command prompt and type fastboot reboot bootloader.
2. When you've entered fastboot, execute this command:
Click to expand...
Click to collapse
I guess we're supposed to have ADB cmd window open on the PC, similar to 3:30 of the following video:
/watch?v=wp4Rb0INxvU
OP then mentions the following
Once bootloader is unlocked you can cross flash back to Verizon Pie kdz. Make the backup for whatever slot your using a or b.
Click to expand...
Click to collapse
This doesn't make any sense, since he didn't revert to Oreo, to install the v35eng.img
Edit: It seems he's referring to the original abl_a/abl_b files, this post talks about distinguishing the 2
3. Installed magisk manager and patched boot_a.
Click to expand...
Click to collapse
It seems Magisk apk needs to be executed directly on the phone, then it'll do it's thing from there
/watch?v=m4f21ZCGJuk
Edit: here are my images of the steps to patch boot_a and boot_b
imgur.com/a/E4Abu4t
You must manually navigate to the directory with your LG, press and hold then select 'share' file, so it can appear in Windows explorer; filenames will be the same so you have to do this twice.
File size of each file went from 64 MB to 23.1 MB
After patching boot_a and boot_b with QFIL, the red question mark will change into a green check mark, when you boot up again.
But yeah, none of this makes any sense without some sort of image or video. Thank you for the guide though.
There are 5 main files that should be backed up 'just in case'
i.imgur.com/uqk2Cwb.png
Edit: consider backing up abl_b as well.
The phone's on a GSM network. I as able to uninstall facebook directly from the phone, and then use ADB shell to remove the app manager/system facebook files as well.
paxar331 said:
Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Click to expand...
Click to collapse
Yes you need it enabled to use adb.
Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.
paxar331 said:
Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.
Click to expand...
Click to collapse
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.
ik this phone is so cool
---------- Post added at 04:57 AM ---------- Previous post was at 04:52 AM ----------
netookska05 said:
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.
Click to expand...
Click to collapse
I am so lost on this....
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).
Unlocking the Verizon LG G710VM bootloader with QFIL may work with other devices
edit
nik322 said:
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).
Click to expand...
Click to collapse
What's going on?
It doesn't work to lock the bootloader, I get red case
HimikoMw said:
It doesn't work to lock the bootloader, I get red case
Click to expand...
Click to collapse
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?
netookska05 said:
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?
Click to expand...
Click to collapse
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case
HimikoMw said:
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case
Click to expand...
Click to collapse
How did you unlock bootloader?
Was it with the official way generating your unlock key?
netookska05 said:
How did you unlock bootloader?
Was it with the official way generating your unlock key?
Click to expand...
Click to collapse
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.
HimikoMw said:
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.
Click to expand...
Click to collapse
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.
netookska05 said:
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.
Click to expand...
Click to collapse
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.
HimikoMw said:
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.
Click to expand...
Click to collapse
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?
netookska05 said:
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?
Click to expand...
Click to collapse
Try this guide for your red case problem. https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
(EDIT) finish the timer for the unlock bootloader, and after that i just flash a stock rom, thanks for everyone who support me
Re-flash Stock ROM
Tell the problem clearly what issues you are facing??
aaashzz said:
Tell the problem clearly what issues you are facing??
Click to expand...
Click to collapse
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
{
"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"
}
Syxnetrax said:
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
View attachment 5198249
Click to expand...
Click to collapse
Yes tha'ts right you can not flash rom with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi. And the with miflash tool you cannot unlock your phone there is an entirely different tool for unlocking the bootloader "miunlock tool" they are entirely different tools the miflash is only for flash mi rom and for lock your phone. And the other side the miunlock tool is for unlocking the bootloader!
aaashzz said:
Yes tha'ts right you can not flash os with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi.
Click to expand...
Click to collapse
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
aaashzz said:
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
Click to expand...
Click to collapse
i can access the fastboot, and the unlock will finish in the time mencioned
Syxnetrax said:
i can access the fastboot, and the unlock will finish in the time mencioned
Click to expand...
Click to collapse
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
jwoegerbauer said:
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
Click to expand...
Click to collapse
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Syxnetrax said:
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Click to expand...
Click to collapse
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
flashing stock rom does not require bootloader to be unlocked.
just flash the rom using adb or fastboot
i will recommend using fastboot because it's reliable but some time it requires unlocked bootloader so just try fastboot after adb has failed.
jwoegerbauer said:
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
adb reboot sideload starts a bootloop of the same screen "ths system has been destroyed"
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Bhanu8082 said:
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Click to expand...
Click to collapse
this happend, idk if im doing something wrong
Syxnetrax said:
View attachment 5198725
this happend, idk if im doing something wrong
Click to expand...
Click to collapse
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
jwoegerbauer said:
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
Click to expand...
Click to collapse
after this the same error repeats and start to bootloop with the system has been destroyed screen
bro problem might be your version of adb just use latest version or try version
Android Debug Bridge version 1.0.32
version 1.0.32 is reliable for me as it works
Syxnetrax said:
after this the same error repeats and start to bootloop with the system has been destroyed screen
Click to expand...
Click to collapse
Fix for "The system has been destroyed" Redmi note 8/8T
Fix for "The system has been destroyed" Redmi note 8/8T This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions...
forum.xda-developers.com
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Hey did you fixed the phone ??
After 6 months from launch date, we finally got bootloader unlock permission on March 2nd 2020 for Realme C12 initially based on Realme UI 1.0. Later Realme gave permission for UI 2.0 too.
Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Unlocking bootloader will trip safetynet. If you want to use bank apps or some apps that use SafetyNet, then you have to pass SafetyNet. To pass it we have to use a Magisk module called 'Universal SafetyNet fix' Or use a custom rom or GSI that uses it if you dont want Magisk.
Also locking bootloader seems to lead 'Red State' in many devices. This can only be solved by going to Service Center. So be prepared for it. To get rid of it flash stock rom once even if you didn't done any modifications.
Prerequisites:-- A PC
- USB Cable(We can use charger cable)
- Platform-tools
- Patience
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool from below
For UI 1.0 https://download.c.realme.com/flash/Unlock_tool/DeepTest_realmeC12.apk
For UI 2.0 https://c.realme.com/in/post-details/1526491339024314368
{
"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"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - Go back. Remove app from Recent apps. Open the app and click on Query verification status which is at top right
Step 6 - You can now click “Start the in-depth test” and the device will reboot to fastboot mode automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and Connect the device to PC using USB cable and ready to unlock it.
Step 8 - Now you are in Fastboot Mode. Type this command
Code:
fastboot flashing unlock
in command prompt of PC and Press enter.
Step 9 - On your phone press the Volume Down key to select "UNLOCK THE BOOTLOADER” (or press the Volume Up key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”).
Step 10 - Now type
Code:
fastboot reboot
. Your phone will reboot and all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
And there you go! Your phone will reboot and you can set it all up again. with the ability to root and you can also install GSIs/custom ROMs/recovery!
After unlocking, flash stock rom once from stock recovery to fix some 'Red state' issue and fastboot errors that may lead to GSI booting issues. See this for flashing stock rom. With this you will also get a idea of flashing stock rom.
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.- Try another USB cable.- Download and install exe for 64-bit and 32-bit- Restart PC- Connect device to PC- Go to Device Manager- Double Click on Unidentified Realme C12(Device with exclamation mark)- Click on Update Driver- Select Browser my computer- Select Let me pick- Select Android Device- Click on NextEnjoy!
Q: I am getting carrier-customized phone?
A: See this
Relock your bootloader
Locking bootloader without flashing stock rom again may lead to 'Red State'(can only be fixed by flashing stock rom with PC). So before locking bootloader, flash stock rom in stock recovery and boot to stock rom once.
Tutorial:
Step 0 - Flash stock ROM in stock recovery.(Don't skip this step even if you haven't done any modification)
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume down button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: fastboot flashing lockStep 4 - Press the Volume Down button to select the “Lock bootloader” option (or press the Volume Up button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Thanks
To this
You are showing relame 6pro device
adityalonkar said:
You are showing relame 6pro device
Click to expand...
Click to collapse
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks
HemanthJabalpuri said:
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks
Click to expand...
Click to collapse
Ok Thanks
adityalonkar said:
Ok Thanks
Click to expand...
Click to collapse
Is there chances for getting twrp image for c12 ?
adityalonkar said:
Is there chances for getting twrp image for c12 ?
Click to expand...
Click to collapse
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks
HemanthJabalpuri said:
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks
Click to expand...
Click to collapse
Thanks a lot
Can you make a full tutorial on flashing twrp image on realme c12 device ?
adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Will try later.
Thanks
adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Just made a guide at https://forum.xda-developers.com/t/custom-roms-and-recovery-for-realme-c12.4250073/
I'm stuck in "fast_boot_unlock verify ok"
HemanthJabalpuri said:
fast_boot_unlock_verify ok
Click to expand...
Click to collapse
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.
ramcadag said:
I'm stuck in "fast_boot_unlock verify ok"
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.
Click to expand...
Click to collapse
See the drivers question in the guide. You need to install drivers for working.
Thanks
I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz
Raqeshpati said:
I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz
Click to expand...
Click to collapse
I guess, there is no support for UI2 yet.
So wait for it or downgrade
Thanks
I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)
Shawmik said:
I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)
Click to expand...
Click to collapse
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks
HemanthJabalpuri said:
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks
Click to expand...
Click to collapse
Thanks a lot. I am facing some problems while trying to unlock bootloader. (Forgive me, I am a noob )
I have successfully installed platform-tools, granted usb debugging permission and rebooted my phone to fastboot mode from depth tool. It's showing "fast boot_unlock_verify ok".
Now if I enter the command "fastboot flashing unlock" in command prompt window, it's showing this message: "waiting for device" and nothing is happening afterwards... Am I missing any drivers? (My cable is ok)
@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks
HemanthJabalpuri said:
@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks
Click to expand...
Click to collapse
I don't know why I am facing these weird issues, sorry for bothering you...
I have installed the driver you mentioned in the questions section, now if I connect my phone while in fastboot mode, my PC detects it but if I give the command "fastboot flashing unlock", the command prompt still shows "Waiting for device"...
And I tried going to device manager and manually update my device drivers (as you guided), still the same