Related
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
t-shock said:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
Click to expand...
Click to collapse
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Pretoriano80 said:
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Click to expand...
Click to collapse
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
t-shock said:
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
Click to expand...
Click to collapse
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
ante0 said:
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
Click to expand...
Click to collapse
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
t-shock said:
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
Click to expand...
Click to collapse
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
ante0 said:
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
Click to expand...
Click to collapse
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
t-shock said:
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
Click to expand...
Click to collapse
It shouldn't. And it works again with root. Apparently something broke in SEPolicy, but mankindtw fixed it in his pre-rooted ramdisk. Though, we can install Magisk "normally" now (as a package through recovery) so it shouldn't be a problem anyway SuperSU should install in a similar way too, if one would take the time to make it. I prefer Magisk though
I have currently TWRP installed and firmware COL-L29 8.1.0.131 (C432).
Since two days now i have a notification for a security update of ~1.5mb but how can I install it?
When I just hit the button "install now" the phone restarts into twrp and can't perform the update.
Any ideas what to do?
Im also interested in this
You will have to remove twrp.
I made full update of my system with twrp via HuRUpdater, so there should be a way to "only" install this security update.
Otherwise, is there a way to get the original recovery back?
flattervieh said:
I made full update of my system with twrp via HuRUpdater, so there should be a way to "only" install this security update.
Otherwise, is there a way to get the original recovery back?
Click to expand...
Click to collapse
Original recovery wont work either.
You need a modified recovery that can install
Not approved firmwares. We had a nocheck recovery on huawei p9 forum. Something similar we need for this device.
You are playing with the fire by playing with that kind of updates without having the basic knowledge of ADB. HuRUpdater fails for many reasons and can brick easily your device even if you do the things right.
So basically you have to find original Recovery.Img and push it through adb. From the other hand the latest firmware is not signed from google yet so in a way its going to be useless since for every future update you will face issues if its not signed by google.
So basic steps find official firmware for your cust.
Extract recovery image, install adb on your pc
Google the commands for adb recovery,
Push recovery image.
Download firmware finder from google play,
Check firmware versions, check if its approved from Google
If not wait a week or so and it will get approval.
Then it will push automatically.
If your device is not to be rooted its not really worth to have twrp. If you are rooted then try to find no-check recovery for honor 10 and this way you can install upcoming updates and security patches with no google approval.
Be extra careful, a security update won't make your phone powerful. Instead you might brick it and never recover it again. As a developer i already send to garbage 5 huawei P9 devices and countless honor 8
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Does anyone have a guide on how to root a Xiaomi Redmi Note 10? I’m a novice Android user so any help will be appreciated. Thanks
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
Thanks mate. Will wait for the phone to be unlocked then will try these steps.
hello, I followed the whole procedure and the phone only reboots in bootloop or after several reboots it brings me back to Fastboot
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
what about vbmeta?
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
I do not understand the question
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
titifayls said:
I do not understand the question
Click to expand...
Click to collapse
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
precisely I did not take magisk v22 but v21, moreover I have exactly the same version as the first poster is 12.0.1 RKGEUXM.
To root I took the boot.img from version 12.0.2, was it an error?
I tried to reflash the original boot.img file from v12.0.2 but still in bootloop
I can not find anywhere where to take my original version yet up to date v12.0.1
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Slim K said:
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Click to expand...
Click to collapse
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
titifayls said:
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
Click to expand...
Click to collapse
I asked if you're using windows or linux to connect to your phone. About losing data, maybe a clean flash could be required, but trying first won't hurt.
Here is how you do it: (you can use the downloaded fastboot firmware, because your device is unlocked, so region differences won't matter that much when flashing full firmware):
Inside that .tgz archive (that you unarchived) you'll find a script called flash_all_except_data_storage.bat for windows or flash_all_except_data_storage.sh for linux. (Do not use the flash_all_lock.bat/.sh script or risk a hard brick, so read carefully this time!!!!)
Connect your device in fastboot mode and open a CMD/Terminal where those scripts and the rest of the firmware files are. Use fastboot devices to make sure device is recognized.
If it is, then type in fastboot followed by dragging and dropping the flash_all_except _data_storage.bat to your CMD/terminal and press Enter. The process should begin automatically. If you get an error, make sure to have typed a space after the fastboot command and before the dropped script.
If it takes a long time during flash of super, don't panic!! Super.img is a very big file
Done!
If it still bootloops after that, then use the flash_all.bat script (will factory reset your phone and delete data)
It doesn't matter, it gives me the list of commands but doesn't launch anything
Wouldn't it be better to put fastboot flash?
don't bother, I'll take miflash, it'll be easier
I delivered an eea_global_images_V12.0.2.0.RKGEUXM rom with miflash by putting flash_all_except_data_storage.
I recovered everything at startup, my applications everything, so I redid the manipulation for the root and now everything works, perfect
thank you
I did the above process successfully.
Also if new update comes out, the process must be done again (not including the unlocking part of course).
The ROMs are posted here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
pihpih95 said:
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
Click to expand...
Click to collapse
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
pihpih95 said:
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
Click to expand...
Click to collapse
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Slim K said:
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Click to expand...
Click to collapse
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
pihpih95 said:
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
Click to expand...
Click to collapse
I used the latest as well. Most of the time, it errors out and I can't see the time left, but sometimes it works. Don't forget, you're giving them your imei for the freedom of your phone. Those imei's must be stored on Chinese servers and the tool must query those servers to get any info, depending on your country it may not work at all.
My experience with using an older tool has been very bad, the time was extended to 2 weeks instead of one on an another Xiaomi device. Avoid doing that and wait the requested time first.
After following the instruction my phone keeps rebooting.
I tried the flash_all.bat without success. What could I do?