Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
Related
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
prashanth_ said:
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
Click to expand...
Click to collapse
I have miui 12 how to root?
Ameer9963 said:
I have miui 12 how to root?
Click to expand...
Click to collapse
Which guide have you followed?
prashanth_ said:
Which guide have you followed?
Click to expand...
Click to collapse
I have followed miui 11 guide
But i have miui 12
Ameer9963 said:
I have followed miui 11 guide
But i have miui 12
Click to expand...
Click to collapse
Plz post how to patch boot image
Magist patched boot image not working to root
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
So i rooted my Oneplus Nord 2 and got into a bootloop wiped the device using TWRP booted into rooted OS and wifi and bluetooth are not working. I dont have a backup of EFS partition.
Flash Boot image
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
pankspoo said:
Flash Boot image
Click to expand...
Click to collapse
Didnt work
krugm0f0 said:
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
Click to expand...
Click to collapse
Didnt work
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
fellu4485 said:
Didnt work
Click to expand...
Click to collapse
You need to flash stock Boot image not rooted
pankspoo said:
You need to flash stock Boot image not rooted
Click to expand...
Click to collapse
I did
krugm0f0 said:
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
Click to expand...
Click to collapse
I can't get WiFi and Bluetooth to work
This error is almost exclusively caused by having the wrong boot.img.
I know you already said you're certain you flashed the correct boot.img, but the fact your phone is showing these symptoms means you likely have the wrong boot.img, as is true in 99.999% of these cases.
The only other possible cause of these symptoms would be because you wiped or corrupted your persist partition.
The persist.img partition contains unique data calibrated to your own device which contains calibration specific to your phone's wifi and bluetooth module/antennas, if you wiped this partition by accident, you will need to find a backup of the persist.img taken from YOUR OWN DEVICE and reflash it, no one else on these forums will be able to provide these for you.
Again, I'll restate that the chances of the persist.img case being the cause here is almost unheard of unless you distinctly remember tampering with the persist image, which you would have had absolute ZERO reason to have done so.
I would highly recommend that you double, triple, and quadruple check you flashed the CORRECT boot.img before resorting to messing with your persist.img, it's likely your download source provided the wrong one, or you mixed up the files in your downloads folder which happens frequently.
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
edit: link removed because i dissected the boot.img, and it indeed, is not an august boot img
how to manually pull boot.img
install dsu sideloader, install this GSI
enable developer settings, enable 'rooted debugging'
open up a terminal, and enter an adb shell to your device, and use this command
su
find /dev/block/platform -type d -name by-name
Click to expand...
Click to collapse
you will then take the destination it produces and input it into this command below respectively
ls -la /the/path/displayed/from/find
Click to expand...
Click to collapse
you will then have a list of all partitions. you will be shown the hardlink where it is pointed to. copy the device path for one of the boot partitions (/dev/block/sd**)
you then return to the storage folder of the phone using
cd /storage/emulated/0
Click to expand...
Click to collapse
then use dd to copy the partition into a boot.img
dd if=/path/to/boot/partition of=boot.img
Click to expand...
Click to collapse
pull the boot.img from device, reboot, install magisk, patch the boot.img and then flash it. reboot.
In the past we have had issues with cross flashing images from different security patches, causes no radios issue. Did you flash your vbmeta to disable verity and verification
? Check that your still on the right slot too, your active slot may have been changed when in fact your system is on the other slot, sometimes it will still boot this way but leftover partitions from your previous system build sometimes cause issues, sometimes the old modems don't get deleted during a system update and if the active slot gets changed it may still boot the system on the other slot with the old modems on the slot that's set to active. Flash vbmeta with disable verity and verification and make sure u flash vbmeta_a and vbmeta_b. Then if it still doesn't boot with radios working try setting active slot to the one that's not currently set to active and reboot. Just on off chance that it might be leftover modems from old system before u updated.
dmtec said:
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
Upload files for free - augustboot.img - ufile.io
Download augustboot.img for free from ufile.io instantly, no signup required and no popup ads
ufile.io
Click to expand...
Click to collapse
And thank you for posting the August image. If you have the time please upload a super along with radios if you feel comfortable doing that, my other thread lists partitions to exclude from upload if you care to do that. Either way we appreciate what you've already posted. Would probably help others. I think u said ur device is NOT TMobile? Radios may or may not be carrier brand specific.
PsYk0n4uT said:
In the past we have had issues with cross flashing images from different security patches, causes no radios issue. Did you flash your vbmeta to disable verity and verification
? Check that your still on the right slot too, your active slot may have been changed when in fact your system is on the other slot, sometimes it will still boot this way but leftover partitions from your previous system build sometimes cause issues, sometimes the old modems don't get deleted during a system update and if the active slot gets changed it may still boot the system on the other slot with the old modems on the slot that's set to active. Flash vbmeta with disable verity and verification and make sure u flash vbmeta_a and vbmeta_b. Then if it still doesn't boot with radios working try setting active slot to the one that's not currently set to active and reboot. Just on off chance that it might be leftover modems from old system before u updated.
Click to expand...
Click to collapse
My device is MetroPCS so essentially T-Mobile. I would upload supers and radios if I had the bandwidth to do it, currently my only internet access is a bridged xfinitywifi connection. When i flashed my boot img back over, I had acknowledged that I was already on slot b and only flashed b. when i realized what happened i flashed the original back over to no avail. i'm gonna try flashing vbmeta back over with those parameters.
okay so keeping in mind i've never been able to boot from a no matter what, it just black screens. so, i went back and pulled my vbmeta, and flashed it back over to both slots. i flashed my patched boot to b. maybe i should flash both.. gonna try that next. but once i flashed my vbmeta back over with disable verity and disable verification, i was booting straight into recovery.
i then followed that by wiping userdata and i was able to boot again, this time the normal OOS boot screen followed instead of the carrier boot screen. still no radios though. when i pulled my boot image i stayed in a specific directory, and i haven't been able to download these large archives that have boot files in them because my download speed doesn't exceed 1MB/s at the moment. so i definitely didn't mix anything up.. it's a little mind boggling at the moment because all i did was send that patched boot image over and just that itself, caused the no radios problem.
Did you use your own vbmetas?
Try disabling verity and verification on all vbmetas....
vbmeta.img, vbmeta_system.img and vbmeta_vendor.img. You may or may not need to create a blank. I haven't had to so far but try these. You need each of these images to do it...:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Check this out to explain a little more about the secure boot and how it works.
Secure boot flow | ConnectCore 8X
www.digi.com
Also check out this link for more on creating blank vbmetas https://android.stackexchange.com/q...-and-generation-of-vbmeta-image/224545#224545
PsYk0n4uT said:
Try disabling verity and verification on all vbmetas....
vbmeta.img, vbmeta_system.img and vbmeta_vendor.img. You may or may not need to create a blank. I haven't had to so far but try these. You need each of these images to do it...:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
that was exactly my next step it's funny you mentioned it here. still didn't work, so i dove a little deeper using this really handy tool and deconstructed the vbmeta's into json format. my current a/b vbmeta.img's had a security patch date of july, whereas when i got to my vbmeta_system_b file, i noticed that it had the correct date of august. so i just got done flashing the respective vbmeta over to all slots, and wiped userdata as it seems to require that each go around or else it will boot into recovery.
as oos loads up now i can see that i still have no radios, but this is inconclusive because the last thing i did before this the other day, was wipe both modem1 and modem2 in hopes that they would regenerate themselves possibly. not sure if that's the case so i will flash the backups back over now and report back if this actually helped solve the problem. if not i'm gonna manually edit the vbmeta and repack it if that's possible with/without needing keys in this scenario.
i was going to add the tags
"avb_vbmeta_image_flags_hashtree_disabled" 1,
"avb_vbmeta_image_flags_verification_disabled" 1,
Click to expand...
Click to collapse
prior to realizing that the security patch dates were off, so went with the minor effort first. this will be my next attempt if the the former doesn't work. thanks for the links, those actually helped a lot with understanding what's going on here.
upon trying to pack the vbmeta back together, it spits out an error that it doesn't know what those flags are and fails to compile. so for future reference, that won't work. so i edited just the fingerprint and patch date and flashed it to both slots. it's obvious here that the vbmeta and vbmeta_system are strikingly different, as the og vbmeta retains the keys for all partitions whereas the system one does not.
dmtec said:
just pulled this from my device. haven't patched it yet, but here's a stock august boot image. i used the pre-rooted lineageos rom and pulled the partition into an img file, i see someone just posted a guide in one of the threads without the boot image shared afterwards.. which kind of defeats the purpose for some people that are having a hard time accomplishing that.
edit: i am successfully rooted, but i have no radios. haven't looked into what the solution would be for that yet. i don't think it's been discussed other than that being a thing. share information here if you have any.
edit: link removed because i dissected the boot.img, and it indeed, is not an august boot img
Click to expand...
Click to collapse
and yes i posted a short how to in hopes that others could get an idea of how to root the device. i have posted the boot images for the previous patches but i dont have the time now to even sit and spend on updating so i dont have the boot image to share. do you mind if i link to your post in the other thread?
PsYk0n4uT said:
and yes i posted a short how to in hopes that others could get an idea of how to root the device. i have posted the boot images for the previous patches but i dont have the time now to even sit and spend on updating so i dont have the boot image to share. do you mind if i link to your post in the other thread?
Click to expand...
Click to collapse
my bad for the confusion, it was like right when I posted this someone other than you had posted a guide at the trail end of one of the threads.
you're welcome to share this anywhere, I don't mind. but what happened here is even though I was active in b this whole time, I think the newer boot img resided in a, and I made the mistake of only backing up b. it wasn't until I found the boot image editor tool that I was able to see that it wasn't an august boot image. so therefore I lost it.
im gonna open a second claim on my phone because the first one got stolen before I could get my unlock token, and this is probably just gonna be my development device for now. commandeering my wife's moto 5g stylus isn't gonna fair well for much longer lol.
until I can get an august boot img and vbmeta, this one is just gonna have to sit out for now.
dmtec said:
how to manually pull boot.img
install dsu sideloader, install this GSI
enable developer settings, enable 'rooted debugging'
open up a terminal, and enter an adb shell to your device, and use this command
you will then take the destination it produces and input it into this command below respectively
you will then have a list of all partitions. you will be shown the hardlink where it is pointed to. copy the device path for one of the boot partitions (/dev/block/sd**)
you then return to the storage folder of the phone using
then use dd to copy the partition into a boot.img
pull the boot.img from device, reboot, install magisk, patch the boot.img and then flash it. reboot.
Click to expand...
Click to collapse
when i click on the Gsi link it just starts downloading Lineage 19.1
dmtec said:
my bad for the confusion, it was like right when I posted this someone other than you had posted a guide at the trail end of one of the threads.
you're welcome to share this anywhere, I don't mind. but what happened here is even though I was active in b this whole time, I think the newer boot img resided in a, and I made the mistake of only backing up b. it wasn't until I found the boot image editor tool that I was able to see that it wasn't an august boot image. so therefore I lost it.
im gonna open a second claim on my phone because the first one got stolen before I could get my unlock token, and this is probably just gonna be my development device for now. commandeering my wife's moto 5g stylus isn't gonna fair well for much longer lol.
until I can get an august boot img and vbmeta, this one is just gonna have to sit out for now.
Click to expand...
Click to collapse
I think if you really want to get it going you could probably flash everything to may or July, the required images should be here on this forum.. that should get you to where you can update to August again
ScarletWizard said:
i started over and pulled the boot.img again and it fails to patch
i did dev/block/sde9 which is boot_a
View attachment 5768613
Click to expand...
Click to collapse
Have you tried going back to complete stock and then trying to tpull that boot.img and flashing with magisk? and then once the boot.img is patched and flashed, one thing that to tthis day i forget to do more trhan antyhing is to issue the following command at some piont before rebooting out of fastboot:
fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Or are you having a hard time pulling your boot.img from the jump?/ wshich step is currently tripping you up?
ScarletWizard said:
i pulled the boot img but it fails during patching,
Click to expand...
Click to collapse
So it's failing while you're letting magisk patch it?
ScarletWizard said:
Yes that's what I said
Click to expand...
Click to collapse
so.. so have you n ot tried using a different version of magisk to patch said boot.img?
Look at you go.. right on man.. I'm telling you, some of the most important yet memorable experiences since getting into this **** was when i'd be left out to dsry but would eventually figure out whstever it was that was puzzling me.. looksl ike the same just happened with you. ;-)
ScarletWizard said:
untouched Boot partitions OCTOBER PATCHView attachment 5771677
Click to expand...
Click to collapse
This is the incremental ota and won't do most ppl much good. If u would please use payload dumper and dump the file u will see which partitions the ota updates and those are the partitions someone would have to pull from their updated device and upload in order for everyone to have access to the full. October firmware if you feel like sharing it with us