Relock Bootloder In Realme 5 pro - Realme 5 Pro Guides, News, & Discussion

I am not responsible if anything goes wrong with your device.
First of all backup your all data. This process will erase data. Now here is steps...
flash stock ozip file downloaded from Realme website thru twrp after that flash same ozip file thru stock (rui) recovery, then connect fastboot and trigger "fastboot flashing lock". Will erase u r data and lock ur bootloader. Wont brick ur device. Tried many times in RUI.
In this process i am on RMX1971EX_11_C.03 and flash RMX1971EX_11_C.03 ozip file.
Note: u should not flash anything like vbmeta or any modifications after ozip flash
All credit goes to its original creater

Related

[NOT WORKING] ReLock bootloader for ZE551ML

After some research on internet and xda i decided to try to relock my bootloader with the information provided by RealYoti, and this is how i did without causing a war conflict a Cthulhu evocation or a burning Zenfone
Anyway follow this guide at your own risk, turn on your brain and everything will be fine (hopefully)
Download these files
AFT: https://mega.nz/#!LcwhXDLZ!PN1jzQ0hD...QyvMzN8VK4fVBU
RAW: https://mega.nz/#!7cA3nTZC!NiHOzVoVP...axpE2es7lrwGpI
Install the Asus flash tool
Reboot your zenfone to bootloader
Open the asusflash tool
Select your model in the drop-down menu (under the button settings)
Choose if you want to keep the data or to wipe it all (i wiped)
Click on the box and the select the raw file you just downloaded
Connect your phone to the pc with the original usb cable
Now you should see your phone in the device list, check if all is ok and then start the flash clicking the green button on the top
Wait for 6-7 minutes and your phone should boot to android but now is recognized as ZE550ML, we have to fix this
Reboot to bootloader
Download from here (thanks to Shaka Huang) the last recovery set for the ze551ml (recovery.img droidboot.img boot.img)
Flash it from cmd:
Code:
fastboot flash fastboot droidboot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash boot boot.img
Now we are ready to flash the ZE551ML firmware download the last one from the asus support site
From the bootloader enter in the recovery
Apply update from adb/sideload
From the pc CMD type
Code:
adb sideload thezipyoujustdownloaded.zip
Wait
Wipe data/cache factory restore
Reboot
Enjoy your warranty
Let me now if there is any unclear passage
Thanks to:
RealYoti
Shakalaca
I Tried to flash twrp after this procedure and it worked so the bootloader even with this method remains unlocked, it only reverts to stock
this is awesome in case you need to regain warranty!!
I Updated the first post, the bootloader after a deeper research remains unlocked, so the method with the raw file reverts only to stock
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Very strange
To be frank, i didn't even gave a thought that it will work
In this way can I return to stock rom ?
I cant download the files from mega.
Waiting for an other method for relock the bootloader.

[AS990] Custom Recovery and Keep Stock

Hey guys, I have been working on this for a while an I think I finally have the answer as to keep stock AS990 and have a custom recovery.
Please note I will not be responsible for bricked devices. If you don't understand something do some research before you start.
Lets get started.
To get roms to install, I had to use the whole guide found here then install a custom rom, create a TWRP backup, take the backup off the internal sd card then once I finished the steps below I put the backup back onto my internal sdcard and used TWRP. Now some of you may be asking "Why the heck did he do that for?". Well when I went to install a ROM, I could not mount the system partition so therefore I used this work around because I had made a backup before I found out the method below. If anyone has a fix for this please be sure to comment.
Download and extract the files here
First off you will need to be on Stock AS990 and rooted. If you have not done this please follow the guide located here to do that.
If you are on a rom that cannot be rooted, follow this guide and use the files found in the restore bullet point to downgrade then root. Backing up your build.prop should not be necessary in this case since you are doing a downgrade.
After you have done this, root and use flashify to install ls990 TWRP.
Reboot your device into recovery.
If all goes well, You should now be stuck in fastboot mode.
Flash the following files found in the folder you downloaded earlier.
Open the folder you extracted the files to earlier, hold shift, right click in a section of the folder where no files are then select "open command window here".
Type the following commands into the CMD window.
fastboot flash aboot aboot.bin
fastboot flash boot boot.bin
fastboot flash dbi dbi.bin
fastboot flash factory factory.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rct rct.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash tz tz.bin
Pull the battery and turn back on and the rom should now boot back into your stock system.
Again use flashify to install ls990 TWRP.
Make a recovery of your current rom.
Flash the rom you backed up.
For me I have figured out how to get mms, data texting and calling on a custom rom with my carrier (Carolina West Wireless).
I installed Google Hangouts then used shortcut master lite to find the apn settings in hangouts which are not the same as using other methods.
If I left out anything please let me know thanks.
Well that's all for now.
Not sure who all to give credit to but this is a compilation of my work as well as all the guys who made the post above.
You may be able to use this method to root as well but have not tired that yet.

Need help with a bootloop in my ZE551ML Z00AD device [explained in detail]

