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
While I was in a hurry, I made a serious mistake and did this :
fastboot flash boot filename.img
( I wrote the TWRP recovery image, into the boot partition ! )
Now, I need to reverse this, and getting stuck.
My Note 11 [SPES] (without NFC) has this current image :
• V13.0.15.0.RGCMIXM
I have re-downloaded this Xiaomi ROM as a Fastboot image and a Recovery image as well.
So, I'm looking for advice on how to get the original boot img
back into my phone, eg. with Fastboot method or Recovery method (if possible)
PS:
I'm using a Windows PC (and not a Mac)
Thank You.
metaxda said:
While I was in a hurry, I made a serious mistake and did this :
fastboot flash boot filename.img
( I wrote the TWRP recovery image, into the boot partition ! )
Now, I need to reverse this, and getting stuck.
My Note 11 [SPES] (without NFC) has this current image :
• V13.0.15.0.RGCMIXM
I have re-downloaded this Xiaomi ROM as a Fastboot image and a Recovery image as well.
So, I'm looking for advice on how to get the original boot img
back into my phone, eg. with Fastboot method or Recovery method (if possible)
PS:
I'm using a Windows PC (and not a Mac)
Thank You.
Click to expand...
Click to collapse
Just flash the boot image that is inside the fastboot ROM, and then, if you want back TWRP, boot to it, through fastboot, and then, through TWRP, flash it to the ramdisk partition.
SubwayChamp said:
Just flash the boot image that is inside the fastboot ROM, and then, if you want back TWRP, boot to it, through fastboot, and then, through TWRP, flash it to the ramdisk partition.
Click to expand...
Click to collapse
@SubwayChamp ,
Thank You for that advice.
It saved me.
( The work PC I was using, had some 'security restrictions' set by the company,
where I could not open the Fastboot image at first, but I managed to work it all out
and grab the boot.img file , and then proceeded as your suggestion )
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
When I first time flashed twrp via Odin in Samsung Everthing was ok. But today I don't have computer (It is brocken) and I flashed magisk.zip in twrp in wrong way because twrp flashed as recovery. It cause bootloop but then I flash uninstall.zip and tryied to flash stock recovery in twrp but partitions /boot and /recovery is too small what should I do?
Ok i was using wrong files. Boot.img was from difrent device. How to close thread?
You can report your own post asking to close it.
Hi.
I had just lineage-20.0-20230426 installed, then using fastboot flashed twrp-3.4.2_A12-lancelot-dimenzino.img as recovery.
Now I cannot enter recovery and fastboot using key combos. I also cannot turn off my phone.
It stays on the "Redmi" boot logo. I can trigger a reboot using long key press.
I cannot get SP Flash Tool working, I only got an error "BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)" twice.
Any ideas how to fix this?
Update: With MTK bypass utility, I can now use SP flash tool to read flash. I also tried writing partitions, but the partition table doesn't match original firmware. (I read out the PT from flash)
Up to "proinfo" partition, it is the same, but then "boot_para" in stock scatter file has start offset 0x18500000, while in phone it starts at 0x18580000. Also, all following partitions up to "ffu" are shifted by 0x80000 bytes. Actual "super" and "cache" again match stock. Not sure how that happened. Any ideas?
I read back shifted "md1img" and the content matches stock md1img, same for spmfw, lk,lk2. Shifted boot and dtbo match the last-flashed LineageOS.
Why are partitions shifted vs stock?
Where is IMEI etc stored?
How to safely revert to stock firmware using SP flash tool? Now it complains the GPT does not match, and I should do "format all + download". But I read you should never do that. How can I make SP flash tool write only a new partition table?
Using MTK bypass utility, I could make SP flash tool work. I read out the on-phone partition table (where I found many partitions were shifted by 0x80000 bytes) and edited a stock scatter file to match it.
Then I flashed only the lineage-20.0-20230426 recovery partition.
Now the phone boots into LOS, and also recovery and fastboot work.
Why is it impossible to use fastboot, just because the recovery partition is bad?
Good evening, I need help because I can't unlock an Android 13 bootloader. Cordially