Phone is a Moto G7 1962-1 (river), unlocked and rooted with Magisk 20.0. TWRP 3.3.1-0 is installed.
Everything was fine for several months, but I temporarily uninstalled Magisk, and something apparently went wrong and I was unable to use mobile data. The mobile connection fluctuates on and off, every ~10 seconds or so.
Someone suggested doing a fastboot erase modemst1 and fastboot erase modemst2, and sure enough, that works - until I reboot. Then it has to be done again.
I tried going back to unrooted stock, and even relocked the bootloader - mobile data will work until I reboot once, then it remains dead until I issue those two erase commands, and it will work for one boot.
I have not tried erasing fsg and am afraid to without hearing from someone.
The phone is usable, given that it doesn't require rebooting often, but it is a frustrating to worry about. Does anyone know a more permanent solution? I could maybe write a script that would do the erase on reboot, but that would be more of a workaround than a fix.
Any thoughts would be gratefully welcomed.
Here to confirm this strange problem on my moto g7 also.
The fastboot erase modemst1 and fastboot erase modemst2 does fix the problem until reboot.
Need help in writing and installing a script to perform these functions that will run when the phone boots.
I thought about doing that, and will try, but only as a last resort. It seems like it would be patching the symptom rather than fixing the problem.
But yeah, it beats having to tether to a PC every time it needs a reboot.
Hi kenerly,
Try this:
Open your terminal and do
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
then reboot. I betcha the problem is resolved...
Some kind folks on the Telegram group were on the ball about it, and there was a recent thread here in the G6 area about it also. Apparently it is related to a bug in TWRP.
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t39948270
Thanks bro, seems to of fixed the problem.
Related
Hi,
I seem to be bricked more than usual. Don't ask me how, I was doing something, rebooted and now I can't get into early usb mode or android recovery. I have no clue what half the other boot options are.
I can use rsd lite to flash sbfs, no problem. Phone is stuck at initial m, no animation. I suspect it is something dumb like the internal memory having an error, something is causing the linux bit to loop. Not reboot, not crash, just hang there.
i can use fastboot, but since it uses names for partitions, I don't know how to flash exact partitions or know what they all are, I have system, webtop, boot, recovery, cdrom, other things like pds are not allowed.
I have a dev usb cable made up, can do everything without a battery, which is cool, have an extra battery and external battery charger. Obviously, I have all the partitions available as backups.
Somehow, I need to get the partitions restored, and internal memory formatted perhaps.
Any ideas? Short of trying to send it back?
Thanks.
for my little experience a full wiped pds let you run the os...and you know better than me which are the others partitions not overwritten by a flash with full sbf
I had a backup of my pds, but no way to flash it or erase it.
Thanks!
in milestone i was having your problem when changing builds (froyo,ginger, eclair) via update.zip without the correct boot.img
but if you already flashed the sbf...
have you tried flashing boot and recovery partition, and then entering it? maybe you regain adb access
I think I am getting blocked before I even get to recovery, early usb, android recovery, etc.
I have fastboot access and nvflash, so in other words I have fastboot.
I can flash boot, recovery, system, webtop, cdt, cdrom, preinstall, but not pds, and I can't erase boot etc.
Thanks.
...i searched for nvram in android:
maybe it's useful (from droid incredible dev area)
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
hope it helps somehow
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
NFHimself said:
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
Click to expand...
Click to collapse
i did not say that file was for you.
but if you can flash boot recovery system and your system won't boot it's something else in the bootstrap process (excluding hardware failures, you could not access fastboot then).
as i read you can flash (already flashed?) almost every partition except pds (useless for your needs) and nv.
i reported a case of other guys experiencing your same problem, with i guess the same cause.
i give you an idea, unfortunately i'm not a dev to give you solution
cheers
So i became a hacker (Obvoiusly) and ive had some issues but i always find a way to fix them and im glad i became a hacker ! <3 but alas i have problems once more :'/. See i was using cm7 BATF2 Or something along those lines, and ive had multiple problems but kept it due to lazyness of backing up and restoring my phone. but now it seems my phone keeps bootlooping unless i flash a new rom, so i flashed cm9 0.3.1. Sure i lost everything but i need a phone and quickly </3 :/.
But there seems to be a problem.....
Whenever i try to use cwm recovery (Button only 5.0.2.8 i believe) i cant factory restore because it cant reach a certain part of android (If im right its android secure.) and skips the format.
So i have literally no space on my phone.
Can someone help me with this and maybe some other issues??
Thanks in advance
-heyhey24 <3
This may work for you:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Okay, so I was trying to unlock my bootloader. Completed ALL the steps up to were I had to flash Radio.zip to get my signal back. Stupid me accidently hit to install the rom I had choosen to install after unlocking my bootloader. I didn't notice untilit was already installing. So it rebooted and I just get the non animated LG logo and it says security error under it. I am able to get to the s/w upgrade screen by holding volume up and plugging usb in. I searched Everywhere and can't solve the issue. I tried re-flashing my kdz file and it only goes to 15% then says my phone is not connected, tried reinstalling the drivers and got the same message. Then I proceeded to the online method. While doing this it found my phone and proceeded to the second part where it begins downloading. It went to 13 seconds time lapsed the stopped. No bar moving across and no more counting with the time lapse. I had read were it froze on others and they let it proceed and it did its thing. So I left it for about 4 hours and nothing changed. I then checked my traffic meter on my router and nothing had even began downloading. I reinstalled and tried again. It would go threw the checking for other software part fine then when it gets to the downloading part its at the 13 second time lapse freeze again. This time it didnt count up to it. It was just instantly where I had left off. I then went to my brothers and tried to his computer. Completely reinstalled it and it did the same thing! Didnt even count up to 13 seconds was just instantly there! I then read where someone had the same issues as me and installed fastboot and flashed xloader and uboot and then the offline method reconized them. Im thinking this is my key to fixing, however when i install the driver as instructed it says install failed because lack of electronic signature. So im lost and ran out of search methods to try. Has anyone else had this issue when installing fastboot? Also I was a little confused on which fastboot file to use so I tried a few and all had the same result. Does someone have a link to the one I need or any other advice? This stinks I just bought this phone but the stock rom was driving me crazy because im use to custom! Thanks so much and please help!!!
SOLVED! flashed ics xloader and uboot and it finally found my phone on the offline method. Now I just have the wonky TS to solve. Should be fun since I lost root and cwm. I was able to get show touches and usb debugging on so that makes lofe easier. You guys have no idea how relieved I feel! I thought I pretty much threw 200 bucks away!
Okay little update. I got fastboot loaded on my phone and flashed a recovery.img but still not having any luck. Both programs are doing the same exact thing as before. I feel like im getting there since I now have fastboot. What other options do I have that I can try?
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay I got it all up and running. However when I used your commands none of them would respond and do anything except flashing the ICS u and x. Once I did this I was able to get the offline method to work. I then rooted and installed Cwm to run the ts fix because I had the wonky touchscreen. I then flashed kumas rom . I forgot to use CWM to clear my cache and such before flashing to kumas ROM. Will this effect anything? Should I go to cwn and delete it all and reflash kumas ROM? Thanks!
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
SlideShowPl said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
Click to expand...
Click to collapse
So the only this you can access is sw upgrade mode? what lead up to this? did you install fastboot drivers twice?
Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Pazzl said:
Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
Click to expand...
Click to collapse
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Saratoga79 said:
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Click to expand...
Click to collapse
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
lfom said:
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Click to expand...
Click to collapse
Hello,
well, it didn't. either full install, either unbrick
Pazzl said:
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
Click to expand...
Click to collapse
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Saratoga79 said:
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Click to expand...
Click to collapse
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Pazzl said:
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Click to expand...
Click to collapse
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
lfom said:
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
Click to expand...
Click to collapse
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Pazzl said:
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Click to expand...
Click to collapse
Hello, any update on this? I have the exact same situation you have. Stratos became sluggish, but when factory reset it works back fine, after few days/months its sluggish again until it stucks in amazfit logo only, everything is stock on this point as well as boot loader is locked, I managed to unlock my bootloader via fastboot. Tried most of the unbrick thread here but haven't managed to make it work. Tried stratosfied and it went to recovery where it is updating firmware but stuck at the end. Exactly same situation with you. Hoping I could get information in here, thanks
Edit: Was able to fix it following this -> https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Somehow custom rom, newer stock firmware doesnt work but old 1.3.0n in the thread works yaay!
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.