I unlocke my Mi9T Pro (global) and tried to flash twrp, but for whatever reason I never managed to boot it
Now i can just get into fastboot
everything else no longer possible,
any ideas how I can get boot android again
I tried different twrp
with
fastboot flash recovery twrpXY
also
fastboot boot twrpXY
doesn't work
and yes it's a Raphael
You need to fastboot flash your stock ROM using Mi Flash tool.
Then you should be able to boot into system again.
P12AV33N said:
You need to fastboot flash your stock ROM using Mi Flash tool.
Click to expand...
Click to collapse
Flash not successful, doesn't really start to flash
stops at this line:
info:$for /F "tokens=2 delims=: " %i in ('fastboot -s XXXXXXXX getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
dna99 said:
Flash not successful, doesn't really start
stops at this line:
info:$for /F "tokens=2 delims=: " %i in ('fastboot -s XXXXXXXX getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Click to expand...
Click to collapse
Try flashing the latest global stable ROM
Seems like an issue related with Anti Roll Back feature implemented by Xiaomi.
The ROM you are flashing has lower ARB version i.e. 1
while the ROM you currently have installed has version 2
(Reboot device into fasboot mode, connect to pc, open command prompt and type "fastboot getvar anti" (without quotes) and check the ARB version)
Then download the ROM which has higher or same ARB version as your device.
Now the Question is, how will you find a ROM with same or higher ARB version?
and the answer is, I don't know.
btw if you tried flashing this ROM via twrp recovery, you would've ended up hard bricking your device.
It's good that Mi Flash gave you this error.
Edit : I'm assuming all this based on what's written in the error.
you have to make sure yourself by checking the ARB version using CMD in your PC.
P12AV33N said:
Try flashing the latest global stable ROM
(Reboot device into fasboot mode, connect to pc, open command prompt and type "fastboot getvar anti" (without quotes) and check the ARB version)
Then download the ROM which has higher or same ARB version as your device.
Click to expand...
Click to collapse
mhhh:
fastboot getvar anti
anti: 1
finished. total time: 0.003s
----
as I failed installing twrp, i tried to install the stable rom again and try it again.
dna99 said:
mhhh:
fastboot getvar anti
anti: 1
finished. total time: 0.003s
----
as I failed installing twrp, i tried to install the stable rom again and try it again.
Click to expand...
Click to collapse
type "fastboot oem device-info" in cmd and let me know.
i just happen to notice that ther is no stable version of raphael..... for fastboot...
fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
finished. total time: 0.012s
dna99 said:
i just happen to notice that ther is no stable version of raphael..... for fastboot...
Click to expand...
Click to collapse
http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
flash this.
does it also work for global, as this is the indian version
is there a step by step how to for installing twrp on the mi9t pro
I just read this, is this still a problem:
https://forum.xda-developers.com/showpost.php?p=77560732&postcount=22
as I also have a Ryzen
-----
although unlocking the bootloader worked
err:target reported max download size of 805306368 bytes
err:sending 'modem' (164428 KB)...
err:FAILED (data transfer failure (Unknown error))
err:finished. total time: 5.407s
info:"Flash modem error"
error:FAILED (data transfer failure (Unknown error))
process exit.
flashSuccess False
isFactory False CheckCPUID False
before:flashSuccess is False set IsUpdate:True set IsDone True
after:flashSuccess is False set IsUpdate:false set IsDone true
But at least it finally started
dna99 said:
But at least it finally started
Click to expand...
Click to collapse
Flashing started?
---------- Post added at 11:48 AM ---------- Previous post was at 11:48 AM ----------
dna99 said:
I just read this, is this still a problem:
https://forum.xda-developers.com/showpost.php?p=77560732&postcount=22
as I also have a Ryzen
-----
although unlocking the bootloader worked
Click to expand...
Click to collapse
Nah, I have ryzen as well but everything works fine.
P12AV33N said:
Flashing started?
Click to expand...
Click to collapse
I mean, at least it got way further in the procedure
it didn't start flashing the system
dna99 said:
I mean, at least it got way further in the procedure
it didn't start
Click to expand...
Click to collapse
Do let me know when you get the device working again.
I could just enter TWRP again
@ P12av33N
Any Ideas how i can make it stay fixed in recovery?
dna99 said:
I could just enter TWRP again
@ P12av33N
Any Ideas how i can make it stay fixed in recovery?
Click to expand...
Click to collapse
Flash magisk
Related
I have decided to post a new thread as all the other threads on this are not for my phone.
I try to do what bootloader says which is 'fastboot oem lock begin' but I get stuck.
It says afterwards:
Code:
...
<bootloader> Ready to flash signed images
OKAY [ 0.476s ]
finished. total time: 0.479s
But what are the signed images?
So I skip flashing the 'signed images' and go ahead and type: 'fastboot oem lock' and it gives me this error:
Code:
...
<bootloader> Re-Lock Failure. See display.
OKAY [ 0.644s ]
finished. total time: 0.667s
So, I look at the display and it says:
Code:
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100MB
USB connected
Fastboot command failed
OEM lock
OEM lock begin
Getvar partition-type:recovery
Fastboot command failed
Getvar max-download-size
OEM lock
E:No valid PIV block in SP for cdrom
E:piv validation failed (cdrom)
E:Falied to validate piv objects
Re-lock failure
Somebody please help me!! I have been trying to search for my phone's stock rom for days without success! PLEASE HELPPP!!!!
If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13
ICuaI said:
If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13
Click to expand...
Click to collapse
Thank you. It did work but I want to know, how do you tell when it is locked?
Also, I have already tried to go back to stock firmware using RSD-Lite but I don't know where to find the needed file...If you can help with that, I would be very grateful.
Thank you,
GoldenPaul27
Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?
GoldenPaul27 said:
Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?
Click to expand...
Click to collapse
No, the is zipped. You have to unzip this file first.
HTML:
ICuaI said:
No, the is zipped. You have to unzip this file first.
Click to expand...
Click to collapse
OK. I shall try this. Thank you for your help so far.
nice
I wanted this 2, tks!!
Just another question:
How do you tell when the bootloader is relocked??
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:
not possible to flash firmware in downloade mode?
mrt box
elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..
Dude, I have the same problem with a P20 Pro since january!
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?
Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Writing devcfg_a failed
Flashing is not allowed forum critical partition
b1gb1ng said:
Writing devcfg_a failed
Flashing is not allowed forum critical partition
Click to expand...
Click to collapse
fastboot flashing unlock_critical
b1gb1ng said:
Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks
Click to expand...
Click to collapse
https://en.miui.com/thread-3052407-1-1.html
Daha3ker said:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
when I launch this command it is not recognised, I just have a list of commands in fastboot
what should I do?
fastboot -w
Be warned, it will wipe your device.
Sift said:
fastboot -w
Be warned, it will wipe your device.
Click to expand...
Click to collapse
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"
Grooverit said:
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"
Click to expand...
Click to collapse
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
minnuss said:
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
well, I updated the newest adb, now the command seems to work, but after "fastboot flashing unlock_critical" I still have this:
PS C:\android-sdk\platform-tools> fastboot flashing unlock_critical
OKAY [ 0.034s]
Finished. Total time: 0.035s
PS C:\android-sdk\platform-tools> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s
no unlock why?
---------- Post added at 03:26 PM ---------- Previous post was at 02:55 PM ----------
it was my erorr, sorry
thanks for the advice, I unlocked and than flashed stock rom after booting in edl mode
I still have to check if I still have bootloader unlocked as I get advise on start screen
Grooverit said:
I still have to check if I still have bootloader unlocked as I get advise on start screen
Click to expand...
Click to collapse
Yes it is still all unlocked.
And if you wish to thanks someone on this forum, use the thanks button in the down right corner of the post that helped you. :good:
You should visit Xiaomi service centre. They will unbrick your phone without any charge.
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
oloco2 said:
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Try something from the following:
A) in fastboot mode use command
fastboot erase userdata
reboot and try to flash stock recovery_ramdisk and flash full stock FW via dload
B) try to update your phone via eRecovery - turn off, plug the cabel and press and hold Power + Vol Up. In eRecovery's menu select "Download latest etc etc."
C) fully discharge the battery and try previous methods
(in your case little chance, this method works with error 11/2, you have 15/1)
D) use testpoint method
E) paid services (dc-phoenix etc.)
Thank so much for your help -Alf-
Unfortunally I have to say that now my phone is not able to enter fastboot mode.
What I dd:
The comands you asked for:
fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0JRE)
OKAY [ 0.007s]
Finished. Total time: 0.009s
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
OKAY [ 0.008s]
Finished. Total time: 0.009s
As nothing changed, I used testpoints.
I had to enter fastboot oem unlock 5KKK7... in order to unlock bootloader again
But now.. Phone keeps rebooting with the same eror window as before, but I'm still unable to ener not fastboot mode not erecovery.
Now i really feel locked, as I think there's nothin else I can do.
I also unplugged battery multiple times in order to discharge all the circuit, but no news...
Any other idea, please?
Regards
oloco2 said:
Unfortunally I have to say that now my phone is not able to enter fastboot mode
Click to expand...
Click to collapse
oloco2 said:
The only way I can use thee phone is via fastboot.
Click to expand...
Click to collapse
?
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
oloco2 said:
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
Click to expand...
Click to collapse
Try this method - turn off, hold Volume Down and plug the cabel.
oloco2 said:
System 8.0.0.046(0JRE
Click to expand...
Click to collapse
oloco2 said:
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Click to expand...
Click to collapse
oloco2 said:
failed input oem_nv_item error
Click to expand...
Click to collapse
oloco2 said:
SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
Click to expand...
Click to collapse
Testpoint or dc-phoenix, bro.
-Alf- said:
Testpoint or dc-phoenix, bro.
Click to expand...
Click to collapse
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
oloco2 said:
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
Click to expand...
Click to collapse
You have to flash board software using testpoint . Google it, I have no experience with that.
Ok. Thank you -Alf-. I will have a look to google.
But in the meanwhile, if someone else coukd help me a little bit, will be more than welcome
Regards!!
Hi -Alf-
I got good news for me. I got fastboot working again. I need to use potatonv in order to get it, but anywayI think it's good news.
Please, any other idea in order to make it come back, please?
Thank you
oloco2 said:
any other idea in order to make it come back,
Click to expand...
Click to collapse
your phone has an incomplete FW (System 8.0.0.046 (0JRE)),, an unknown model and a problem with oeminfo. Do you even read what I'm writing???
https://forum.xda-developers.com/t/...-security-verify-failed.4453855/post-86982695
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
oloco2 said:
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/i-bricked-my-honor-9-lite.3799176/post-76943641
Hey -Alf- !
I can ay that finally I got it working.
How I did it:
I got a full firmware for my devce and using Huawei Update extractor I extracted all the images to a folder.
Using a little script un batch I createda .txt with multiple lines:
fastboot flash cache cache.img
fastboot flash crc crc.img
fastboot flash curver curver.img
fastboot flash cust cust.img
fastboot flash dts dts.img
fastboot flash eng_system eng_system.img
fastboot flash eng_vendor eng_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmet erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
fastboot flash fastboot fastboot.img
fastboot flash fw_hifi fw_hifi.img
fastboot flash fw_lpm3 fw_lpm3.img
fastboot flash hisiufs_gpt hisiufs_gpt.img
fastboot flash boot kernel.img
fastboot flash modemnvm_update modemnvm_update.img
fastboot flash modem_fw modem_fw.img
fastboot flash odm odm.img
fastboot flash package_type.img package_type.img
fastboot flash patch patch.img
fastboot flash preas preas.img
fastboot flash preavs preavs.img
fastboot flash preload preload.img
fastboot flash product product.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash sensorhub sensorhub.img
fastboot flash sha256rsa sha256rsa.img
fastboot flash system system.img
fastboot flash teeos teeos.img
fastboot flash trustfirmware trustfirmware.img
fastboot flash userdata userdata.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash verlist verlist.img
fastboot flash version version.img
fastboot flash xloader xloader.img
And I run all the commands.
Some of them gave me some errors like partition lenght or something like that, but at the end, once rebooted, the error was gone.
Then, I updated all the firmware usong dload.
Now I'm facing a little error about oeminfo. I think itis due to the fact that the firmware I used was rusian, and my phone is from EU. I already created another thread in this forum.
I want to thank you for your tme and your ideas.
I hope this post can help someone over there with an error like mine.
Thank you very much for your time and help
Regards
No problem. Btw, why russian FW? I gave you a link with EU FW . Okay, your choice...
oloco2 said:
Now I'm facing a little error about oeminfo
Click to expand...
Click to collapse
Little?
Yes, The russian FW I flashed was yeterday. Now, after you replied to my post, I will try to upgrade FW to the EU version. I hope now everything works as it should
The "litle error" about oeminfo is:
"/preas/xxx" in some parts of the settings. I read somewhere it was due to oeminfo.I'm I wrong?
Thank you!!
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
All fixed!!
I found this oeminfo:
OEMinfo & Dump & CERT Honor 9 Lite (LLD-ALL)
OEMinfo & Dump & CERT Honor 9 Lite (LLD-AL00 / LLD-AL10 / LLD-AL20 / LLD-AL30 / LLD-TL00 / LLD-TL10 / LLD-L21 / LLD-L22 / LLD-L31 / LLD-L32 / LLD-L42). Share File Certificate, File Dump, OE…
azrom.net
After updating it, all info seems to be correct in about. Also, there's a new OTA for me!
What a road gave me this phone
I hope I'mnot comming back to here in a while
Thank you for all your help
Regards!!!
oloco2 said:
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
Click to expand...
Click to collapse
Kindly share your batch script, pls
Please help me, I have a Redmi Note 10S. I followed the tutorial and now my phone appears the Redmi logo and restarts, I can't flash the stock rom I flashed the twrp recovery rosemary but when I run the command:
❯ fastboot getvar product // product: maltose Finished. Total time: 0.001s
Previously, the output of this command showed _b show it
❯ fastboot getvar partition-layout
getvar:artition-layout FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
I think this information may be important because when I installed twrp the log appeared
sending boot_a
writing boot_a
rafaelinaciodev said:
Please help me, I have a Redmi Note 10S. I followed the tutorial and now my phone appears the Redmi logo and restarts, I can't flash the stock rom I flashed the twrp recovery rosemary but when I run the command:
❯ fastboot getvar product // product: maltose Finished. Total time: 0.001s
Previously, the output of this command showed _b show it
❯ fastboot getvar partition-layout
getvar:artition-layout FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
I think this information may be important because when I installed twrp the log appeared
sending boot_a
writing boot_a
Click to expand...
Click to collapse
Try to flash through spflashtool
Thanks I'll try
I came back here to say that after having help I managed to get my phone working again, Redmi Note 10S codenamed maltose you can use the same rosemary firmware to flash the stock rom, just go to the firmware update xiaomi website and download the stock rom from your cell phone and flash it by running the flash_all.sh file on linux with the cell phone in fastboot mode