Related
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...
gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.
since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin
THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM
First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)
There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img
I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S
use the galaxy nexus toolkit to unlock bootloader, root
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.
Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250
OP, OMAP flash?
Calling all the Huawei Experts to help me out on this!!
Short Summary of problem
On my Ascend Mate 7 MT7-TL10 (running Android 5.1.1 version B326) -The bootloader shows as unlocked but I still can't flash a custom recovery - It gives error 'FAILED (remote: image verification error)'. I am using the lastest version of ADB/Fastboot, I have USB drivers installed and I also have the Bootloader Unlock code from Huawei, which works and shows 'Done'
Please read the details below first and kindly see all attachments
Click to expand...
Click to collapse
Little bit more information
- On the Bootloader screen of my MT7-TL10 (Gold 32 GB, 3 GB RAM version), I see "Phone Unlocked" in red, which means that my bootloader is unlocked. (refer to attachment)
- When I run the command 'Fastboot OEM get-bootinfo', it returns 'UNLOCKED'.
- However, whenever I try to flash a custom recovery, it gives me an error 'FAILED: (remote: image verification error).
- At the same time, if I flash stock recovery, it is successful.
Detailed Information
- When I run the command 'fastboot oem get-bootinfo' it returns 'UNLOCKED'.
- However, when I run the command 'fastboot oem get-lockstate', it returns 'Locked'
- I rolled back to KitKat 4.4.2 - But the process of roll-back to KitKat 4.4.2 was not as simple as it was described in many forums and I first ended up soft-bricking the device
- I followed the restore process described on Huawei's website and ended up flashing a chinese ROM (JAZZ) on my MT7-TL10 and there were plethora of chinese apps
- Then, I unlocked the bootloader using (fastboot oem unlock <unlock code>) and on KitKat, both commands 'fastboot oem get-bootinfo' and 'fastboot oem get-lockstate' returned 'UNLOCKED' (Hurray!, That's what I thought but...)
- Realizing that the bootloader was finally unlocked, with the help of @acbka, I was finally able to restore Lollipop (version 5.1.1 - B326) and to my utter disgust, after upgrading, I found out that I was again not able to flash a custom ROM - On Lollipop, the command 'fastboot oem get-lockstate' again returned 'LOCKED' and the command 'fastboot oem get-bootinfo' returned 'UNLOCKED'
- As you can see, I was back to square 1 and I still can't unlock the bootloader and therefore, I cannot root my phone
Final statement
- When I rolled back to KitKat, the Bootloader showed as Unlocked and I was able to flash custom recovery TWRP
- After upgrading to Lollipop (5.1.1 B324 and B326), I am unable to flash custom recovery (somehow, the bootloader shows as 'Locked' when I run 'fastboot oem get-lockstate')
- If I flash stock recovery, it is successful
- The error 'FAILED (remote: image verification error)' implies that the bootloader is locked and that's why it forbids flashing of custom recovery BUT it allows flashing stock recovery
Please see the attached pictures, which will show what I mean.
I will really appreciate any help to enable me to flash a custom recovery!! Please help!
i also face the same problem any one can help us ?
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
prahastaabenk said:
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Click to expand...
Click to collapse
kingrk said:
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Edit: The link that you posted is not dead - it didn't open on my smartphone. The author of that post ACBKA helped me and we both tried it but could not beat the bootloader. While it shows that it is unlocked, it is still restrictive and doesn't allow flashing of custom recovery.
awzx_77 said:
i also face the same problem any one can help us ?
Click to expand...
Click to collapse
I have an idea!
I remember that when I was troubleshooting the problem (my smartphone was soft-bricked when I tried to rollback to KitKat and I ended up flashing Chinese 'Jazz' version on my TL10), I had realized that the bootloader was FULLY UNLOCKED on the chinese Jazz ROM and I could actually install a custom recovery. So, here is the idea:
a) First roll back to KitKat 4.4.2 --> I believe that there is a procedure on XDA to roll-back to KitKat
b) Change the phone's location to China
c) Install custom recovery and root phone by flashing superuser
d) Upgrade to Lollipop 5.1.1 (Chinese version)
e) Upgrade to Marshmallow beta (Chinese version)
f) Install custom recovery and root phone
same problem
just unlock the bootloader again using unlock code!
it worked for me
+1 for @xAghilx. Same here.
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!
Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /
thiagoserrao said:
Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /
Click to expand...
Click to collapse
On fastboot oem lock... I get "Command not allowed".
On the other 2... "root type is risk".
Not working.
same here
So... No method to lock the bootloader once it is unlocked?!
Update through OTG. It will relock bootloader.
alexcraciun said:
Update through OTG. It will relock bootloader.
Click to expand...
Click to collapse
any one can verify this method ?
greets, Peter
why would you want to relock when everyone is trying to unlock it?
the re-lock and un-lock bootloader function,
is it the same as the OEM lock and unlock option in developer mode ?
pardon me if this is a noob question but i really
TIA
How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter
I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked
CCJ22 said:
I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked
Click to expand...
Click to collapse
sorry, sell my unlocked evr-l29 yesterday
greets, Peter
Anyone willing to sell unlocked bootloader EVR-L29 please DM me your price
alexcraciun said:
Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!
Click to expand...
Click to collapse
Relock your Bootloader with your Unlock Code.
Command:
fastboot oem relock your Code (16 character)
---------- Post added at 04:29 PM ---------- Previous post was at 04:23 PM ----------
greddy said:
How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter
Click to expand...
Click to collapse
Use this File and Dload Method works
https://www.androidfilehost.com/?fid=6006931924117916589
letschky said:
Use this File and Dload Method works
Click to expand...
Click to collapse
Do I lose my data if I go back to 9.0?
KalleGermany said:
Do I lose my data if I go back to 9.0?
Click to expand...
Click to collapse
Yes,please Backup your Data!
i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition
BlvckSensei816 said:
i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition
Click to expand...
Click to collapse
No thank you.
Hello guys,
As always, I am here with a new share. I am sharing with you the deep testing app for Android 10 RM5 pro. I got to fastboot with this app. Next to unlock....[Update: UNLOCKED & Rooted]
Go on try it out.
The sweet guy who shared this video and app.
https://www.youtube.com/watch?v=LFuuZSh6C-I
The apk link here:
https://www.youtube.com/redirect?re...vPDNolgt_uV4AaABAg&q=http://shorturl.at/acuT5
Note: I had already selected OEM unlock in my RM5P since long, so I just installed this apk and opened and selected
QUERY VERIFICATION STATUS (right top corner). It showed Review Successful. Select START IN-DEPTH TEST.
You go straight to fastboot..
Enjoy LOCKDOWN safe in your home.
Thank you for reading.
Do you know if work for european devices?
loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
Officially no, but for me and several others it still worked, even with an EU phone.
I had to upgrade to Android 10 and then follow the steps described here:
https://c.realme.com/in/post-details/1244566811094024192?language=en-US
Btw., it's better to stick to the official post from realme I linked above, apps and links on youtube could be malicious.
I am using RM5P Indian version. The youtube link is safe. I didn't find any issues.
More than that, this apk was already listed in xda by faisalxp. I realized that late.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615.
Go to this link to download safely.
loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
AFAIK, installing this apk and getting into fastboot wont do any harm to your mobile.
Unlocking BL will erase all your data.
gracias !!
Can i unlock BL version RMX1971_11_c.02 with this apk
Juni_MJ said:
Can i unlock BL version RMX1971_11_c.02 with this apk
Click to expand...
Click to collapse
Yes, that's exactly what I was on before unlocking and rooting (INDIAN version).
Install adb and fastboot drivers in PC.
Good practice is to put all the necessary files in the C:/adb folder for installing twrp recovery.
Backup your data/pictures/notes etc first to pc.
Enable OEM unlock in Developer options. Enable USB debugging.
Install deep test apk and follow the instructions and get into FASTBOOT.
In fastboot type: fastboot flashing unlock and enter, and then unlock.
Needed Files:
twrp - link: https://files.orangefox.tech/OrangeFox-Beta/rmx1971/OrangeFox-R10.1_1-Beta-RMX1971.zip
vbmeta - link: https://drive.google.com/file/d/17hHXy4tJVxoXAIdTuVV--gq6qI_fsmaQ
But my realme 5 pro have (Indonesian version) this is work to ?
Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.
Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615
jijojamie said:
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.
Click to expand...
Click to collapse
Oke thanks i hope
this work on my phone ???
jijojamie said:
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615
Click to expand...
Click to collapse
i have problem command write failed with this but in depth test work
Juni_MJ said:
i have problem command write failed with this but in depth test work
Click to expand...
Click to collapse
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.
jijojamie said:
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.
Click to expand...
Click to collapse
Okee thanks
Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system
prashant.palange said:
Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system
Click to expand...
Click to collapse
What's the status now? Fixed?
Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.
RockV said:
Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.
Click to expand...
Click to collapse
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.
jijojamie said:
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.
Click to expand...
Click to collapse
Actually when i press that button it shows this "You can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode".
so I went into fastboot mode and used the command fastboot flashing lock it wiped my data and rebooted to welcome screen (language region setup)
Should I now use the app to "Apply to exit in-depth test"? or don't use the app?