I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (689036 KB) OKAY [ 17.058s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
lzgmc said:
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
Click to expand...
Click to collapse
Thanks for the blank vbmeta.
I was able to flash that fine; but the phone still doesn't do anything. As I explained, my tinkering with it trying to follow the T-Mobile instructions to reflash partitions, I somehow managed to delete almost everything from the phone. Even doing "fastboot reboot fastboot" *does not get me into fastbootd mode*, just back to the original "dumb" fastboot mode.
Nothing is booting anymore because there's nothing left to boot!
And I can't use the MSM tool because this is not a T-Mobile phone, and the program knows that. It immediately fails saying the target model doesn't match the ROM I'm flashing to it.
Is there a way to override that with the MSM tool? Or am I SOL until OnePlus helps me? I was able to use fastbootd to delete the partitions but then it errored trying to remake them, and I'm left with basically nothing usable.
Possible answer Here
drfsupercenter said:
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Click to expand...
Click to collapse
i have a bricked unlocked phone myself .. having the latest platform-tools is not enough for me to get anything on this phone .. mine is also rebooting on loop as i made the mistake and didn't unlock the OEM
Related
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
PirxRaumpilot said:
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
Click to expand...
Click to collapse
Try fastboot getvar all command.
It should at least give you info about which update channel you're on and probably fingerprint as well. This would hopefully help in finding the right firmware for your device.
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.
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you