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
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.
Dear Community,
I'm trying to root my Ulefone Armor X7 Pro using Magisk and so far I've experienced several issues, starting with unlocking the bootloader.
I hope you can help me somehow.
Here's what I've done and seen so far:
- OEM Unlock enabled and USB Debugging enabled
- Using ADB from latest Google SDK to reboot in FASTBOOT mode
- Now 'fastboot oem unlock' returns FAILED (remote: 'unknown command'). I've tried to wipe cache partition, it doesn't help, I've tried a few workarounds found on this forum with no luck so far...
- I've read that sometimes this command doesn't work so I used 'fastboot flashing unlock' instead --> that one worked
With this done, and stock boot.img, the phone will display an Orange State warning saying that the device can't be trusted. However it will boot anyway (with the stock boot.img).
Also, the OEM Unlock option will be greyed out in developer options after performing this command.
- However, after flashing the boot image that Magisk Manager generated (from the stock boot.img from Ulefone website), the phone goes into a boot loop with a Red State saying that the boot signature is wrong and verified boot should be disabled. (However I don't know how to do this.)
So I flashed back the stock boot.img and could reboot my phone again (at least it is not bricked -- but that was scary).
Now, here are my questions and thoughts:
- Is it normal that 'fastboot oem unlock' won't work? Is it fine to use 'fastboot flashing unlock' instead?
- The boot image generated by Magisk is only 10 MB while the stock one is 32 MB. I've read the thread of issue #2005 Pad Images to Original Size With Zeros on Github and I thought maybe that's why the phone won't boot with the Magisk image. But I don't know exactly what I should do about it. (I'm on Windows.)
- Finally, if the solution is to disable verified boot, how should it be done? Is there anything to do with the 'Preserve AVB 2.0/dm-verity' option in Magisk Manager?
I hope you'll be able to help me and I wish you all the best anyway.
Thank you.
same deal
- It's never been an issue for me if 'fastboot oem unlock' doesn't work. In fact, in my experience (which isn't really that much), it never works. I've always had to use 'fastboot flashing unlock'
- I tried padding the image with zeroes using
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
(on a linux box), but it produces the same bootloop. I've tried this same thing with recovery, no such luck.
- I tried flashing via SP Flash Tools, as well. Both the padded and non-padded magisk_patched.img; neither worked. I updated checksum.ini so that flash tools would accept the scatter file. I've tried formatting the section, as well as the 'write memory' tab. SPFT flashes it just fine, but the bootloop continues.
- I even tried patching and flashing boot-debug.img (because why the hell not?) and again, the loop goes on and on.
- I opened up the preloader....bin file in hex editor and removed all instances of 'verify' and flashed via SPFT. Do not do this. The phone will no longer turn on or anything. Luckily, SPFT flashes before anything else in the phone does anything, so it was recovable.
- I tried sideloading my rom as an 'update' but oddly enough adb won't recognize the phone in sideload.
I haven't tried reflashing the whole phone with magisk_patched.img as my boot. I may attempt this. I'll get back to you if I have any luck.
I plan on using mine as a media device (music, video, camera, etc) that I can bring with me on excursions, because I'm terrified to bring my pixel 4xl.. As such, I don't have a SIM card in mine. I have no idea if this would make any difference, but I'm not receiving the 'red state' status saying that verified boot is the issue. I have tried it with unchecking dm-verify, but maybe this hasn't worked. I'm thinking that it may have something to do with vbmeta*.img files. Like I said, I'll let you know if I have any luck
lunalsmojo said:
Like I said, I'll let you know if I have any luck
Click to expand...
Click to collapse
I'll do the same. Thank you for your feedback!
0
success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
THANK YOU!
lunalsmojo said:
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!
Thank you sooo much! I finally got my brand new x7 pro rooted!
Have to ask
What os is does this refer to, I take it it's android 9?
What size is your bootloader/recovery in stock folder?
What mtk version?
lecrocq said:
... Thank you.
Click to expand...
Click to collapse
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?
phaleg said:
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?
Click to expand...
Click to collapse
I didn't install a custom rom, but I did eventually flash the Vanilla Bless GSI by @eremitein. Magisk still worked with patched boot, runs super smooth, and offers a ton of great customizations.
The stock rom is lackluster; it's the phone itself that has a ton of cool features like the underwater camera. I haven't really checked if all of those features are still usable with the GSI. To be honest, haven't really thought of it. Haven't gotten much of my intended use out of it during coroneumonia times. Sounds like a fun investigation, though. If it doesn't work straight out, I'm sure it can be made to work with a little tinkering.
@Pachacouti sorry for response forever later.... It's Android 10 with a MT6761 (Helio A22)
Hello boys. Thanks for how to root. I have rooted, but i had to reinstall system complete. Now i have root and new system and i have sms issue. Sometimes sms is coming, sometimes no..
Hello,
I'm trying to unlock my bootloader for my new Armor 7X but i'm struggling with the fastboot command.
First, there is two "fastboot" mode with this phone :
- the first when you do an : adb reboot bootloader. There is "=> FASTBOOT mode" in the screen. In this mode I can't detect my phone with "fastboot devices" command...
- the second mode is when you power on the phone with the volume "-"and you select "enter fastboot" in the menu. In this mode the phone is detected by "fastboot devices" ! But, the command "fastboot flashing unlock" always fails.
The error :
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
I've tried severals adb/fastboot tools without any succes. I think it's a driver issue but I'm not sure.
If someone have an idea, I will be greatful !
https://www.getdroidtips.com/unlock-bootloader-ulefone-armor-x6/ but i dont make this command fastboot flashing unlock. On phone you must chose unlock and confirm.
Probleme Solved, Use the NON-EU ROM !
I've find the problem ! It was the EU version of the ROM that blocked fastboot, so use the NON-EU version for that.
I've have succesfully rooted my phone, thank you for this thread !
I don't know exactly what are the differences between the two versions but everything seems to work normally.
Очень интересная тема. Наконец-то дошли руки до рутизации. Чрезвычайно долго описывать свой петь не буду, но скажу одно- знаю способ получения root до перезагрузки. Оранжевое предупреждение навсегда. Я допереведу ваш способ и попроьую сделать так-же. Спасибо!
Thanks for this guide
I got root now, has anyone got TWRP installed? Or another custom recovery
Does anyone have a problem receiving SMS?
Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?
CupidAlaska said:
Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?
Click to expand...
Click to collapse
This is not about Note 8.
lecrocq said:
THANK YOU!
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!
Click to expand...
Click to collapse
I would also like to confirm
lunalsmojo said:
success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
I would also like to confirm that this approached worked for me without issue. Some tips that may prove useful for someone, ensure that you have the correct drivers, adb, fastboot, vcom, and cdc. I had issues using fastboot because I did not have the correct drivers, a day was wasted on this.
I also used the tutorial from hovatek, his blog post is where you will find the vbeta.img, I could not correctly flash my patched magisk without first patching the vbeta.img.
Thanks again.
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.
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.
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.