Hello,
today to my utmost rage i accepted system update, as i never had problems with getting the phoned rooted etc. after updates. But little did I know it was emui 5.0 along with android 7.0 update which pretty much rekt me.
The details of my phone:
HUAWEI VNS-L21
VNS-L21C09B336
kernel 4.1.18-g5e26674
Can provide more if needed.
The only thing I did was to get TWRP through SRKTool from here, xda, and rooting through it. And it worked flawlessly to my needs.
After the update I lost twrp, so without searching back then i tried to get it back through SRKTool to no avail. Downloaded newer SRKTool, same thing.
Then I started searching for more information regarding how to root my phone, during which I found out that I'm PHONE Unlocked FRP locked at fastboot.
And of course my "Disable OEM lock" in developer options is greyed out.
I tried p9toolkit from here, I tried command syntaxes in adb's fastboot, everything with USB debugging, nothing did anything. I can't flash either new TWRP or Revolution Recovery because the FRP lock isn't letting me flash anything, and for some reason i can't relock bootloader. I have correct unlock code, command line syntaxes just failed and p9toolkit produced errors saying that my unlock code is wrong (which is not true, I checked at huawei's site) or my phone is locked/unlocked depending on me trying to lock it or unlock it.
Even the built in recovery fails to get the package when I try to restore with it.
The boot message that "my device can't be trusted" is of course still present.
Feeling defeated I did a factory reset along with both wipes, hoping that'll let me change OEM lock in dev options and will clean the phone of many root related settings, but OEM lock is still greyed out.
Basically it seems the phone is locked in some kind of limbo of having bootloader unlocked but locked when you try to flash anything, because of FRP, and I can't relock to unlock FRP...and so on.
I would be extremely grateful if someone could help with sorting this out, basically I only want root, but it's just a mess overall.
Did you already try to dload an UODATE.APP file? If not:
1) create a folder on your external SD card named DLOAD
2) Download your firmware's update.zip file and extract it
3) put the extracted update.app file in the dload folder
4) boot phone with volume up + volume down + power
5) this will relock bootloader, install stock Android, stock recovery, stock boot (basically make every single thing stock) do you can start over again by rooting nougat!
I did not try it because I have no idea how to find the correct firmware for my phone, I have used the firmware finder from xda but the amount of results pretty much overwhelmed me so I didn't try anything with it, as i would probably get my situation worse.
EDIT: i found this site http://hwmt.ru/oth/HWFF/info/view.php?find_model= and there is update.zip of seemingly the same version as mine, is this the correct file http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87119/f2/full/update.zip?
Hello,
To install TWRP, may I know do I need to unlock the boodloader? I already asked for permission and have downloaded the MiUnlock but it is unable to unlock; error at 50%
Also, do I need root access before I do fastboot flash recovery?
Thanks!
leoncheong said:
Hello,
To install TWRP, may I know do I need to unlock the boodloader? I already asked for permission and have downloaded the MiUnlock but it is unable to unlock; error at 50%
Also, do I need root access before I do fastboot flash recovery?
Thanks!
Click to expand...
Click to collapse
- in redmi note 3G, you dont have to unlock, because the device has unlock by default from factory.
- yes, installing TWRP, you must ROOT your device
Hi all,
I've ran into a problem while attempting to flash TWRP recovery to my Lemfo LEM8 watch. When I boot into the bootloader I found out that it is still locked so I tried unlocking the bootloader by executing the command: fastboot oem unlock. Now the problem is that in order to actually unlock the bootloader I have to press the vol up button which is a problem since the Lemfo LEM8 doesn't have any volume buttons....
The reason why I want to unlocker the bootloader is because I want to temporarily boot into TWRP recovery, why temporarily? Because I am not sure I succesfully ported the TWRP recovery for my watch and I don't want to brick the watch with flashing a faulty recovery.
I know the tool: flashtool which can also flash the recovery to the device ofcouse but I rather temporarily boot into the recovery instead of permanently flashing it with flashtool.
Steps I took:
HTML:
adb reboot bootloader
fastboot devices
0123456789ABCDEF fastboot
fastboot oem unlock
....
So my question for you guys is: does anyone know how to simulate a volume up key press so I can unlock the bootloader?
Any other suggestions on how to install the recovery are welcome aswell ofcourse!
Thanks in advance,
Kasper
kaspertje100 said:
Hi all,
I've ran into a problem while attempting to flash TWRP recovery to my Lemfo LEM8 watch. When I boot into the bootloader I found out that it is still locked so I tried unlocking the bootloader by executing the command: fastboot oem unlock. Now the problem is that in order to actually unlock the bootloader I have to press the vol up button which is a problem since the Lemfo LEM8 doesn't have any volume buttons....
The reason why I want to unlocker the bootloader is because I want to temporarily boot into TWRP recovery, why temporarily? Because I am not sure I succesfully ported the TWRP recovery for my watch and I don't want to brick the watch with flashing a faulty recovery.
I know the tool: flashtool which can also flash the recovery to the device ofcouse but I rather temporarily boot into the recovery instead of permanently flashing it with flashtool.
...
So my question for you guys is: does anyone know how to simulate a volume up key press so I can unlock the bootloader?
Any other suggestions on how to install the recovery are welcome aswell ofcourse!
Thanks in advance,
Kasper
Click to expand...
Click to collapse
You do not need to unlock the bootloader on a LEM8. It does not actually validate the contents of anything you flash into recovery at all. Use SP Tools (flashtool, as you mentioned) to flash recovery (and/or system and boot if you like). You will need a scatter file specifically for the LEM8, which is available around the 'net. If your custom TWRP does not work, just flash the original recovery back in. (Make sure you extract the original recovery first, also using flashtool, or pull it out of the most recent firmware image if you choose to download one.) As long as you use the right scatter file and only replace recovery, you will not brick the watch. You might get a boot loop, but that's easy to fix by simply reflashing the original recovery.
I am in the same position. I think I have both root and TWRP but cannot load them in to test.
From what I have found is that the command "fastboot oem unlock" is only used with older Android ROMs and you need to go into developer options and turn on OEM Unlock.
You then issue the command "fastboot flashing unlock" so that you can then flash the twrp recovery image by issuing the command "fastboot flash boot recovery.img" or whatever you named it.
The problem is that the command "fastboot flashing unlock" results in a warning message on the watch screen that requires you to tap an accept radio button or similar. Unfortunately this radio button is hidden behind the curved screen at the bottom and you cannot use the round to square screen found on the turn off screen to bring it into view..
Edit: On a closer look with a magnifying glass when I retried it asked to push the volume button up, but since there are no volume buttons on the device then ???????
If anyone has a solution, I would be grateful.
I used Magisk to patch the boot.img to give root and Team Hovatek's Mediatek Auto TWRP Recovery Porter to incorporate TWRP into the recovery.img.
I have tried the SP Flashtool in many configurations without success. The watch simply refuses to reboot and I have to use SP Flashtool to flash the stock ROM back on it to get it to work.
Any help would be appreciated.
I Can't find Scatter File for Lemfo LEM8
Brentworth said:
You do not need to unlock the bootloader on a LEM8. It does not actually validate the contents of anything you flash into recovery at all. Use SP Tools (flashtool, as you mentioned) to flash recovery (and/or system and boot if you like). You will need a scatter file specifically for the LEM8, which is available around the 'net. If your custom TWRP does not work, just flash the original recovery back in. (Make sure you extract the original recovery first, also using flashtool, or pull it out of the most recent firmware image if you choose to download one.) As long as you use the right scatter file and only replace recovery, you will not brick the watch. You might get a boot loop, but that's easy to fix by simply reflashing the original recovery.
Click to expand...
Click to collapse
Please could ou tell me where i can find the scatter file for Lemfo Lem8, I've tryed to search on the net for days, but I can't find it.
Markap76 said:
Please could ou tell me where i can find the scatter file for Lemfo Lem8, I've tryed to search on the net for days, but I can't find it.
Click to expand...
Click to collapse
http://roundandroidwatches.proboards.com/thread/2937/lemfo-lem8-z29-m6739-16gb
Register and download your firmware; the scatter will be in the extracted download.
Or create one using the likes of WwR_MTK
Also, for the volume up issue - have you tried connecting a USB keyboard to your watch using a USB to Micro USB adapter? Long shot but never know? I've connected a mouse before and it worked. However Android had already booted and loaded the GUI so not sure about the lower boot level drivers etc
Hi, I need help, I'm new to this and I want you to answer me: I just installed the twrp recovery on my j500m and I have flashed magisk and the non-verity-opt-encrypt file started normal but I realized that I have unlocked oem disabled, I read somewhere else that if it is not damaged it should be disable the oem unlock option but when I'm going to activate it can not be activated for more than the button to activate, I think it's because of the non-verity-opt-encript file, I do not know if this could cause a brick when I turn off the phone and turn it on again, I need help, please.
you should before flashing twrp 3.1.1.1 or other files by odin
You must open the oem lock from the developers options
and active usb debugging
At start i want to say that I'm not responsible for your bricked devices, houses set on fire, bla bla bla and so on.
Hello
Since I see that many users are having problems with unlocking bootloader, flashing twrp and getting properly working Magisk. So here i come.
Downloads:
Everything you need you find here, on my OneDrive.
Unlocking Bootloader
BEWARE! After unlocking bootloader your DRM widevine will change to L3.
Steps:
- download and install Realme_x2_Pro_DeepTesting.apk,
- open app and apply for deep test,
- enable Developer Options by tapping 7 times Version in Settings > About Phone
- go to developer options and enable OEM unlock and USB debugging,
- open app once again after some time tap "Query verification status",
- If you got approved application tap "Start the in-depth test" and phone will reboot to bootloader,
- on PC, download fastboot tools from somewhere else(unless you already have it, its not on my OneDrive)
- open folder where you have your fastboot installed, hold shift and click right mouse buton and choose "open command prompt here"(or Power Shell in newer version of windows),
- connect your phone to PC, and write
Code:
fastboot flashing unlock
- now on phone select "yes"
- now your phone will reboot and erase all your data,
- now you have unlocked bootloader.
Flashing Custom Recovery
I will guide you how to flash Custom Recovery.
Steps:
- connect phone to PC,
- on your PC in command prompt type adb reboot bootloader,
- download TWRP image from mauronofrio or OrangeFox image from thread put in your fastboot tools folder on PC,
- download vbmeta.img from my OneDrive and put in your fastboot tools folder on PC,
- type
Code:
fastboot flash recovery *******.img
- type
Code:
fastboot flash vbmeta vbmeta.img
- when flashing is done, on your phone select "Recovery Mode" with volume +/- buttons and accept with power key,
- now it will boot into TWRP
Getting properly working Magisk
For now I recommend always using Magisk Canary Debug version cause it supports realme phones(stable needs magiskfix to get out of Core only mode).
Steps:
-download Magisk Canary zip to your phones internal storage,
- boot to Custom Recovery,
- flash magisk,
- reboot to OS.
Updating ColorOS on rooted phone via TWRP
Use Magisk Canary cause it supports realme phones(stable needs magiskfix to get out of Core only mode).
This is the only way to update ColorOS via TWRP without losing magisk or running into damaged boot/recovery image message on boot for now.
Steps:
- download latest Magisk Canary, vbmeta.img and latest update package(ozip) for your device(cn rom for cn device, global rom for eu/in device), if you download update via official OTA app the package is located in
Code:
/data/oppo/coloros/OTA/.otaPackage
- reboot to Custom Recovery,
- flash latest ozip through twrp recovery(don't reboot yet),
- flash vbmeta.img through Custom Recovery
- flash magisk(if flashing fail, than reboot recovery),
- reboot to system.
Locking Bootloader
Think twice after evey step you did if it's done correctly before doing next step to prevent HARD BRICKS.
Steps:
- download right latest ozip for your device from realme site(don't cross flash device, flash global ozip on eu/in devices and cn ozip for cn devices),
- boot to Custom Recovery,
- Flash ozip and after don't do anything else, just reboot to system,
- let it boot to OS and replace Custom Recovery with stock recovery.
- (optional) boot to recovery to check if it is stock, if its stock recovery than you can lock bootloader(don't ever try to lock with Custom Recovery),
- reboot device to bootloader and through adb go with:
Code:
fastboot flashing lock
- accept locking bootloader query on phone,
- device now will reboot and perform factory reset.
F.A.Q.
Q: Can't flash xxxxxxxx.zip(or xxxxxxx.ozip/xxxxxxx.img) in Custom Recovery cause it throws an error, what to do?
A: Reboot recovery and try again.
...
...
hello bro, so when we do this is imposible to relock bootloader?
Arn0ldx said:
hello bro, so when we do this is imposible to relock bootloader?
Click to expand...
Click to collapse
It is possible, but you need to use for it some other guide as I will not guide how to. It's because I don't want users to cry over their mistakes in my thread.
Jerry08 said:
It is possible, but you need to use for it some other guide as I will not guide how to. It's because I don't want users to cry over their mistakes in my thread.
Click to expand...
Click to collapse
OK bro I'll wait then
this method is compatible with CN version? Can we install a stock Rom or EU rom after unlocking the bootloader? It's really pity for the fingerprint I think as the majority will wait a fix for this issue before doing that
Thank you for your work anyway
Nice Work
Great Guide. But at this time i'm not willing to trade fingerprint unlock for root and magisk .
Already losing the loading animation for using my good old lawnchair was disappointing can go back to coloros launcher easy though.
Maybe someone will/can find a trick for this boot unlock problem.
Thanks for your efforts!
As I don't own a X2 Pro (yet) I'd like to know how presumably it is to get a solution for the "losing fingerprint problem"?
From other phones I know, that Widevine Lv1 gets lost but I never had the problem of losing my fingerprint scanner.
I'm planning to purchase X2 Pro and it seems a flaw for me if unlocking bootloader will disable fingerprint.
Does anyone ever try not to set up fingerprint, pattern or PIN lock from the first phone setup and then directly unlocking bootloader, flash TWRP, magisk and still have locking features working?
rooveg said:
I'm planning to purchase X2 Pro and it seems a flaw for me if unlocking bootloader will disable fingerprint.
Does anyone ever try not to set up fingerprint, pattern or PIN lock from the first phone setup and then directly unlocking bootloader, flash TWRP, magisk and still have locking features working?
Click to expand...
Click to collapse
Doesn't work. I tried it like that when I got the phone. Not logging in or setting anything on the phone, went straight to installing the unlock APK and unlocking the bootloader, still the FP issue.
rooveg said:
I'm planning to purchase X2 Pro and it seems a flaw for me if unlocking bootloader will disable fingerprint.
Does anyone ever try not to set up fingerprint, pattern or PIN lock from the first phone setup and then directly unlocking bootloader, flash TWRP, magisk and still have locking features working?
Click to expand...
Click to collapse
Will not work cause when you unlock bootloader it formats data, so fp lock will be removed...
henrym1203 said:
this method is compatible with CN version? Can we install a stock Rom or EU rom after unlocking the bootloader? It's really pity for the fingerprint I think as the majority will wait a fix for this issue before doing that
Thank you for your work anyway
Click to expand...
Click to collapse
This method should be compatible with CN version. And for the 2nd question answer is: no, at least not yet.
Is the FP issue permenant .i mean i locked the bootloader again and all seems good now....but does that mean the realme x2 pro cannot be rooted without loosing FP???
This sucks big time ...its a shame on oppo/realme
Wow, if there is no method of getting root on this phone and not losing the FPS it would be massive setback ?
Jerry08 said:
Will not work cause when you unlock bootloader it formats data, so fp lock will be removed...
Click to expand...
Click to collapse
I think we're lost in translation.
Is bootloader unlocking and data wipe causing a permanent fp lock removal? Or just the ones that we have already set? If it's the 2nd case, then we can go back and set it up once again, right?
loumaros said:
I think we're lost in translation.
Is bootloader unlocking and data wipe causing a permanent fp lock removal? Or just the ones that we have already set? If it's the 2nd case, then we can go back and set it up once again, right?
Click to expand...
Click to collapse
No, fingerprint sensor is disabled. Can't do anything with it on unlocked bootloader. And once you lock bootloader you get back fingerprint sensor.
Ist there any way/chance of the fingerprint issue getting fixed by xda developers (magisk module, flashable zip, whatever) or can this only by fixed by Realme itself via updating firmware respectively bootloader?
bmwbasti said:
Ist there any way/chance of the fingerprint issue getting fixed by xda developers (magisk module, flashable zip, whatever) or can this only by fixed by Realme itself via updating firmware respectively bootloader?
Click to expand...
Click to collapse
There's always a chance, be patient. I don't see a big issue with fingerprint. I got used to faceunlock. Using for a week already and I like it even more than unlocking with fingerprint.
@Jerry08
Thanks for your answer ?
It's not about not beeing patient, but rather don't have a good feeling if such a mandatory part of the phone won't work. It's just like buying a new car and not beeing able to use the remote control to lock the doors and telling people "I don't mind cause I got used to use the key instead" ?
Don't get me wrong, I'm using faceunlock very often on my device but I have a bunch of apps where I use the fingerprint scanner to log in oder authorize and I would really really miss that feature.
It's less about not beeing able to use the fingerprint scanner for a few weeks but way more about beeing able to use the fingerprint scanner in some days/weeks in connection with an unlocked bootloader (again).
As I need a new phone theese day (and Black Friday is ahead) I can't wait a few month to see, if this issue gets fixed. Otherwise I would just watch the Realme x2 pro forum and buy (or not) in a few weeks or months ?
bmwbasti said:
@Jerry08
Don't get me wrong, I'm using faceunlock very often on my device but I have a bunch of apps where I use the fingerprint scanner to log in oder authorize and I would really really miss that feature.
It's less about not beeing able to use the fingerprint scanner for a few weeks but way more about beeing able to use the fingerprint scanner in some days/weeks in connection with an unlocked bootloader (again).
Click to expand...
Click to collapse
I couldn't agree more. Most banking apps use fingerprint to bypass the password section. Also face unlock is not as secure as fingerprint.
It's a same as I would compromise on the not-so-good-photo quality over the speed and battery life of that device
@Jerry08 I did what you said, replaced the build.prop, then went to twrp, flash it, then flash your magisk canary you provided but build.prop did not get replaced. Here is the file https://drive.google.com/open?id=1CBvMuFwr84PDRZror4H9I8Std_kNNhQg My device name is RMX1991CN