I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot NB1-boot.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
Sorry I've put the recovery for Nokia 5 by mistake, now replaced with correct one.
Click to expand...
Click to collapse
To activate maintenance purposed bootloader, you need to load original stock firmware with OST LA, then click "Edit phone data". When OST LA prompts "Boot FTM mode fail", the maintenance purposed bootloader is loaded.
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
----------SEPARATOR----------
Here's how to enter Emergency Download mode:
1. Enter Download Mode by using OST LA.
2. After maintenance purposed bootloader activated by OST LA, type this command:
Code:
fastboot-android oem reboot-edl
In order to enter Emergency Download Mode. It may complex, currently it's the only way to enter Emergency Download Mode without disassembling.
3. Do something with your phone with QFIL.
----------SEPARATOR----------
I finally untrapped my Nokia 8 prototype, which has an unlocked bootloader.
Although Nokia 8 cannot enter EDL mode (Or 9008) with EDL Cable directly while Nokia 5 and 6 are able to enter EDL mode with EDL cable, I still figured out how to enter the EDL mode on Nokia 8 without any specific peripherals.
With @heineken78‘s nb0tools2016v2, I was able to unpack few of files from Nokia 5/6/8's nb0 firmware from @blackpanther0582, but that's only about bootloaders and rawprogram*.xml and patch*.xml, and I was not able to unpack any further, the program got overflow and terminated.
These files should be enough for unbrick your phone from full brick.
Anyway, that's off topic.
After I entered the EDL mode of my Nokia 8 prototype (with provided retail firmware installed), I used Partition Manager from QFIL included in QPST 2.7.460. I attached the screenshots of the partitions.
However, I noticed there's no recovery partition, which makes the TWRP port to Nokia 8 confusing.
(Although our Chinese Team ported TWRP to Nokia 6 and 5 recently)
And which partitions are important for bootloader unlocking?
Since we could enter EDL mode easily, it should be easy to unlock bootloader for Nokia 5/6/8 currently.
There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.
CazeW said:
There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.
Click to expand...
Click to collapse
Well, I got this information from Nokibar.
To enter Recovery for factory reset if you want to try it out, here's the method provided by HMD:
1. Power off your phone.
2. Press and hold Volume Up key and connect your phone to PC.
3. Waiting for Android robot on the ground displays along with NO COMMAND, release the Volume Up.
4. Press Volume Up while pressing power key to get Recovery menu.
Click to expand...
Click to collapse
It does have recovery, but I still can't figure out which partition includes it.
hikari_calyx said:
Well, I got this information from Nokibar.
It does have recovery, but I still can't figure out which partition includes it.
Click to expand...
Click to collapse
Thank you for the reminder that I found it
hikari_calyx said:
I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot nokia-ta-1004-twrp3.1.1-7to-recovery.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
Click to expand...
Click to collapse
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.
CazeW said:
now we just need a way to unlock the bootloader and we can get rooting
Click to expand...
Click to collapse
HMD promised they'd unlock all Nokia phones one by one. It's just a matter of time till they reach Nokia 8.
But if someone can figure out how to do it before that happens, that'd be amazing
CazeW said:
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.
Click to expand...
Click to collapse
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.
hikari_calyx said:
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.
Click to expand...
Click to collapse
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.
hikari_calyx said:
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Click to expand...
Click to collapse
Prototype units are for development use, so most likely have secure boot disabled.
In retail unit or production unit with secure boot enabled, if you modified the bootloader (or its partition), the secure boot verification will fail.
CazeW said:
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.
Click to expand...
Click to collapse
I updated the procedure of entering Emergency Download mode on topic. You can give it a try if interested.
How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Araa01 said:
How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
Use adb : adb reboot recovery, then hold the power + volume up buttons.
gee2012 said:
Use adb : adb reboot recovery, then hold the power + volume up buttons.
Click to expand...
Click to collapse
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Araa01 said:
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
No, don`t think so but for me thats the easiest method to get into recovery
gee2012 said:
No, don`t think so but for me thats the easiest method to get into recovery
Click to expand...
Click to collapse
Thank u! When we get oreo i must shoot full wipe so.. :d
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Interesting to see 'OEM Unlocking' in the Developer Settings.
Steve Geemaggio said:
Interesting to see 'OEM Unlocking' in the Developer Settings.
Click to expand...
Click to collapse
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.
alexcannasV said:
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.
Click to expand...
Click to collapse
I see! Well then I guess we got to wait for Nokia to step up and do it then.
Great to be running pure AOSP out of the box though. I'm grateful for that, but would love to be able to get rid of the mountain of Google apps pre-installed.
Glad Nokia changed their mind about unlocking the bootloader!
Steve Geemaggio said:
Glad Nokia changed their mind about unlocking the bootloader!
Click to expand...
Click to collapse
Hold your horses! Haven't seen any unlocked bootloaders yet...
I was reading today this http://neopodapsi.com/how-to-unlock-bootloader-on-nokia-8/
Is this for real or not? I was very interested in the Nokia 8 if they were unlocking the BL and releasing the kernel sources
Related
Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!
theres an update out. V14_20200820 with "minor bug fixes"
question to those how have a rooted quest... does it stay rooted when you install that update?
edit: okay normal way update does not work, becouse of custom twrp recovery... does anyone know where the downloaded ota-update file is located... i cant find it... (need to flash it with twrp)...
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
That happens when flashing TWRP. The guide says you should boot TWRP.
Garyyy said:
That happens when flashing TWRP. The guide says you should boot TWRP.
Click to expand...
Click to collapse
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
The TWRP Version isn't made by me. I know that it wont work when flashing it. Does your phone gets listed in the weird "artifact mode" when you type fastboot devices?
A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.
veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:
Steve8262 said:
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:
Click to expand...
Click to collapse
For me the artifact screen appears before doing the unlocking bootloader step and when it's on that screen, the device doesn't respond to ADB at all, so I cannot actually continue and root this device. I tried reflashing the stock firmware and even that didn't help. I'm honestly starting to regret purchasing this phone.
Does anyone else with this device ever use it for USB tethering or WiFi hotspot? First device I've ever had that actually loses power while it's plugged in. I can plug the phone into my computer, activate USB tethering, and it'll lose about 15% of battery every hour. I can keep the phone plugged into the wall, activate WiFi hotspot, and it'll lose about 10% of battery power every hour. This device is a bad joke.
Phenom2122 said:
A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.
Click to expand...
Click to collapse
The patched boot image is from the V12 firmware. I also had the artifacts but I was able to continue anyways.
Hey thanks for replying man. For me, ADB gets stuck on "detecting devices" and doesn't actually pick up my device at that point. But I have contacted the shop regarding the battery and charging issues and they have told me that my device is faulty and I'm picking up a replacement tomorrow. So hopefully I'll be able to do this soon.
I've just been kinda depressed about my purchase. I could've bought a Nokia 2 for just a little bit less and I would've been guaranteed quality. But I took a gamble on this 'Cubot' device with specs that were too good to be true for the price. It's a nice phone but it's battery and charging sucks balls. And I knew that it shipped with Android 7.0 but I thought that there would at least be an update to Android 7.2.1. I dunno, I'm just disappointed. My S4 Mini seems to kick this thing's ass in terms of battery power. And my S4 Mini is 6 years old, still on its original battery and has literally half the processing power and two thirds the RAM. I just needed this device for its 4G capability because my S4 Mini is the 3G model. I might sell it at a loss and pick up a MiFi router and new battery for my S4 Mini instead.
These phones are a huge missed opportunity. They pack some great specs for the price but offer a crappy, limited version of Android with no custom firmwares to be seen. Maybe if the battery thing works out and I can actually use this phone as a Wifi hotpot without it dying, I'll look into how to port a custom firmware to it. I think Slim or Carbon are in order, if they still exist.
Thanks for the reply dude. Maybe I'll have a different attitude to this phone once I have my replacement.
veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
Adb a different twrp
Garyyy said:
Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!
Click to expand...
Click to collapse
Does this method work with the Cubot P20 too ???
frank808 said:
Does this method work with the Cubot P20 too ???
Click to expand...
Click to collapse
No, because it is the boot image from the cubot note plus.
... dont want to open a new topic.
is there root option for the new cubot quest out there allready?
tko said:
... dont want to open a new topic.
is there root option for the new cubot quest out there allready?
Click to expand...
Click to collapse
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.
Garyyy said:
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.
Click to expand...
Click to collapse
the firmware i have.
but how do i patch the boot image?
tko said:
the firmware i have.
but how do i patch the boot image?
Click to expand...
Click to collapse
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.
Garyyy said:
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.
Click to expand...
Click to collapse
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.
tko said:
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.
Click to expand...
Click to collapse
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.
Garyyy said:
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.
Click to expand...
Click to collapse
okay if i could find a earlier version... , i would like to try it with 18.0
edit: found it... will try now.
crap, now the app does not give me the option to patch... no popup, no button, ...
edit2: okay, i cant use an older version, when i "install/patch" the app always first wants to update to the newest version.
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
File link is broken (file not found), please fix.
Repaired, sometimes a few times you need to refresh
I have rooted emui 9.1 mate 20x chinese but contact and dialer dont open ..any idea how to fix it?
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
I don't have twrp
walkwitmeinhel said:
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
I don't have twrp
Click to expand...
Click to collapse
Maybe you flash busybox in magisk and unzip the downloaded file then replace the file in system with root explorer. Try and let me know also. Ps. I never try before.
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
If you unlocked bl you can flash patched img and root
walkwitmeinhel said:
If you unlocked bl you can flash patched img and root
Click to expand...
Click to collapse
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556
dladz said:
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk magisk_patched.img
walkwitmeinhel said:
Fastboot flash recovery_ramdisk magisk_patched.img
Click to expand...
Click to collapse
Yep I know pal..doesn't work.
Have done this hundreds of times.
Don't worry about it, I'm getting rid of this turd of a phone.
1+7pro here I come.
dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
I have highlighted your problem above. This is a mate 20 x thread. You have a p20 pro.
facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Does this also work on my Huawei Mate 9?
And did you just patch the EMUI 9.1 recovery_ramdis via magisk or something else?
Doesn't work for me I have AL00 135
i had the same prob: the trick ist to keep Vol up and (!) Power at the same time until the blue bootschreen from the honor appears. Do it NOT as in earlier times: Do NOT realese power after the first vibration as before. After flashing the modyfied patched recovery (modyfied by magisk), keep both buttons until the blue honor bootscreen apears, then release the buttons & you will see only one text line (not the three), which indicates that the v10 is booting with root!
Anybody want to sell their rooted mate 20 x? United States only
Thanks
Does this work for Mate 20 non-X?!
facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
I've been looking for a way to install Magisk on a Huawei Mate 20 Lite (running EMUI 9.1 before) for weeks, and you gave me the solution (= reboot to eRecovery then wipe before the first boot) ! THANK YOU !!!
What I need to do is to downgrade the OS to Android 9 so I can unlock the bootloader.
How can I do the downgrade? I already have the special Harmony cable for the downgrade.
Hlw all.
Sorry for late to write this post. I will write this post in several parts. So Don't angry if i am late.
PART 1:
HOW TO UNLOCK BOOTLOADER
Click to expand...
Click to collapse
First add a xiaomi account on your device.
Now
1. Go settings
2. My Devices
3. All Specs
4.Miui Version
Tap 5 times to activate Developer Option.
Now return settings menu
And Scroll down
Go
1. Additional Settings
2. Developer option
3.OEM Unlocking [ On This]
Now turn on your phone's internet connection through personal data pack.
Now go Mi unlock status and press add account .
Your Device will be added successfully.
You have to wait 10 days for unlock your bootloader.
Xiaomi privacy policy
Click to expand...
Click to collapse
Now Go xiaomi website and Download xiaomi unlock tool .
You will need a pc or laptop with internet connection for this process.
Extract that zip and open Xiaomi unlock.exe
Login your Xiaomi account.
Backup important Documents on your phone.
Click to expand...
Click to collapse
Power off your Phone
Press "Power button + Volume down"
for fastboot mod .
Connect your phone through usb cable
Now press unlock
When it will complete 100%, Your device will unlocked and Reseted.
PART 2:
INSTALL TWRP
Click to expand...
Click to collapse
First you have to Download TWRP. Official twrp is not release. So you have to download unofficial twrp. it is safe and 100% well for Mi cc9. Because i am using this.
Download this from here:
https://androidfilehost.com/?fid=6006931924117916679
And Also download
adb usb driver version 1.4.3.exe
Install this software .
Next you have to enable usb debugging in your device.
Connect via usb cable to your pc or laptop.
Now unzip the twrp file and go that folder .
See many cmd command file in this zip inside.
Just open last one
Now write
adb devices
Click to expand...
Click to collapse
Screen on your phone and Ok the demon they ask.
Next write
adb reboot bootloader
Click to expand...
Click to collapse
Now write
fastboot flash recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
fastboot boot recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
Twrp will install successfully. just disconnect your phone and press power button + volume up.
Twrp will appear which one you install.
Any help you need just comments here if you failed.
Thats all for today.
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
dragokanev said:
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
Click to expand...
Click to collapse
Use those phone number and password which one you sing in for unlock bootloader.you need internet connection to complete this process.
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
Yes. You have to write:
fastboot boot recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img
easier to rename the file to twrp.img .....
Please help to restore CC 9
Please help me bring my Xiaomi CC 9 back to life. I updated it with MIUI 11.3.3.0.PFGEUXM and my device does not boot normally. My bootloader is locked and an account is not installed in the developer settings. Does anyone know what to do ???
I got error -1 on my smartphone when I added account and device in the '' mi unlock status '' menu.
How to solve
--
Edit:
resolved: I logged out and logged into the Mi account on the device and gave no error
I have to wait 168H to unlock
Tks
GSI's are quite good. I have good SOT with ArrowOS GSI: 12h - 13 h. I think it's more interesting to use Pie GSI's for now.
Where can I get this ArrowOs GSI rom?
Unlock tool stops at 50%
What should I do when the Unlock Tool stops at 50% and reports: couldn't verify the device. Is it because I haven't waited the 10 days yet?
You have to wait to unlock bootloader.
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
you dont have to boot the image if you flashed it first, if you did 'fastboot flash recovery recoveryname.img', no reason to do the boot part, just do fastboot reboot-recovery
if you dont want to flash twrp over your stock recovery, then use the fastboot boot recoveryname.img and then mess around with twrp, backup everything and flash a new rom and reboot, next time you reboot to recovery, stock will still be there
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
axlina said:
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
Click to expand...
Click to collapse
In this unlock tool folder ( Install Drider) one file exist.
You must install it. Then your device will connect.
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
axlina said:
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
Click to expand...
Click to collapse
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
TelumLetiferum said:
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
Click to expand...
Click to collapse
Download 15 seconds adb installer and answer question with three yyy.
I waited 43 hours to unlock bootloader.
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
kingofmb said:
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
Click to expand...
Click to collapse
It's power button +volume down... Try again
For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/
I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.
whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.
Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai
horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.
[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...
Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.
An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).
@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.
-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.
An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?
An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.
Code:
By Doing this, You may Void your warranty..
Neither Me nor XDA is Responsible for any Damage Caused for Your Mobile..
If you show Finger at me, I'll laugh at you..
Why there is need for this Guide?
When I got my Realme 5, I wanted to Unlock the Bootloader, Install the TWRP Recovery, root it and finally Install a Custom ROM. So, I've Searched for it and Finally Disappointed B'coz many Guides were wrong and some were Very Old and Outdated Guides.. So I've Researched and now with many problems, Finally I've Unlocked the Bootloader, installed TWRP and finally Flashed LineageOS 17.1.. So, this Guide saves your time, I've Included the Steps What I did, you guys can simply follow it..
This Guide is only applicable for Realme 5(rmx1911) and not for Realme 5i, Realme 5s or Realme 5 Pro..
Click to expand...
Click to collapse
Things You need to Continue :
A Windows Laptop/PC (Windows because, I am showing the Procedure with Windows)
Minimal ADB and FastBoot
Recovery (I've flashed PitchBlack Recovery, but you can also do this procedure with TWRP recovery)
Of course a Realme5 (rmx1911)
In-Depth Test apk
All the Download Links of above files are in Attachments..
Click to expand...
Click to collapse
Procedure :
Steps to Downgrade from RealmeUI 1 to ColorOS 6
If you're in Latest android 10 RealmeUI, first you need to downgrade to ColorOS 6 android pie.
To do so, download ColorOS package(.ozip package) from below link.
Open this .ozip package with File Manager app and Locate this package.
Click on that package, A pop-up will appear, In that Select "Upgrade Now" or something like that..
It will wipe your data and It will boot into ColorOS setup, Complete the Setup..
Users who are in ColorOS 6, need not to follow above Steps!
Click to expand...
Click to collapse
Steps to Unlock Bootloader:
Enable developer options in settings and enable OEM Unlocking, USB Debugging from Developer Options from Settings.
Download and Install In-Depth apk from attachments.
Open it and Click on Start Applying.
After 20min Open app and click on "Query Verification Status" .(if you dont see like this wait for some moretime, maximum it will take upto 24hours only)
If you see something like "Review Successful", You are good to go..
Select "Start the in-depth test", You will be forwarded to fast boot mode..
Connect the mobile to PC.
Now comes the role of PC/Laptop, Download the Fastboot and Minimal ADB, Recovery.img and vbmeta.img From the attachments.
Extract that fastboot zip in some Directory, Copy the recovery.img and vbmeta.img to the fastboot folder.
Open the Minimal ADB and Fastboot and in that open "cmd-here.exe"
Type "fastboot devices", then enter, You should see something like serial number.
Type "fastboot flashing unlock", then enter, now check ur phone you will see something like "Unlock" or similar to something..
You need to select the Unlock with the help of volume button and select with power button.
After Selecting "Unlock" all data will be deleted and Your Phone will be unlocked..
HURRAY, YOUR PHONE IS UNLOCKED
Installing Pitchblack Recovery :
After Unlocking Phone all the Data will be deleted, complete the setup wizard and enable USB Debugging.
Connect the Phone to PC via USB.
Open ADB Fastboot folder and select "cmd-here.exe".
Type "adb devices" you should see something like Serial Number.(If you did not see, re-insert the phone cable to another port and check)
Type "adb reboot fastboot", You will be forwarded to Fastboot mode.
Type "fastboot flash recovery recovery.img"
Type "fastboot flash vbmeta vbmeta.img"
Disconnect the Mobile from PC, then click on Volume down Button Until you get Something Like "Recovery" and Select using Power Button.
HURRAY! YOU'VE INSTALLED RECOVERY
IF YOU WANT TO ROOT YOUR DEVICE, DOWNLOAD MAGISK AND INSTALL IT FROM RECOVERY
Click to expand...
Click to collapse
IF YOU WANT TO GO TO RECOVERY AGAIN JUST BOOT INTO FASTBOOT(Power-off Your device, click on volume down button and power button simultaneously, within few seconds you will boot into fastboot) THEN CLICK ON VOL- BUTTON UNTIL YOU GET RECOVERY OPTION, THEN SELECT IT USING POWER BUTTON
Click to expand...
Click to collapse
You've Unlocked BL, flashed RECOVERY, Installed Magisk, Now what? Go and Search for your Favourite ROMs and flash them
Realme 5 Downgrade package link
{Mod edit}
triplr_dev_users
Test forum for ROM Builders !
All roms Welcome, All devices welcome!
Samsung Note 3,4 Qualcomm and exynos 5433
Galaxy Tab S2
Realme 5(rmx1991)
All things RPi 4 Family
An open discussion on Tech, Dev and Life
Welcome .
Rule 1. Have fun
Rule 2. Be nice
{Mod edit}
Reserved
supper sir i have very usefull i have flashed a lineage 17.1
with ur guide and i have unlocked boot lodder also thank u very much well done sir
Sensui--moksha said:
supper sir i have very usefull i have flashed a lineage 17.1
Click to expand...
Click to collapse
Glad, this helped!!
Why happend like this in depth test ?
Bebe's said:
Why happend like this in depth test ?
Click to expand...
Click to collapse
Sorry for the delay bro, I think you can't unlock the bootloader of Your Phone, bcoz it is not directly from the realme, I mean the phone which u bought is customized by your sim(carrier) company
Hello. The Downgrade file is not in the attachments thanks
nezuxiv said:
Hello. The Downgrade file is not in the attachments thanks
Click to expand...
Click to collapse
dude I have updated the post with the link to downgrade package, by the way thanks for informing
bro by installing pictblack recovery my phone got in a recovery bootloop and internal storgae is not showing ay files help pls
smarty7880 said:
bro by installing pictblack recovery my phone got in a recovery bootloop and internal storgae is not showing ay files help pls
Click to expand...
Click to collapse
Did you flash vbmeta.img ?
does the downgrade firmware supports realme in philippines ? thank you so much sir.
I am at color os v7 I also need to downgrade fast reply will be appreciated
Dar_shan_11 said:
I am at color os v7 I also need to downgrade fast reply will be appreciated
Click to expand...
Click to collapse
Yes, You need to downgrade...
I unlocked my bootloader ..than I installed recovery and after than I installed vbmeta.img
After that I tried to install Havoc Os.
Now I'm stuck at bootloop, can you help me
I must be blind but I can't find the downgrade file in your attachments...
(Edit) Never mind, it's not in the attachments. ^^;
Is there any guide to do it on realms UI?
i have RMX1911ex_11_A.31.
i should follow steps from Unlock Bootloader
correct?
It dœsn't work: my phone just comes back to the fastboot…