Related
hi guys, there is several posts for upgrade to the newer firmware, but is there any guide to downgrade? I'm running L29C636b138 and it's draining my battery quickly. I was using 136 and it was super! and for now i can't upgrade to the 158 yet since it's not authorized yet.
I guess you will just have to wait on that 158 update. It will come soon enough. I've been experiencing the same updating from 126 to 138 on my eu phone. The standby drain is worse than the 126 fw. Battery is still good for me tho with 9hrs sot over 2 days off charger. Just that 126 was better.
Hi guys, I was using L29b636b158. I decided to flash to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]". Some how I didn't like, I used TWRP to restore my backup. and Now the camera is not working at all. It shows an android icon. nothing happens (it tries to open but crash right away). I've tried to Format Data in TWRP. I didn't work. I tried to install "hw_data.zip". I didn't work. I tried to flash back to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]" camera still not working.
Can some one help please??
aznboix said:
Hi guys, I was using L29b636b158. I decided to flash to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]". Some how I didn't like, I used TWRP to restore my backup. and Now the camera is not working at all. It shows an android icon. nothing happens (it tries to open but crash right away). I've tried to Format Data in TWRP. I didn't work. I tried to install "hw_data.zip". I didn't work. I tried to flash back to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]" camera still not working.
Can some one help please??
Click to expand...
Click to collapse
Did you restore your boot image?
If you didn't back it up:
Download firmware from http://hwmt.ru/hwmtsite/firmware-database
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Unzip update.zip
Open update.app in update extractor
Right click on boot and Extract.
Flash boot using twrp.
Note: this will encrypt your /data if you boot without applying SuperRoot or SuperSU.
ante0 said:
Did you restore your boot image?
If you didn't back it up:
Download firmware from http://hwmt.ru/hwmtsite/firmware-database
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Unzip update.zip
Open update.app in update extractor
Right click on boot and Extract.
Flash boot using twrp.
Note: this will encrypt your /data if you boot without applying SuperRoot or SuperSU.
Click to expand...
Click to collapse
1) which option do i choose when it prompts "boot" or "recovery" when I flash using twrp
2) Do I have to flash "superoot soverinity" again? after flashed the stock boot img?
aznboix said:
1) which option do i choose when it prompts "boot" or "recovery" when I flash using twrp
2) Do I have to flash "superoot soverinity" again? after flashed the stock boot img?
Click to expand...
Click to collapse
1. Boot
2. Yes.
Before you do, can you go to Install click Select Storage - internal, and check that /data is not encrypted again. You should see regularly named folders, not random letters/numbers. If you can mount data that is.
If it is encrypted you will bootloop if you try to boot with a decrypted boot image.
So I installed the boot.img from stock (158). Nothing changed..My phone works super well. Camera still not working ;(
u can try to find your boot here as well
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.
hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock
Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.
Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?
Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI
Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
When i try to install zip package with weekly miui12 (unnoficial TWRP) i forgot to mount partitions and now i can't mount it anymore. Try to tick it but nothing happened.
So I can't install any package. Do I brick my device?
Is there any posibbility to mount those partitions?
Twrp errors:
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/odm' (invalid argument)
Are you trying to install Chinese weekly rom?
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
ZeroSherd said:
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
Click to expand...
Click to collapse
I jist flash fastboot rom twice and everything is ok xD
Is there a solution this error? I'm having the same problem.
I have the same problem. Can anybody help?
edit file rom, extract rom .zip, edit updater-script and delete first line. save and make file zip again.
tested rom global stable beta.
how edit updater-script,
https://forum.xda-developers.com/showthread.php?t=2522762
do my tutorial to get the phone and then start again, it's in Spanish but it's simple.
https://www.htcmania.com/showthread.php?t=1565656
you have to install the recovery "TWRP-3.4.2B-0623-REDMI_K30PRO-CN-wzsx150-fastboot.zip" and with that you will not have errors, the twrp of this website gives errors
i have the same problem How i can flash miui china beta on F2 Pro from twrp?
Koziol87 said:
I jist flash fastboot rom twice and everything is ok xD
Click to expand...
Click to collapse
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Latin_lion_ said:
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Click to expand...
Click to collapse
Did you use miflash?
NOSS8 said:
Did you use miflash?
Click to expand...
Click to collapse
yh BUT for some strange reason i cant flash the latest stock rom on my device arb error ive tried everything hoping to find help im new to this first phone ive tried to install custom roms on
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
cxm05 said:
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
NOSS8 said:
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
Click to expand...
Click to collapse
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
cxm05 said:
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
Click to expand...
Click to collapse
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
NOSS8 said:
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
Click to expand...
Click to collapse
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
in flash folder of rom, you have flashall.bat open it in txt format, find two rows that contain CRC and delete it, save file and than try to flash rom again. it will pass. I have the same CRC error and deleting this two row help me to flash rom
NOSS8 said:
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
Click to expand...
Click to collapse
The MI Assistant version is 3.2.522.32 beta. Once I start the Mi Assisant client on my phone and then plug my cable, the application prompts me to select a Fastboot ROM on my harddrive. ONce I select a valid imag, it flashes my phone and then reboots. After loading for 15 minutes or so, the phone reboots to the MI recovery where I can select to use Mi Assistant again.
This time, Mi Assistant detects the version of ROM I have installed and advises there is a newer ROM. On this screen I select the first button (which I believe downloads the image from MI server) or the sencond button (which allows me to select a local Recovery ROM stored on my hard drive).
Regardless of which option I choose, the 2nd flash occurs and my phone reboots again. in A cycle until I have the most recent ROM on the phone and it still sits at the MIUI boot screen for 30 minutes. I've gone from 11.2.0.9 ==> 12.2.0.4 ==> 12.2.2.4. All successfully flash to the phone but phone never boots past the MIUI logo.
I've even gone as far as flashing a beta ROM 12.2.2.5 on top of the latet stable version using MI Assistant (flash runs successfully ut phone still never boots).
I have also gone into bootloader mode & flashed the TWRP version you recommended. After botting into this recovery, I can "factory reset" the phone and the sideload the HK 12.2.0.3 rom you provided. The sideload flashes to the phone with no errors, but phone still doesn't boot past the MIUI logo
In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
I heard that orangefox has issues with custom rom. Use Original twrp for custom roms. Hot boot twrp and flash . No need to wipe cache or data before flahsing. But after flash format data.
notathinker said:
In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
Click to expand...
Click to collapse
I found a copy of OrangeFox that worked for me available here.
OrangeFox-R11.1-Stable-Unofficial-lime.zip
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The key was to first flash xiaomi.eu_multi_HMNote94G_HM9T_V12.5.6.0.RJQCNXM_v12-11.zip
reboot the phone and let it fully start (I think this updated the partition tables or something)
Then go back into OrangeFox and flash crDroidAndroid-11.0-20220121-juice-v7.14.zip
By doing this I was able to get the phone to boot into crDroid whilst using OrangeFox without any bootloops or partition size errors like the one I was initially getting "assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))"
I think the important step is to let it fully boot after putting on the xiaomi.eu ROM as it must resize partitions or something...
I am having the same problem. I tried to restore an orangefox backup and i ticked the "super" box. After that when i try to flash a rom proccess fails with the exact same message (assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))). I have flashed three different recoveries (pitchblack, orangefox, lineageos) and tried from every each of them flashing a rom both from the recovery and sideloading. The roms i have tried are: crdroid A12, arrowos A11 & A12, lineageos microg and at last the stock miui for my device. Nothing worked so far. Please if someone has any knowledge or ideas help because i am starting to believe it is irreversible...
Device: Redmi note 9s (curtana)
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
HomoImpudens said:
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
Click to expand...
Click to collapse
Yeah, after flashing it with miflash tool your phone runs fine with miui. Were you able to install a custom rom after this? If yes, could you tell what steps did you follow.
If I remember correctly, after that I followed the standard procedure first to flash a custom recovery and then through that a custom rom. Downloaded SDK tools (if I remember the name correctly), opened smartphone on fastboot mode, opened terminal window fom inside SDK tools folder, downloaded a custom recovery, placed it inside SDK folder, rename it "recovery", typed on terminal window: "fastboot flash recovery recovery.img" (again if I remember correctly) and then reboot to recovery. From there install any custom Rom you want.
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
GiGilGilang said:
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
Click to expand...
Click to collapse
Thank you so much. I'm so lucky that I stumbled into your comment, you saved my device!!