Related
It all started when I tried to temporarily boot into the TWRP img file. It didn't work so I tried flashing the file to boot_a. Then I installed TWRP through the installer (stupidly didn't wipe the caches) and... Well. When I try to boot into System through TWRP, it gets COMPLETELY stuck at the powered by Android logo screen. No amount or combination of button holding will shut it off and I actually had to let the battery (thank you SO MUCH for non-removable batteries by the way, smartphone manufacturers >_>) drain before it would actually boot again. Rebooting it into Download mode will get it stuck in there too where every time I hold the power button and shut it off, it will just reboot right back into Download mode again. And now, here's probably the worst part. I CAN'T UNLOCK the critical partition to flash when in Download mode, so I can't use the OST tool! When I try to unlock it, it just complains that flashing unlock is not allowed even though the rest of the bootloader is completely unlocked.
TL;DR - When I power the phone up it goes straight into TWRP. Booting to System totally freezes it and the Bootloader puts it in a loop when I try to power it off. Critical partition is locked for some reason. I CAN get around the bootloader loop though and get back to TWRP by switching active slots and rebooting.
Did you flash the TWRP installer to your active boot partition or your inactive one? If you flashed it to the active one, you can't get into system anymore because TWRP is your boot partition.
If you are on Oreo, and you flashed to the inactive slot, and then patched the active slot, you have to reboot into the active slot recovery and flash the Magisk installer to disable verification of the partitions.
If you can get into the bootloader, and you still have the unlock key from nokia, do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
THMSP said:
do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
Click to expand...
Click to collapse
This unlocked it! Thank you! <3
I also did have an issue with the OST tool complaining that the updater was out of date, but changing the .mlf file and leaving it unpacked when I opened it in OST seemed to make it work perfectly. My phone is now booting just fine and back to stock!
Now I just need to solve the original problem I had. How can I install TWRP to recovery since the img file wouldn't temporarily boot last time?
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
S5Guy said:
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
Click to expand...
Click to collapse
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Yeah looks like you're right. Letting it update back to Android 9 deleted TWRP and made fastboot boot for TWRP nonfunctional again.
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
S5Guy said:
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
Click to expand...
Click to collapse
You have to flash it directly to your boot partition. fastboot boot will work for nothing (and even if it worked those images would just send you directly into the system)
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Alright! fastboot flash boot_a (TWRP image) worked! Thank you so much for all the help. <333
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
IronJacob said:
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
Click to expand...
Click to collapse
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
lolo9393 said:
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
Click to expand...
Click to collapse
No i did know. Just tried but both twrp don't work.
Btw i'll try to write in that thread too.
Thank you
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Stoffl_ said:
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Click to expand...
Click to collapse
As written on eu forum, the only recovery working is the 3.2.2.
Every other recovery, 1208 too give me:
Mi logo (unlocked) - black screen - Mi logo (unlocked) - system. But no recovery.
Tried to flash a custom rom different to xiaomi.eu but got bootloop, same with kernel flashable zips on xda. Only bootlooo...
I really don't know what to do anymore...
Yeah weird, I've literally guided a friend through the process just yesterday with that method.
Zero issues
Hi guys,
I flash Havoc-OS on Mi9T Pro Global PFKMIXM 10.3.1 by TWRP, after reboot do not start system and not enter on TWRP again.
I try this commands on fastboot below.
Code:
adb devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
fastboot reboot recovery
Can anyone give me a help?
Thanks.
fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.
S3miniFin said:
fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.
Click to expand...
Click to collapse
Hi friend, mainly thanks for helping.
I tried your suggestion, but it doesn't work.
I restored with Mi Flash Tolls, the only alternative. Now it works well.
You will now try the Flash I Rom and waiting for new updates and then flash any custom rom.
After I want share stuff tools and congratulations.
Have nice guys!
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
E:\Downloads\Mobile Phone\ADB>fastboot flash recovery twrp-3.3.1-13-raphael-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.400s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.732s
E:\Downloads\Mobile Phone\ADB>
Click to expand...
Click to collapse
Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
Yes, that's what happened to me.
The only solution I found was to install the new rom via fastboot.
For this you will need to perform the following steps:
1 - Install Mi Flash + drivers (this is boring, if you have Windows 7, it will be easier). In this link you will find some downloads and more details.
2 - Download the Sotck Rom (for fastboot important) from your device, in my case it was PFKMIXM 10.3.1 for Mi9T Pro. You need to extract zip then before.
3 - Flash the new rom via fastboot (approximately 10 minutes).
After that, your device will start with the new rom, then you can flash TWRP again and everything will work. The Magisk installation may cause error 1, but only flash boot.img through TWRP.
Be quick, because if the battery drain, you won't be able to start it in fastboot again.
If you need any links, ask me. I didn't have time to share everything.
Have a nice and good luck!!
Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)
rodolphe06 said:
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)
Click to expand...
Click to collapse
Yes, very important.
In Mi Flash, check only "Clean All" dont clean and lock.
Thanks.
thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower
Madaz2 said:
thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower
Click to expand...
Click to collapse
Thank you for sharing your experiences.
Too bad you couldn't recover. I hope you can do it again.
Today I had to flash twice, once because I flashed Kernel Quax and couldn't rollback and once for trying Rom Syberian. I hope that in the future we will have a firmware balanced with the customs kernel and roms.
Good luck.
Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.
Madaz2 said:
Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.
Click to expand...
Click to collapse
With flash cable or have you open?
Hot-Proton said:
With flash cable or have you open?
Click to expand...
Click to collapse
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL
Madaz2 said:
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL
Click to expand...
Click to collapse
I think works, for me it was like this.
Have nice.
After an android update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
fastboot flash boot_a "boot.img"
fastboot flash boot_b "boot.img"
But now It's in a bootloop,
I tried flashing the unpatched boot.img from redfin-rd1a.200810.021.a1-factory-cd18efdf but that didn't help.
Is there a way to solve this without loosing all my data?
fr0sty said:
After a firmware update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
Click to expand...
Click to collapse
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Edit- you can try flashing over the previous version or reflash the current version. If those all fail, I'm not sure what to suggest and some one with a bit more knowledge maybe can suggest a fix.
Ducter said:
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Click to expand...
Click to collapse
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
fr0sty said:
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
Click to expand...
Click to collapse
If you were promoted with an update, updated, then proceeded to flash the boot image you were running prior to updating, that's not going to work. You'll need to track down a patched boot image for your current version you have flashed or reflash the update via fastboot, you can follow the guide posted and it walks you through the steps to not wipe everything.
I'm in the same position. I took the OTA update, then downloaded the 11.0.0 (RQ1A.210105.003, Jan 2021) from Google. I patched the boot.img with Magisk, put it on my laptop, and flashed it in fastboot. Now I'm getting a bootloop. I tried flashing the unpatched boot.img to try to just get back in, but I'm still bootlooping.
Did you ever find a solution? FWIW, I'm on AT&T. I noticed that sometimes there is an AT&T specific file, but that did not appear to be the case this time.
I finally fixed it. At first I didn't see that the latest factory image was on the end of the list here https://developers.google.com/android/images
I picked 11.0.0 (RQ1A.210105.003, Jan 2021), then i extraced the boot.img file from it and flashed it in fastboot with fastboot flash boot boot.img --slot all.
That resulted in a no command screen when booting. But i was able to boot in safe mode. And from there i could patch the new boot.img file with the latest magisk. After that i patched that in fastboot and now everything is working again!
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
saturday_night said:
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
Click to expand...
Click to collapse
For me my solution is easier, because i don't know all the fastboot commands to do the things you write
Well, you are not the only one with the exact same Problem (wrong boot.img or maybe broken dl) and there are several threads already. Just answering here because it was the newest.
If you or anybody else use the boot.img from your own device there will never ever be a Problem with it. I already wrote a step by step guide (with fastboot comands) for this somewhere on xda for one of my older devices. Just need to find it and i will link it here.
Hi ALL,
any chance that anyone rooted the Pixel 5 or pixel4a 5G then get the NSG working?
the device i have is rooted correctly and checked by (Root checker) however the Diag port is silent and not producing any log, need to get the NSG working...
please help !
Thanks
Hello guys!
I am having a problem updating my current TWRP (version 3.52 came from one youtuber) to TWRP 3.6/OrangeFox.
I carefully follow steps. Even extracting my own rom boot.img just to flash it in accordance to said step. I successfully flash the said recovery but when i reboot to system or power off. It just keeps booting to recovery. Hoping for some enlightenment. Thank you!
1) you did not say what steps you did, or which tutorial you followed
2) what do you need twrp for?
jjsan said:
1) you did not say what steps you did, or which tutorial you followed
2) what do you need twrp for?
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
That's the instruction given in a thread. I followed it but no luck. Keeps rebooting to recovery.
cant say if it works or not.
for rooting its better patch img and flash.
read this. there is also solution for bootloop
How To root Redmi Note 10S without TWRP (Text Guide in English)
By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader) So, if like me, you ended up buying the Redmi Note 10S because it was...
forum.xda-developers.com
jjsan said:
cant say if it works or not.
for rooting its better patch img and flash.
read this. there is also solution for bootloop
How To root Redmi Note 10S without TWRP (Text Guide in English)
By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader) So, if like me, you ended up buying the Redmi Note 10S because it was...
forum.xda-developers.com
Click to expand...
Click to collapse
I already root my device . Just confused why the posted updated TWRP and Orangefox (both by Woomy) doesn't let me boot to system.
pumpkin072618 said:
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
That's the instruction given in a thread. I followed it but no luck. Keeps rebooting to recovery.
Click to expand...
Click to collapse
hmm, you sure you actually installed the stock rom kernel?
J6idot said:
hmm, you sure you actually installed the stock rom kernel?
Click to expand...
Click to collapse
I used the extracted boot.img pulled using adb. Am i doing it right?
pumpkin072618 said:
I used the extracted boot.img pulled using adb. Am i doing it right?
Click to expand...
Click to collapse
You can download the original ROM package and extract the boot.img from it, see if it works
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com