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
Related
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.
Hi I bring you how to root and install twrp on A70 any version ,I think its work on all new samsung device:good:
note :
1-first unlock your bootloader https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
2-in all step Remove auto reboot in odin
requirement files :
PeaZip
https://www.peazip.org/download-installer-p-windows.html
TWRP recovery.img mack it tar with PeaZip
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases
vbmeta.tar Vbmeta.img- https://www.androidfilehost.com/?fid...26312261811717
Stock recovery.img from your stock rom [ you can download your device rom and extract stock recovery ] and mack it tar with PeaZip
Magisk 20.1- https://www.androidfilehost.com/?fid...26312261797449
Odin3- https://www.androidfilehost.com/?fid...26312261811763
Samfirm- https://www.androidfilehost.com/?fid...26312261811762
Lets start
1- in stock roms maybe work on custom roms
2-boot in to download mode and flash vbmeta.tar via odin in ap
3-after that reboot to recovery by pressing vol+ and power and clear data and cache in stock recovery
4- reboot again in to download mod and now flash twrp via odin in ap
5-reboot to twrp recovery by pressing vol+ and power and slide right to modify. Click wipe, click format data, type yes after that go back and reboot to recovery. slide right to modify, click mount, if mount system partition read-only is checked, back out and reboot back to recovery and check mount again, it should now be unchecked. . Now click Vendor so its checked and system should be unchecked, back out.
6- Copy Magisk 20.1 to the External sd card. In TWRP click install, select storage and choose micro sd card, click on magisk and slide right to confirm. (you must have vendor checked in mount or it wont flash properly). when done, click all way back click reboot to download.
7- now flash stcok recovery tar file via odin and reboot your device to system
8-after your device start run Magisk and update it by install options
well done you have twrp and rooted device :fingers-crossed::good::fingers-crossed:
i think this method work on all new samsung device and just you have own your device file like
twrp /stock recovery /vbmeta
note : if your twrp Stuck on twrp logo you have to install stock recovery and repeat from step 2
tested device A705FN:fingers-crossed:
thanks to :good:
MarvinMod
Grarak
and other to help me in this method
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
thewalekk said:
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
Click to expand...
Click to collapse
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
seli1987 said:
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
Click to expand...
Click to collapse
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
thewalekk said:
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
Click to expand...
Click to collapse
Try again flash 4 file frimware and let device start to system after that reboot to download mod and flash vbmeta.tar and let your device start to system
After that reboot to stock recovery and wipdata and cach and reboot to download mod and now flash twrp
The wrong is with your bootloader if you cant fix it try to search your problem in google
You are not only one have this problem
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
thewalekk said:
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
Click to expand...
Click to collapse
Unlock bootloader, factory reset, unsure oem is unlocked and grayed out in settings >developer options.
Then flash vbmeta, manual reboot to download mode, flash twrp, boot to twrp, factory reset in twrp , flash magisk zip then factory reset again, now boot system.
The vbmeta you flash is empty and allows flashing third party zips.
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
BubSystemS said:
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
Click to expand...
Click to collapse
Go ahead with the steps. Ignore mount system.
Let's see what happens
Worst scenario, you soft brick the phone or bootloop which can be fixed by flashing stock rom again.
Make sure you have stock rom and you backup your data
Any way to pass SatefyNet?
Instal this path in Magisk:
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.0/safetynet-fix-v1.1.0.zip
So, i decided to get back to stock rom on my mi a2 since the pixel experience rom i've installed was very glitchy (i blame the method i used back than because i didnt have even root on it, but i admit the pixel experience rom was very nice!) but then i decided to install the stock rom so i could have a backup phone with no bugs, but only with root. so i installed the stock one (android version 8.1 / and 5 of august 2018 security patch update) but when i go to fastboot so i could boot it with twrp for example, it give me this error...
https://imgur.com/AYVIWL4
and it shows this on my screen too...
https://imgur.com/a/d4BQJAd (press any key to shutdown)
what can i do?
ZuNNN said:
So, i decided to get back to stock rom on my mi a2 since the pixel experience rom i've installed was very glitchy (i blame the method i used back than because i didnt have even root on it, but i admit the pixel experience rom was very nice!) but then i decided to install the stock rom so i could have a backup phone with no bugs, but only with root. so i installed the stock one (android version 8.1 / and 5 of august 2018 security patch update) but when i go to fastboot so i could boot it with twrp for example, it give me this error...
https://imgur.com/AYVIWL4
and it shows this on my screen too...
https://imgur.com/a/d4BQJAd (press any key to shutdown)
what can i do?
Click to expand...
Click to collapse
Bro what are you doing ?
Put TWRP RECOVERY image in adb folder and give name recovery.img
Then :
fastboot boot recovery.img
Then:
Inside twrp flash boot to boot partition by selecting install img or just flash magisk 20.4 zip by using adb sideload
adb sideload magisk.zip
( put magisk zip in adb folder and give name magisk.zip )
Also select adb sideload under advanced button. ..
KevMetal said:
Bro what are you doing ?
Put TWRP RECOVERY image in adb folder and give name recovery.img
Then :
fastboot boot recovery.img
Then:
Inside twrp flash boot to boot partition by selecting install img or just flash magisk 20.4 zip by using adb sideload
adb sideload magisk.zip
( put magisk zip in adb folder and give name magisk.zip )
Also select adb sideload under advanced button. ..
Click to expand...
Click to collapse
okay i tried what you said but it gave me this error after i fastboot the recovery.img, https://imgur.com/a/vMPVjvZ , and it shows the same error on my device
Which method did you use to install the stock ROM?
What version was the stock ROM before modding? As far as I know, from Android 9 Pie there's an Anti-RollBack protection.
ZuNNN said:
okay i tried what you said but it gave me this error after i fastboot the recovery.img, https://imgur.com/a/vMPVjvZ , and it shows the same error on my device
Click to expand...
Click to collapse
Just unlock the bootloader again ..you probably flashed stock and somehow locked bootloader ..
Fastboot oem unlock
Fastboot flashing unlock_critical
If that doesn't work you need to google "test point" for mi a2 and physically open your phone using video tut ..then you enter edl mode and flash stock rom using miflash and start over from 0
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Did you type on your pc fastboot reboot as a final step? Maybe you have to repair or reflash the stock rom using miflash and try again (you cant clear cache without twrp) as a way to get the system prepared to Flash a modified boot image
I have the exact same problem. I tried older versions of Magisk, then the Canary build, but nothing helped..
Bilihh said:
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Click to expand...
Click to collapse
Found a solution! It's right here:
How to flash twrp recovery and root redmi note 10s?
I can't install a twrp recovery if I tried A message appears (remote : this partition doesn't exist)
forum.xda-developers.com
I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
fastboot flash recovery recovery.img
fastboot reboot bootloader
and then select Recovery using Vol-Up/Down buttons + Power button to start the recovery ROM
Click to expand...
Click to collapse
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot
Click to expand...
Click to collapse
fastboot flash recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
fastboot boot twrp.img
Click to expand...
Click to collapse
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance
escalhavardo said:
I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance
Click to expand...
Click to collapse
hi
I think the arraki's TWRP on xda cannot be started.
Better to use orangeFox.
There is no Recovery partition on this phone, so we use "fastboot flash boot recovery.img".
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot
escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Click to expand...
Click to collapse
Use Xiaomi Flash Tool.
If you can get into fastboot mode, you can restore.
Then do the following. or give up.
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot
escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot
Click to expand...
Click to collapse
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.
kousuke5555 said:
6.Select "Slot A is active"
Click to expand...
Click to collapse
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
Thank you so much, you're a lifesaver.
escalhavardo said:
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
thank you so much, your a life saver.
Click to expand...
Click to collapse
Go back to fastboot
"fastboot set_active a"
1.fastboot getvar current-slot
2.if the result is slot a.(slot a in which the system boots)
3.fastboot set_active b
4.fastboot flash boot_b New_fox.img
5.fastboot reboot recovery
6.Select "Flash current OrangeFOX" in menu (automatically flash to both slot a/b )
7.Select "back"
8.Select "reboot" in menu
9.Select "Slot A is active"
10.reboot
You solved my problem. Thank you so much for all your help. You're a life saver.
kousuke5555 said:
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.
Click to expand...
Click to collapse
Can you send me unlocked bootloader backup of poco m4 pro 5g i just locked it and i can't unlock it now because my phone is bricked and it's showing nv data is corrupted if you have solution on this plz share it.
delete
kousuke5555 said:
hi
We can't solve boot loops with the bootloader locked.
Please go to the service center.
Had you backed up seccfg.img, you could have unlocked it again.
However, it is specific to each device.
I can't send.
Click to expand...
Click to collapse
Do you have any other solution to this error "nv data is corrupted"
delete
It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.
V0latyle said:
It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.
Click to expand...
Click to collapse
hi
Unfortunately, some models of xiaomi cannot use the fastboot "boot" command.
The method mentioned in the thread here is a last resort.
I've talked to some developers but they don't accept this method.
sad.
However, there is no thread in xda, but the developer made twrp, so I think we should use it.
shanawgray said:
Do you have any other solution to this error "nv data is corrupted"
Click to expand...
Click to collapse
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.
kousuke5555 said:
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.
Click to expand...
Click to collapse
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?
shanawgray said:
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?
Click to expand...
Click to collapse
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.
kousuke5555 said:
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.
Click to expand...
Click to collapse
thanks.....!
but I think I got the solution
For those looking at this thread.
Just in case, I'll mention it below.
This article is about "arraki's" TWRP and orangefox.
Information is old.
there's a new TWRP, so any troubles or questions should be resolved in that TWRP thread.
Thank you