Related
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
Hi all,
Last week i received my new MI A1. IT worked perfectly during 3 days, with 2 OTA updates to Android 8. (December and January OTA i remember)
Then, one night my MI A1 just shutdown itself without doing anything (i was sleeping)
And in the morning i tryed to reboot it but i had everytime a freeze and reboot when it asked to enter my PIN CODE. (i tryed without my SIM it was the same, big freeze and reboot)
Si i went to the MI website (xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/) to download the XiaoMiFlash Tools and the ROM (Android 8.0.0 Oreo (OPR1.170623.026.8.1.10) | Fastboot)
It worked to flash the MI A1 but i cannot start the phone, i had the Screen ENCRYPTION UNSUCCESFULL
When i clicked to Resert the phone, it reboot and came to the same screen. (I can host a video if ou want to see)
I've tryed to use FASTBOOT Unlock / TWRP 3.1 to wipe the system but still the same.
Do you have any idea please ?
Thank you in advance for your help
Mathieu
mdesmettre said:
Hi all,
Last week i received my new MI A1. IT worked perfectly during 3 days, with 2 OTA updates to Android 8. (December and January OTA i remember)
Then, one night my MI A1 just shutdown itself without doing anything (i was sleeping)
And in the morning i tryed to reboot it but i had everytime a freeze and reboot when it asked to enter my PIN CODE. (i tryed without my SIM it was the same, big freeze and reboot)
Si i went to the MI website (xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/) to download the XiaoMiFlash Tools and the ROM (Android 8.0.0 Oreo (OPR1.170623.026.8.1.10) | Fastboot)
It worked to flash the MI A1 but i cannot start the phone, i had the Screen ENCRYPTION UNSUCCESFULL
When i clicked to Resert the phone, it reboot and came to the same screen. (I can host a video if ou want to see)
I've tryed to use FASTBOOT Unlock / TWRP 3.1 to wipe the system but still the same.
Do you have any idea please ?
Thank you in advance for your help
Mathieu
Click to expand...
Click to collapse
How did you flash the stock rom?
What option did you choose? Wipe all and lock? Or?
Hi
I tried with full flash And full flash with lock
mdesmettre said:
Hi
I tried with full flash And full flash with lock
Click to expand...
Click to collapse
Can you try with a different firmware? Android Nougat?
Hi,
I've tested with Nougat (tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794) as flash and lock.
and that doesn't work. Still in like a bootloop.
i've tried also to go through twrp 3.2.1 but a a little bit lost.
Which FULL ROM do i need to take as ZIP file in TWRP ?
Also, do i need a SD CARD to completly reinstall Android ?
thanks in advance.
mdesmettre said:
Hi,
I've tested with Nougat (tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794) as flash and lock.
and that doesn't work. Still in like a bootloop.
i've tried also to go through twrp 3.2.1 but a a little bit lost.
Which FULL ROM do i need to take as ZIP file in TWRP ?
Also, do i need a SD CARD to completly reinstall Android ?
thanks in advance.
Click to expand...
Click to collapse
Can you repeat your question about twrp?
You can try to flash lineage os 15.1 with latest twrp-oreo and see if that works.
varben said:
Can you repeat your question about twrp?
You can try to flash lineage os 15.1 with latest twrp-oreo and see if that works.
Click to expand...
Click to collapse
And do i need a MICROSD CARD to flash lineage ?
mdesmettre said:
And do i need a MICROSD CARD to flash lineage ?
Click to expand...
Click to collapse
Nope. Lineage ROM can be stored in internal storage and flashed. Also, if you aren't able to solve the encryption issue, I suggest you to go to your nearest service center and get help. They do it for free, even if you're rooted or modified the system.
guy_infinity said:
Nope. Lineage ROM can be stored in internal storage and flashed. Also, if you aren't able to solve the encryption issue, I suggest you to go to your nearest service center and get help. They do it for free, even if you're rooted or modified the system.
Click to expand...
Click to collapse
Thanks for the answer.
I cannot go to service center because i'm in France.
I've tryed to flash Lineage15.1 but doesnt work.
May be an idea, i've seen in TWRP that i don't have a cache partition. Is that normal ? If not, how do i create it ?
Flash your device from edl mode
If doesnt work it seems that your emmc is faulty
Many huawei phones with faulty emmc shows such this encryption failed message and by changing emmc become functional
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were “_Flash_lock.bat”, “_Flash_.bat”, “_Flash_erase_userdata_lock.bat” and “_Flash_erase_userdata_lock.bat” files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
what about deleting those underscores before each word, i think they shouldn't be there.
kuartito said:
what about deleting those underscores before each word, i think they shouldn't be there.
Click to expand...
Click to collapse
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.
finxminx said:
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.
Click to expand...
Click to collapse
i'm by no means an expert and my advice has no value at all, but i don't see why you wouldn't give flashing from fastboot a try.
1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.
What directory did you select in miflash?
JakobSWE said:
1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.
Click to expand...
Click to collapse
I downloaded 3 copies of 10.0.3.0 firmware from different places and each one claimed those firmwares were for fastboot, not twrp. I attached the folder's screenshot.
henk_j said:
What directory did you select in miflash?
Click to expand...
Click to collapse
I attached the screenshot of the directory.
finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
flash this official pie rom
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
...
Stuck in Loading Screen after Update Magisk
I have the same problem here,, This morning i got nontification from Magisk to update to the new version,, and update done, Magisk start reboot,,, when reboot,, i always stuck on Loading Screen. I check from TWRP my Internal Storage cannot detect by Pc,, So i think i cannot doing Flashing by TWRP,, I'm wipe out all data to clear this mess,, so i start to do a flashing with MIFlash, i'm download the custom rom and start flashing.. and i got this message "cannot found file flash_all_lock.bat"
Sorry for my Bad english.. cus i'm still young
I tried many time to flash my mi A1 phone. In flashing, phone gonna automatically switched off and then open. But no sim being support here. I mean, the phone can not take flash fully. As opposite, Custom rom installed perfectly, but their have also same network issue. Anyone can help me to solve the problem?
Check if your IMEI is ok dialing *#06#
ccalixtro said:
Check if your IMEI is ok dialing *#06#
Click to expand...
Click to collapse
I checked out that. Thats okay
akibafnan said:
I checked out that. Thats okay
Click to expand...
Click to collapse
Maybe you need to flash the rom in edl mode with miflash.
May be you must restore efs with twpr recovery!
And then install the stock.... If you haven't to install it with mi flash..... Install it with twpr flashable zips......
And then every thing will work perfectly
It was the same problem to me and i solved it
reply
usama20E said:
May be you must restore efs with twpr recovery!
And then install the stock.... If you haven't to install it with mi flash..... Install it with twpr flashable zips......
And then every thing will work perfectly
It was the same problem to me and i solved it
Click to expand...
Click to collapse
I flashed phone with mi flash, But flash didn't done fully. In flashing, phone gonna switched off, but in "mi flash" still showing loading.
First thing first....
Download this
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Downloed the twpr file(thia file is the Resolve)
boot to twpr and restore efs
And then install the stock twpr flashable it should Succeed
Boot to system and all things will start normal and the you will restore the sim signal! :good:
And then you have to flash the stock whith mi flash!
All things will be normal As nothing Happened
I solved the same problem with thim method
usama20E said:
First thing first....
Download this
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Downloed the twpr file(thia file is the Resolve)
boot to twpr and restore efs
And then install the stock twpr flashable it should Succeed
Boot to system and all things will start normal and the you will restore the sim signal! :good:
And then you have to flash the stock whith mi flash!
All things will be normal As nothing Happened
I solved the same problem with thim method
Click to expand...
Click to collapse
Thanks man, Its working.
akibafnan said:
Thanks man, Its working.
Click to expand...
Click to collapse
Hi,
I too lost all the signals when i upgraded to pie.
I have also downgraded and followed all the Steps shown in the link, but still i had no signal.
I even upgraded to pie again hoping that i will get signal, but still i had no signal. Can you please explain me the steps in detail so that i get my signal back.
Note: I tried my sims in other mia1 on pie and they are working. I also tried other working sims on my mia1, but no signal.
Kindly help at the earliest. I am without a phone for the last one week.
My understanding is as follows: ( I am on STOCK PIE with NO SIGNAL)
Follow Steps 1 to 7 as it is in the link.
Step 8. Go to RESTORE, choose BACKUP , restore EFS and swipe. (No need to restore BOOT.img)
ADDITION: Step 8a. Go back and Install TWRP Flashable zip of Oreo 8.1 November Update (V9.6.8.0.ODHMIFE)
Step 9. Now in TWRP, go to REBOOT and Click SYSTEM. (No need to click BOOTLOADER here)
I will have November Update 8.1 installed on my phone.
Now, which ROM should i flash through MIFLASH after all this (November 8.1 once again or Pie January update) to restore mobile signal?
Please reply.
Str!der said:
Hi,
I too lost all the signals when i upgraded to pie.
I have also downgraded and followed all the Steps shown in the link, but still i had no signal.
I even upgraded to pie again hoping that i will get signal, but still i had no signal. Can you please explain me the steps in detail so that i get my signal back.
Note: I tried my sims in other mia1 on pie and they are working. I also tried other working sims on my mia1, but no signal.
Kindly help at the earliest. I am without a phone for the last one week.
My understanding is as follows: ( I am on STOCK PIE with NO SIGNAL)
Follow Steps 1 to 7 as it is in the link.
Step 8. Go to RESTORE, choose BACKUP , restore EFS and swipe. (No need to restore BOOT.img)
ADDITION: Step 8a. Go back and Install TWRP Flashable zip of Oreo 8.1 November Update (V9.6.8.0.ODHMIFE)
Step 9. Now in TWRP, go to REBOOT and Click SYSTEM. (No need to click BOOTLOADER here)
I will have November Update 8.1 installed on my phone.
Now, which ROM should i flash through MIFLASH after all this (November 8.1 once again or Pie January update) to restore mobile signal?
Please reply.
Click to expand...
Click to collapse
My problem have been solved. thanks man.
akibafnan said:
My problem have been solved. thanks man.
Click to expand...
Click to collapse
I am asking for your help in solving my problem with network signal.
Please explain the steps.
Any 8.1 stock rom!
And then if you wnat to flash a custom!Treate the phone as normal
Str!der said:
Hi,
I too lost all the signals when i upgraded to pie.
I have also downgraded and followed all the Steps shown in the link, but still i had no signal.
I even upgraded to pie again hoping that i will get signal, but still i had no signal. Can you please explain me the steps in detail so that i get my signal back.
Note: I tried my sims in other mia1 on pie and they are working. I also tried other working sims on my mia1, but no signal.
Kindly help at the earliest. I am without a phone for the last one week.
My understanding is as follows: ( I am on STOCK PIE with NO SIGNAL)
Follow Steps 1 to 7 as it is in the link.
Step 8. Go to RESTORE, choose BACKUP , restore EFS and swipe. (No need to restore BOOT.img)
ADDITION: Step 8a. Go back and Install TWRP Flashable zip of Oreo 8.1 November Update (V9.6.8.0.ODHMIFE)
Step 9. Now in TWRP, go to REBOOT and Click SYSTEM. (No need to click BOOTLOADER here)
I will have November Update 8.1 installed on my phone.
Now, which ROM should i flash through MIFLASH after all this (November 8.1 once again or Pie January update) to restore mobile signal?
Please reply.
Click to expand...
Click to collapse
follow these steps,
First thing first....
Download this
https://forum.xda-developers.com/mi-...-imei-t3879624
Downloed the twpr file(thia file is the Resolve)
boot to twpr and restore efs
And then install the stock twpr flashable it should Succeed
Boot to system and all things will start normal and the you will restore the sim signal!
And then you have to flash the stock whith mi flash!
All things will be normal As nothing Happened
I solved the same problem with thim method
Str!der said:
I am asking for your help in solving my problem with network signal.
Please explain the steps.
Click to expand...
Click to collapse
follow these step,
First thing first....
Download this
https://forum.xda-developers.com/mi-...-imei-t3879624
Downloed the twpr file(thia file is the Resolve)
boot to twpr and restore efs
And then install the stock twpr flashable it should Succeed
Boot to system and all things will start normal and the you will restore the sim signal!
And then you have to flash the stock whith mi flash!
All things will be normal As nothing Happened
I solved the same problem with thim method
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well