So I had a very old cm13 I think, never touched, but then thought of going for RR 7.1 rom,
but I had very old rom, and what I did is
used xFSTK-Downloader switched to second tab, mrd a0/bo+ moor a0 + crc
and then from options> modify settings
enable gp flag override 0x800000807(PLEASE HELP CONFIRM IF IT'S 4 OR 5 ZEROS BEFORE "807")
and then select fw dnx, ifwi and OS Image
begin download, connect phone with vol down button, let it happen it used to happen successfully
then I use asus flash tool, flash twice, first time wait for 30 mins, then for 20 mins, select wipe yes and select my device, reconnect usb and let it happen successfully
then I flash
fastboot flash splashimage splashimage.img
fastboot fastboot flash droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot format cache
fastboot reboot
basically according to this vid
https://www.youtube.com/watch?v=RISRlqFj5k8&t=1139s
and after I got into device, updated to 2.20.40.194 and then to 4.21.40.223
all went success, but I forgot to download that bootloader unlock apk, and went to flash twrp, bad thing happen, phone was working, but could not get into recovery, so I thought of using the apk to unlock, and apk used to stop working, and then I tried the xfstk again to flash those three items, but now it's showing me
errors
FAILED (remote: flash_cmds error!)
so then I followed another guide to extract few files from latest stock firmware zip
I'm able to flash these files
bom-token_ann_a0-mofd_v1-ze551ml
dnx_fwr_ann_a0-mofd_v1-ze551ml
ifwi_ann_a0-mofd_v1-ze551ml
all those bin files get flashed successfully
but when it comes to splash, recovery boot droidboot system
it all ends up with that flash_cmds error!
so how do I get my phone fixed, please help
flash files with xfstk again with correct gp flag value. (u might have entered the earlier bootloader to make sure xfstk worked see ifwi version before and after flashing xfstk if it changes or not) when boots into temp bootloader flash desired bootloader files there. it will allow u to flash any image
keep in mind gp flag value is always 10 digits hence correct is four zeros. 0x80000807

Mixed Nougat/Oreo partitions

My Honor 7x (BND-L21) is totally bricked for the moment. I think there is Nougat and Oreo partitions at the same time because of Huawei Multi-Tool. Now I can't boot into recovery/eRecovery and the device stucks in the splash screen (bootloader unlocked). I think I have to rewrite all the partitions but I don't know how to do it... If anybody has a solution it will be greatly appreciated, I tried for 1 week!
If your device has a locked bootloader or frp follow these steps
First of charge your device for 1 hour in whatever mode it is..
https://www.androidfilehost.com/?fid=11050483647474828964
Then download the service rom from the above link
Extract the contents of the downloaded file. Copy the dload folder from the extracted files to a sdcard.. (Directly to it not on any directory)
Insert the sd card..
Press all the buttons until the emui logo comes.
After the flashing reaches 100 percent.. Reboot the device unlock the oem in developer option..
Step-2 (Computer)
Download adb drivers and fastboot and install them.
Download complete ota package for your device (make sure you have the correct build number because service rom has a different build number ) (download size will be above 2gb)
Extract all downloaded zip files. Then using huawei firmware extractor extract all contents of the update. app files.. (one update. App file in each zip files)
Copy
kernel. Img
Ramdisk. Img
System. Img
Cust. Img
Version. Img
Vendor. Img
And version. Img to the folder having adb files. And version and vendor files to sd card
//Make sure that the complete ota package you downloaded matches the os before the software brick(noughat or oreo) //
Open the adb folder and do shift plus right click to open command window there and connect your device in fastboot mode to pc
Use the below commands one by one each after completion
Fastboot devices(show your device if its connected)
Fastboot oem unlock (code obtained from huawei unlock page)
#factory rest occur
After tha enter fastboot mode again
Step-3
Fastboot flash ramdisk ramdisk.img
Fastboot flash recovery_ramdisk recovery_ramdisk. Img
Fastboot flash system system. Img
Fastboot flash cust cust.img
Flash twrp using
Fastboot flash recovery_ramdisk twrp. img
Boot your device to recovery mode.( Volume up plus power)
Flash version. Img to version partition and vendor. Img to vendor partition
If you want stock recovery back
Boot into fastboot mode
Enter the command
fastboot flash recovery_ramdisk recovery_ramdisk. Img
And do a reboot
Relock bootloader upto your wish..
Better keep oem unlocked in developer options
If you have both unlocked bootloader and frp follow from step 2
I heard huawei discontinued the unlock page
In that case use dc unlocker to find the code
It will cost some money
All credits to @mrmazak
Thank you I will try this but the dload method didn't worked when I tried 4 days ago...
I can't go into dload update mode (when I hold all the physical buttons the phone restarts and this appears (picture 1) and got stuck on this screen).
Also I don't know why but the phone doesn't charge, when I unplug it after 1h of charge, it shows the critical battery screen (picture 2) and it goes off...
Any help is reaaly appreciated!
Any other ideas?
gabrce said:
Any other ideas?
Click to expand...
Click to collapse
Though situation, if not charging. Bit to verify, try different cable and charging brick to make sure.
I changed twice the cable and nothing change...
Is there a method to factory reset the device in fastboot mode?
Maybe I should try HWOTA8?
gabrce said:
Maybe I should try HWOTA8?
Click to expand...
Click to collapse
Will need to de able to boot twrp for hwota to work.
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
gabrce said:
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
Click to expand...
Click to collapse
If battery is not charging, then it will not take a flash.
You can maybe try remove back cover and unplug battery, then reconnect see if it will take a charge.
As for your question about resetting with fastboot. You can wipe data, and maybe format system also. But I don't think that will help you.
My friend is asking help. His situation is similar. The phone is honor 6x.
My opinion is that something wrong with boot partition. you can ask some body extract the boot image from another phone. Then run "fastboot flash boot_ramdisk boot.img".
Hope it helps
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
gabrce said:
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
Click to expand...
Click to collapse
I try to help again.
Describe problem please
As I recall it is as follows
** Phone working,
** Attempts some backup or restore using multi-tool
** This made phone no longer boot
**Possible that nougat images flashes to Oreo partition tanle (or visa- versa)
**Now no recovery or erecovery will even boot.
**Also phone shuts off with low battery as soon as cable unplugged.
If this is the case, I see no way forward. Because the battery needs to hold something in order for flashing to complete

Question Rooting - anyone successful?

I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).

Categories

Resources