I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
In TWRP to skip the password requirement I touched cancel and touched wipe (without a custom wipe), and after doing so I made an error, but after trying a couple of hours later the same thing came out, until I tried 3 more times in a row and he left me, after that I could finally use LineageOS 17.1
maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------
FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
You need to format data
TWRP - wipe - format data (option on the right)
Reboot to recovery & flash rom again
Or in fastboot do
fastboot erase userdata
Either way backup anything on internal storage (pics docs music etc) first as this will be deleted
TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
would you be kind enough to help me through it on messenger?
TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?
maserati2011 said:
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?
Click to expand...
Click to collapse
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device
TheFixItMan said:
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device
Click to expand...
Click to collapse
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?
maserati2011 said:
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?
Click to expand...
Click to collapse
Please read my past responses carefully
I said once you have found a custom rom that gives you imei you can then back up efs partition using a 64bit twrp to restore it if you loose it in future (or using other roms)
Related
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Voyebanm said:
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Click to expand...
Click to collapse
Did you erase the system? If not try to flash for fastboot just boot.img, maybe help you, if don't reboot flash the entire rom image
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
did u check "clean all" and try edl mode (just a reminder,it happened to me many times,i was impatient/panicked forgot to check "clean all")
Voyebanm said:
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
Click to expand...
Click to collapse
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
nijel8 said:
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
Click to expand...
Click to collapse
No Luck so far.
Voyebanm said:
No Luck so far.
Click to expand...
Click to collapse
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
I will give that a try. Thanks
http://en.miui.com/a-234.html
Install MiFlash from Xiaomi, download fastboot image and unpack it.
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
Boot to EDL mode with hard keys method, screen stays black, but Qualcomm QH USB device shows up in Device Manager/Ports. MiFlash fastboot image.
If you have 8 or newer Windows, you have to boot it driver signature verification disabled before MiFlash install:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Voyebanm said:
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Click to expand...
Click to collapse
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
SubwayChamp said:
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
Click to expand...
Click to collapse
Thank you though, I was able to resolved it by flashing the EFS backup that I had.
Problem SOLVED !!!
Thanks again for your Help.
I got a bricking when I tried flashing MIUI EU ROM over CM on a locked bootloader. Is there a way to flash the latest firmware files without also flashing a new boot image which could brick the phone? I had to do an EDL flash using MiFlash last time, I don't want to go through the hassle again.
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?
Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully
OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?
i accidently flash the custom rom but now i dont have the original rom backup :crying::cryinglz help any body can upload the twrp system ,vendor and any other things required to restore the original rom :angel::angel:
redmi 6 pro indian version or atleast english version plz
edit : twrp sakura
Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/
coolek33 said:
Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/
Click to expand...
Click to collapse
will i be able to flash the stock rom because i tried indian version but it wont work twrp sakura
also which one shall i download fastboot or recovery ?
If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.
coolek33 said:
If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.
Click to expand...
Click to collapse
1) lol is there a way to not to lock my bootloader again because if it fails then all is left is fastboot??
2) and also twrp will be removed or shall i flash twrp again or will it brick my device ??
3) or i need to wait 15 days and unlock my device again??
man lot of questions
4) my mi account has unlock permission so do i need to permission again because right now i am using custom rom to keep my phone alive.:crying:
these questions will raise to all if they did the same mistake some more questions but lets see these first
also thanks man you are wonderful helper
If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.
coolek33 said:
If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.
Click to expand...
Click to collapse
i flashed
crdroid rom from redmi 6 pro forums
bootable
kk i will try advanced wipe
also that redmi6 pro tool kit u mentioned is it mi unlock tool if not plz send me the link plz
also thanks i will contact you when something went wrong
also when i flashed custom rom it shows installing unconditionally why
also the restore function is not working is it the twrp fault or the rom
it doesn't boot says boots on logo and then shows the boot animation waits for 5 min and boots twrp again automatically why???(when i try to restore the crdroid rom not to mentioned i tried flashing resurrection os but goes on boot loop )
When flashing custom ROM different from miui you should wipe dalvick, cache, data and system before flash. Then flash RR or something else gapps and boot.
Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436
coolek33 said:
Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436
Click to expand...
Click to collapse
found this site
https://mi-globe.com/rom-builder/
Ethical Hacker|Youtuber said:
found this site
https://mi-globe.com/rom-builder/
Click to expand...
Click to collapse
lol man that unlock tool did the trick i flashed the above rom from the mi globe rom and my phone got locked again i open the tool and then i unlocked the phone and boom it got unlocked but remember that when u unlock ur data will be deleted and always keep the backup of ur twrp image
after unlock and the login id and pass that pass u will need to enter the phone startup otherwise just boot to fastboot and then bypass account
man finally back to miui without any bugs with root man what else we want
Hi everyone,
I flashed the stock ROM today from bootloader and after that I restored both the persist and efs partition on my device but still the imei and baseband versions are missing, please help me solve this...
Turns out that after flashing your stock ROM you should first boot to twrp from bootloader (do not flash twrp) and restore the backup of your EFS and persist partitions, after that boot to system, there you will find that your imei and baseband are missing, then connect to a WiFi network and start installing all ota updates that pop up till your device is up to date, after installing the last ota update and booting the imei and baseband will be visible...
You might not get any signal after doing so, I don't know how to fix it, I will post a fix for that here after I find one...
Hausemaster said:
Turns out that after flashing your stock ROM you should first boot to twrp from bootloader (do not flash twrp) and restore the backup of your EFS and persist partitions, after that boot to system, there you will find that your imei and baseband are missing, then connect to a WiFi network and start installing all ota updates that pop up till your device is up to date, after installing the last ota update and booting the imei and baseband will be visible...
You might not get any signal after doing so, I don't know how to fix it, I will post a fix for that here after I find one...
Click to expand...
Click to collapse
have you fixed it ? i did same thing with my G6 Play ..
infango said:
have you fixed it ? i did same thing with my G6 Play ..
Click to expand...
Click to collapse
Nope, I also no longer have the device
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
woelkchen said:
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
Click to expand...
Click to collapse
Try to flash the last firmware or rom
V13.0.4.0.SJSMIXM
https://xiaomifirmwareupdater.com/firmware/gauguin/
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
TWRP
https://androidfilehost.com/?w=files&flid=318225
Thx. Went ahead and did that which ofc solved the issue. Thx a lot
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
BolognaTown said:
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
Click to expand...
Click to collapse
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
BolognaTown said:
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
Click to expand...
Click to collapse
Use Miflash and read the tutorial carefully.
Miflash=Fastboot rom
Thank you, i unbricked it, and i installed lineage. Great Job