I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
Thanks for any help.....
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
sille said:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
Click to expand...
Click to collapse
Where do I run this from, recovery mode? Do I need any new files?
Glitchedz said:
Where do I run this from, recovery mode? Do I need any new files?
Click to expand...
Click to collapse
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
sille said:
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
Click to expand...
Click to collapse
Sorry, I'm new to this. Do you mean that just have fastboot open on my phone, and type that command into cmd? And where do I put the vbmeta files? Do you have a link to the vbmeta files? I can't find any.
Really really appreciate any help, would love to save the phone.....
Glitchedz said:
Do you have a link to the vbmeta files? I can't find any.
Click to expand...
Click to collapse
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Princip_Loskuta said:
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Click to expand...
Click to collapse
Your reply is 8 months late, but if he didn't figure it out back then he will know now.
Hey sorry,
I have Pixel 6A.
adb shell ls -l /dev/block/by-name shows me that it has vbmeta_a AND vbmeta_b partition.
Would be this right?
fastboot flash boot_ab magisk_patched-[random_strings].img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87413987
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
ephemunch said:
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
Click to expand...
Click to collapse
That is because, to the best of my knowledge, you no longer need to touch vbmeta in order to root.
Related
All info current as of 05/12/2021I'm editing this original post to update what I've cobbled together from various forums. I do not take credit for any of the below. Nor the responsibility if you brick your phone. So, proceed with caution and at your own risk.
All steps were tested on windows 10. Make sure you follow the steps below, in order. Don't skip steps or ignore errors.
TWRP:
The only TWRP version available is an unofficial version. This version doesn't mount super/system and there's no reason to install it.Rooting your stock ROM:
00. Save the folowing stock ROM files in your adb folder on your computer. If you plan to patch boot.img yourself, save the boot.img on your phone too. Attached is the patched boot.img (magisk 23).
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
boot.img
01. Boot into stock ROM02. Go to settings/About phone. At the bottom, tap on "build number" until developer options are enabled.03. Connect the phone to your ADB installed computer. Ensure that your computer has the latest version of drivers and the latest version of adb.04. On your phone, go to settings/system/advanced/developer options. Enable "OEM Unlocking" and "USB debugging". Authorize device when the prompt shows up on your phone.05. Install Magisk and patch the boot.img from stock ROM. Alternatively, you can use the attached file. The file is required in step 14.06. Execute the below commands from the adb folder using a PowerShell window.07. ./adb reboot recovery. Wait for phone to reboot to recovery.08. factory reset the phone09. ./adb reboot bootloader. Wait for phone to reboot to fastboot.10. ./fastboot flashing unlock. Read disclaimer and press vol+ to confirm that you want the bootloader unlocked. 11. ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img12. ./fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img13. ./fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img14. ./fastboot --disable-verity --disable-verification flash boot magisk_patched_P3_23.img15. ./fastboot reboot16. You are now rooted.
Installing a GSI:
Installing Magisk on any GSI results in a boot loop. If you are already rooted, you can skip to step 12 after getting to fastboot. But I strongly recommend starting from step 01.
01. Download an AB GSI. If it a zip file, extract the img from it. Flashing an A-Only GSI will result in a boot loop. 02. Flash the stock ROM. I used UMIDIGI_Power_3.E_V1.2_202003282206. Keep the stock firmware and SP flash tool folders.03. Boot into the stock rom. In developer settings enable OEM unlock, USB debugging and authorize it from your computer. Don't bother setting up Wi-Fi or installing apps. The phone will be factory reset shortly. 04. Perform the below commands in the latest version of adb.05. ./adb reboot recovery06. Select Factory reset and reset.07. ./adb reboot bootloader (or use the menu option). The screen should show "fastboot mode" at the bottom of the screen in small font.08. ./fastboot flashing unlock. Read phone screen for instructions. You will have to press volume up key to continue to unlock.09. ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (from stock ROM)10. ./fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img (from stock ROM)11. ./fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img (from stock ROM)12. ./fastboot --disable-verity --disable-verification flash boot boot.img (from stock ROM)13. ./fastboot -w14. ./fastboot reboot fastboot (you MUST be at the fastbootd menu now. If not, you will not be able to flash the GSI successfully)15. ./fastboot erase system16. You will need a larger system partition to flash a GSI. There are 2 ways to achieve this16a. ./fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partitionOR16b. ./fastboot resize-logical-partition product 50934476816c. ./fastboot resize-logical-partition system 3089272064resizes product and system partitions. This gives you about 3GB of system partitions. Adjust the numbers as required.17 ./fastboot --disable-verity --disable-verification flash system <GSI file with .img extention>18. Reboot to system.19. Hold your breath and wait to see your GSI's bootscreen.
Other useful info:
The boot.img is already present in the ROM. The below command will recover the boot.img from your phone and save it in your phone's Downloads folder. Execute it from a terminal on your phone and as super user. You will need root.dd if=/dev/block/by-name/boot of=/storage/emulated/0/Download/boot.imgFor retrieving super partition to your device's download folder,dd if=/dev/block/platform/bootdevice/by-name/super of=/storage/emulated/0/Download/super.imgUnpacking and repacking super.img is a bit involved. I've only gotten till step 06 so far.01 You WILL need a linux environment. If you are on windows, you can install a linux distro from the microsoft store.02 Download lpunpack_and_lpmake-masterz.zip. Unzip it to a folder and execute the below commands in the linux shellx86 or x86_64: sudo apt install clang zlib1g-dev ./make.sharm or arm64:sudo apt install clang ./make.sh03 You should see 2 files in the folder - lpmake and lpunpack.04 Copy stock super.img into the folder and in the linux shell, execute ./lpunpack super.img.05 After a few minutes, you will see vendor, product and system images in the folder now.06 Replace system.img with a gsi of your choice. The file name MUST be system.img.07 Repack super.img using ./lpmake. Syntax.08 You should now be able to flash super.img using the SPFlash tool.
I can't find the thanks button anywhere, but ThankS for asking, I ordered this model too. It is a new model still, so i expect it is hardly being worked on, if at all yet. Then there is the time after someone starts to "crack it" so to speak. Stock android 10 on this U-P3, and I only want a soft root, for a few extra functions for some apps lo, maybe a generic supersu setup will work now? At the price (£120-£150 new), for what it offers, I expect someone will root it and share how soon. As a noob i think i'd rather wait and see someone using it rooted before potentially bricking a phone i don't even have yet lol.
(edit. thanks button jus popped up lol)
Problem Sound Umidigi Power 3
I just hope that yours does not win as much as mine ...
Device show ball works very fast without locks extraordinary battery but mine came with sound defect ...
Out of nowhere the device stops emitting sound and only after restarting the device the sound comes back or I noticed that I connect and disconnect several times the headset p2 the audio comes back without restarting, that is, today I got it out of the box for 2 days 09 / 03/2020 in Brazil i bought it on aliexpress and sent a message to the seller about what happened and no answer for now and by the way i must be at a loss because sending the device back to china to get a refund will cost me half the value of the device and I'm going to end up with it like this while I'm looking for a program to help me with this as an example by isolating the P2 audio output to see if for this error ....
NOTE: I took out of the box I already had a software update I let it do and started normal and I noticed the sound defect I restored the device as original from the factory to see if it resolved and nothing helped it went back to being silent from nothing after a rest period without using it the device happens because if you leave playing music it doesn’t stop ...
In short, I do not know what to do waiting for a response from the seller or find a program to solve this ....
And making it clear I loved the device it is very good just sad with that part of the sound.
smvsmv said:
I just got a UMIDIGI Power 3 and have been trying to root it using the Magisk Boot.img patching method. This ends up in a boot loop for me. Flashing the original Boot.img back allows the phone to boot properly.
Anyone have ideas on other safe methods to root? My bootloader is unlocked, but I don't think we have a custom anything for this phone.
Click to expand...
Click to collapse
Did you try this?
1.
make magisk_patched.img by Magisk Manager
2.
get recovery.img & vbmeta.img from stock ROM
3.
boot to fastboot mode
4.
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
(if I remember correctly, at this moment the phone rebooted, you will need to take it to the fastboot again)
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
it works for me.
mankind1019 said:
Did you try this?
1.
make magisk_patched.img by Magisk Manager
2.
get recovery.img & vbmeta.img from stock ROM
3.
boot to fastboot mode
4.
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
(if I remember correctly, at this moment the phone rebooted, you will need to take it to the fastboot again)
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
it works for me.
Click to expand...
Click to collapse
This seriously working? Probably best budget phone if it does
mankind1019 said:
Did you try this?
1.
make magisk_patched.img by Magisk Manager
...
...
it works for me.
Click to expand...
Click to collapse
Can you explain your steps further. Until a month ago I used an old phone with Android 4, which only needed supersu for rooting. So these programms are fairly new to me
Yesterday I tried to root that thing for a whole day without success. Unlocking the bootloader was not a problem but rooting really finished me.
As far as I understand from the Magisk Manager website, I either need to have a rooted phone already to install Magisk Manager, or I need to install Magisk Manager over TWRP, which doesn't exist for the Phone as of right now. Kinda a dead end.
I also wasn't able to extract the boot img with the MTK droid tool. Seems like the last update was 4 years ago and it isn't supported anymore.
@gilbermarcilio
Have you tried to deactivate voice recognition. I've read in a review that a lot of audio problems can be solved if you deactivate the "OK Google" Assistant.
regards tav
With respect to sound issue. I read it is an equaliser problem that needs an update. Quick work around, is to turn on a sound for key presses, it keeps the equaliser running or something.
anon1135 said:
This seriously working? Probably best budget phone if it does
Click to expand...
Click to collapse
yes, it really works.
of course passed SafetyNet & modules works fine!
---------- Post added at 11:31 PM ---------- Previous post was at 10:59 PM ----------
Tavero said:
Can you explain your steps further. Until a month ago I used an old phone with Android 4, which only needed supersu for rooting. So these programms are fairly new to me
Yesterday I tried to root that thing for a whole day without success. Unlocking the bootloader was not a problem but rooting really finished me.
As far as I understand from the Magisk Manager website, I either need to have a rooted phone already to install Magisk Manager, or I need to install Magisk Manager over TWRP, which doesn't exist for the Phone as of right now. Kinda a dead end.
I also wasn't able to extract the boot img with the MTK droid tool. Seems like the last update was 4 years ago and it isn't supported anymore.
@gilbermarcilio
Have you tried to deactivate voice recognition. I've read in a review that a lot of audio problems can be solved if you deactivate the "OK Google" Assistant.
regards tav
Click to expand...
Click to collapse
Magisk Manager apk file exists.
Google it.
you don't need TWRP to install only Magisk Manager.
you can download stock ROM from UMIDIGI community website.
you can find img files in the archive file.
I sent an email on the support on the Umidigi website and they really answered that the problem of disappearing the sound of the device is related to "Ok Google" and I deactivated the function and is working normally without missing the sound and said that they are working on a update to correct this defect.
And thanks to everyone at XDA I will continue to follow what they have for more than the Umidigi Power 3 and I am enjoying the device so far.
mankind1019 said:
yes, it really works.
of course passed SafetyNet & modules works fine!
---------- Post added at 11:31 PM ---------- Previous post was at 10:59 PM ----------
Magisk Manager apk file exists.
Google it.
you don't need TWRP to install only Magisk Manager.
you can download stock ROM from UMIDIGI community website.
you can find img files in the archive file.
Click to expand...
Click to collapse
mankind1019 said:
Magisk Manager apk file exists.
Google it.
you don't need TWRP to install only Magisk Manager.
you can download stock ROM from UMIDIGI community website.
you can find img files in the archive file.
Click to expand...
Click to collapse
Well fu*k ... seems like I've bricked my device.
Installing Magisk manager worked fine and I've modified and flashed the boot.img without problems.
But during flashing the recovery.img it seems like I've touched my usb cable and disconnected the phone from the PC. I didn't think much about it in the beginning and rebooted it...just to be greeted with an endless boot loop. Right now I can't even shut it off. Holding the power button doesn't do anything.
That failed flashing action even seems to have locked my bootloader again. At least I don't see the message: Orange status. your bootloader has been modified.
I tried for the last hour to get somehow into fastboot. No chance.
When I boot into fastboot none of the commands are recognized. I'm using platform-tools_r29.0.6-windows.zip for adb and fastboot. When I boot into fastbootd, fastboot devices works, but none of the other commands. Has anyone succesfully rooted their Power 3? If so how did you do it?
Rooting Power 3
scotty562 said:
When I boot into fastboot none of the commands are recognized. I'm using platform-tools_r29.0.6-windows.zip for adb and fastboot. When I boot into fastbootd, fastboot devices works, but none of the other commands. Has anyone succesfully rooted their Power 3? If so how did you do it?
Click to expand...
Click to collapse
Try the process here.. it worked for me
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-f2-t4030407
The issue is that once I get to step 7 (reboot into bootloader) it goes to the black screen with FASTBOOT mode... in lower left with the usb noise chiming every 10 seconds or so like it's cycling so fastboot never detects the device.
Edit:
Got past the issue. I opened up device manager and android was there looking for drivers. I had it do a search automatically for drivers and that ended up working and fixed fastboot.
Edit 2:
Next issue is I get a bootloop after flashing the patched boot img.
Edit 3:
I must have done something wrong in steps 6-8 because I redid them and now it works!
smvsmv said:
I just got a UMIDIGI Power 3 and have been trying to root it using the Magisk Boot.img patching method. This ends up in a boot loop for me. Flashing the original Boot.img back allows the phone to boot properly.
Anyone have ideas on other safe methods to root? My bootloader is unlocked, but I don't think we have a custom anything for this phone.
Update: I found that the F2 rooting process works on Power 3 as well
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-f2-t4030407
Click to expand...
Click to collapse
If someone can make a youtube video will be a lifesaver. The bluetooth is really unstable on this phone and the audio issues don't help it.
Hello!
I solved the sound problem by disconnecting Ok Google. But I can't find the notification led. Locked screen notifications don't work for me either.
Please help.
Thank you.
Notification LED
Apipote said:
Hello!
I solved the sound problem by disconnecting Ok Google. But I can't find the notification led. Locked screen notifications don't work for me either.
Please help.
Thank you.
Click to expand...
Click to collapse
I don't believe this phone has a notification led light on it.
smvsmv said:
I don't believe this phone has a notification led light on it.
Click to expand...
Click to collapse
Screen notifications don't work either. This device is full of bugs. Software is crap.
Do you have any tips?
Tnx
Tips
Apipote said:
Screen notifications don't work either. This device is full of bugs. Software is crap.
Do you have any tips?
Tnx
Click to expand...
Click to collapse
I don't have any problems with sound or notifications. I do have other issues with the phone. For your issue, check if your apps have notification access. If that fails, try a clean install of the full ROM and as a new device.
https://community.umidigi.com/forum.php?mod=viewthread&tid=19232&extra=page=1
This phone probably is going to be my only UMIDIGI unless something changes in quality.
umidigi power 3 sound problem fix
gilbermarcilio said:
I just hope that yours does not win as much as mine ...
Device show ball works very fast without locks extraordinary battery but mine came with sound defect ...
Out of nowhere the device stops emitting sound and only after restarting the device the sound comes back or I noticed that I connect and disconnect several times the headset p2 the audio comes back without restarting, that is, today I got it out of the box for 2 days 09 / 03/2020 in Brazil i bought it on aliexpress and sent a message to the seller about what happened and no answer for now and by the way i must be at a loss because sending the device back to china to get a refund will cost me half the value of the device and I'm going to end up with it like this while I'm looking for a program to help me with this as an example by isolating the P2 audio output to see if for this error ....
NOTE: I took out of the box I already had a software update I let it do and started normal and I noticed the sound defect I restored the device as original from the factory to see if it resolved and nothing helped it went back to being silent from nothing after a rest period without using it the device happens because if you leave playing music it doesn’t stop ...
In short, I do not know what to do waiting for a response from the seller or find a program to solve this ....
And making it clear I loved the device it is very good just sad with that part of the sound.
Click to expand...
Click to collapse
You need to disable the google quick search box
(com.google.android.googlequicksearchbox)
After you disable that it should work fine
I am drowning here. Supersu and twrp was all i needed in the past.
"use magisk" is not a thing i understand yet. and the other applications too, are all new to me. When i see "patch boot with magisk" i think "****ing - What??"
I need a guide for a 7 year old, because I am 7 years old with 35 years of experience at it.
I need a guide which is a step by step idiot guide, for someone that has never ever used any of the applications involved. Anyone out there fancy writing one please?
I did it. Combination of a youtube video (vulgar, I know) and the umidigi f2 guide here on xda. Youtube guide just to see what was being done. then when i could see how fastboot etc were used, i followed the xda f2 for a successful root. And it's nice to have a phone on orange again lol.
Only want root functions, so never bothered with twrp yet.
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.
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
narayan chetri said:
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
Click to expand...
Click to collapse
RMX2155 or 2MX2151?
OrthodoxOxygen said:
RMX2155 or 2MX2151?
Click to expand...
Click to collapse
RMX 2151 bro
OrthodoxOxygen said:
RMX2155 or 2MX2151?
Click to expand...
Click to collapse
I have the same issue, could you help?
narayan chetri said:
RMX 2151 bro
Click to expand...
Click to collapse
yoboy44 said:
I have the same issue, could you help?
Click to expand...
Click to collapse
Did you make sure that USB debugging was turned on via the developer settings?
Try this guide, maybe:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Lemme know if it works.
Do you use the newest version of adb & fastboot? (older version had problem with the parameter)
Are you sure that verity is not disabled already? (try it without the parameter)
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
HeiloWorid said:
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
Click to expand...
Click to collapse
Didn't work for me
KillSkill said:
Didn't work for me
Click to expand...
Click to collapse
Flashing a blank vbmeta does the trick, don't need of a special command.
narayan chetri said:
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
Click to expand...
Click to collapse
YOU HAVE TO USE FASTBOOT FROM ANDROID PLATFORM TOOLS FOR WINDOWS
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
here's its direct link :
https://dl.google.com/android/repository/platform-tools_r33.0.1-windows.zip
HeiloWorid said:
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
Click to expand...
Click to collapse
Thank you so much. This actually helped me rooting my Oneplus 7 Pro with Magisk instructions. I was using Powershell, but got the error "unknown option -- disable-verity".
It worked in CMD.
Thanks!
snsgn said:
It worked in CMD.
Click to expand...
Click to collapse
I've always had a sneaking distrust of Powerhell and its pedantic error messages.
I presume that these problems are a case of cmd and PS finding different versions of fastboot.
Just run fastboot --version in both to see if they are different.
A separate topic
In Windows and in Linux the default argument handling is based on the C language.
That means that fastboot flash recovery recovery.img gets changed to an array of 4 strings.
There is quoting and escaping and evaluation going on there too.
Windows has the GetCommandLine() which returns the command line as a single string.
This all sounds good, but a program can be executed in code with an array of strings too and the "command line" has to be manufactured after the fact.
This can lead to some complicated differences.
I think it's best to ignore that GetCommandLine() even exists.
Also, I noticed a peculiarity about GetCommandLine().
In cmd fastboot flash recovery recovery.img gets turned into:
C:\Dir\Subdir\fastboot.exe flash recovery recovery.img,
while PS turns it into:
"C:\Dir\Subdir\fastboot.exe" flash recovery recovery.img
Even when there are no spaces in the path.
Undoubtedly this breaks some Windows programs using GCL.
OTOH, adb and fastboot stick to straight C language handling, so this is not that.
hi everyone,
by mistake i didnt reload magisk after ota(RMX2202_11.C.15 GDPR), so i lost my root
now, the situaiton is:
bootloader is working
ive tried to instal twrp but something doesnt wanna work. i guess i installed but the screen is black
then i did manually:
adb.exe shell "twrp install /sbin/Magisk.zip"
Click to expand...
Click to collapse
didnt work.
for 2nd solution i tried
with my rom's vbmeta.img, vbmeta_system.img, vbmeta_vendor.img basicly
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
didnt work either. and now when i try to open the phone, close itself and not always im able to open. now i can use just bootloader which is difficult to reach (need to press 3 buttons)
right now im waiting to finish unroot file.
well, (how) can i boot and root my phone without losing data?
Wow I'm in pretty much the exact same situation just made a thread lol
idk how but after some hours suddenly i saw that it started to work.
i think i changed the slot (like a>b) and flashed .img files on fastboot. at least now it works
Here is a copy of July modems and vbmetas in case anyone needs to reflash their modems due to mismatching May & July patches. Should work for July patched system with May bootloader or some other combo with the july system.
VBMeta should work for any
JULYmodemsbackupN20.zip
drive.google.com
**Note*** please backup your vbmetas before flashing the vbmetas in this archive. According to iKlover these did not work for his July device and had thankfully backed up his own first. I have not had much time to spend on this device lately and likely won't for a while. I was rushing to get this up for anyone in need and may have gotten them mixed up. If anyone can confirm these vbmetas are not July or for a specific device I would greatly appreciate the time and effort***
Also as a side note you can probably just flash your own vbmetas with the disable switches so please be mindful
You're a ****ing saint! Dorothy Mantooth is a saint!
PsYk0n4uT said:
Here is a copy of July modems and vbmetas in case anyone needs to reflash their modems due to mismatching May & July patches. Should work for July patched system with May bootloader or some other combo with the july system.
VBMeta should work for any
JULYmodemsbackupN20.zip
drive.google.com
Click to expand...
Click to collapse
I flashed vbmeta using this command: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
on my July device, and I'm stuck in a bootloop. It boots to recovery only. Any idea how to fix this?
Do you have a backup of stock boot and vbmeta you can restore?
DrScrad said:
Do you have a backup of stock boot and vbmeta you can restore?
Click to expand...
Click to collapse
Yeah, I reflashed and got out of the loop. Thanks for reminding me I made a backup, I didn't remember
iKlover said:
Yeah, I reflashed and got out of the loop. Thanks for reminding me I made a backup, I didn't remember
Click to expand...
Click to collapse
You may be able to flash a blank vbmeta as on other devices. Sorry this happened. I have Soo many backups and was in a rush to get everything backed up on my PC. I can only think that maybe I got the patch dates wrong on these. I will make note..
Also my July device is a sort of Frankenstein at this point and I haven't yet identified the culprit. You should have your carrier boot animation when powering up the phone if everything matches. Mine does not. Just the OnePlus boot animation, circle with the revolving circle/s ..
But everything is working perfectly other than that and the boot animation doesn't bother me so I haven't had the motivation to even look into it yet. I doubt I will even be able to for a while.
iKlover said:
I flashed vbmeta using this command: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
on my July device, and I'm stuck in a bootloop. It boots to recovery only. Any idea how to fix this?
Click to expand...
Click to collapse
Not sure if any of these need flashing as well but if someone wants to back theirs up first and try these maybe it could be of value. Has worked on other manufacturers but I haven't tested on this one nor this device. But:
fastboot flash --disable-verification --disable-verity vbmeta vbmeta.img
Then run fastboot flash --disable-verification --disable-verity vbmeta_system vbmeta.img
Also run fastboot flash --disable-verification --disable-verity vbmeta_vendor vbmeta.img
Or replace vbmeta.img in those last two with the corresponding vbmeta_vendor or vbmeta_system images. You can rename the .bins to .img and flash them if I didn't already rename them in the archive.
If anyone has the time to check this out please do so and post results and/or info if you know whether or not this is necessary or even helpful/possible with this device. I don't want to encourage anything that would cause any issues but if it doesn't work you should just be able to reflash your backups
PsYk0n4uT said:
You may be able to flash a blank vbmeta as on other devices. Sorry this happened. I have Soo many backups and was in a rush to get everything backed up on my PC. I can only think that maybe I got the patch dates wrong on these. I will make note..
Also my July device is a sort of Frankenstein at this point and I haven't yet identified the culprit. You should have your carrier boot animation when powering up the phone if everything matches. Mine does not. Just the OnePlus boot animation, circle with the revolving circle/s ..
But everything is working perfectly other than that and the boot animation doesn't bother me so I haven't had the motivation to even look into it yet. I doubt I will even be able to for a while.
Click to expand...
Click to collapse
These things happen man, no worries. For anyone reading, it's best to back up as soon as you obtain root in case you make a mistake. I prefer Partitions Backup and Restore like the other poster said.