Related
because of modem update in hydrogen os 2.5 this whole mess starts pls help
Rohanlovely said:
because of modem update in hydrogen os 2.5 this whole mess starts pls help
Click to expand...
Click to collapse
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
How u got back the sim 2 working ?
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Rohandd said:
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Click to expand...
Click to collapse
Sim 2 start working after that ?? U tried that ?
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
could you please list out the exact steps you have done to fix your issue?
there are many users who are getting this issue including me.
please list the steps with the links of files you flashed. it would be a great help.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2?
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
Did you tried with this??
any fix??
ashu01 said:
Did you tried with this??
any fix??
Click to expand...
Click to collapse
My laptop windows crashed after repairing that i will try
Rohanlovely said:
My laptop windows crashed after repairing that i will try
Click to expand...
Click to collapse
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Had the same problem
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
ashu01 said:
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Click to expand...
Click to collapse
now new is problem started in my mobile telegram guys i able start d 2nd sim in my mobile but now sim 1 imei is 0
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
u tried it? works?
lockmunk said:
u tried it? works?
Click to expand...
Click to collapse
I tried and was fine.
First i did full wipe, then flash this zip + any rom and rom started fine.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
rajatdixit said:
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
Click to expand...
Click to collapse
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
ashokmor007 said:
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
Click to expand...
Click to collapse
Make sure your bootloader is unlocked
rajatdixit said:
Make sure your bootloader is unlocked
Click to expand...
Click to collapse
yes it is unlocked
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Hello,
Inside the fastboot ROM file "tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz" (Nougat 7.1.2) ... in the file "flash_all_lock_crc.bat" for example, these lines appear:
fastboot %* flash modem_a %~dp0images\modem.img || @ECHO "Flash modem_a error" && exit /B 1
fastboot %* flash modem_b %~dp0images\modem.img || @ECHO "Flash modem_b error" && exit /B 1
It seems that the file is called "modem.img", not "NON-HLOS.bin".
May be?
Regards!
PS: Sorry for my English!
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
m.hashem said:
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
Click to expand...
Click to collapse
if it is under warranty just brick your phone and give it to service centre they will flash it and give you back
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Wow! The file NON-HLOS.bin is the modem for other Xiaomi phone. May be you use a batch file (flash_factory.bat) for other phone, not Mi A1. Please use Mi Flash with right rom.
this is method not working
bangir said:
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Click to expand...
Click to collapse
this is method not working
gautamaurya said:
this is method not working
Click to expand...
Click to collapse
What happens if you try to re-flash your modem with the flash_all or flash_all_except_storage scripts from here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929 ?
Can you please report, if it works and if should not work, please attach the terminal/ shell outpout of the failed flashing attempt here.
modemst1 and modemst2
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
m.hashem said:
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
Click to expand...
Click to collapse
I have done some digging in order to assist you to get this fixed. I think I have 2 very hot leads (untested as I don't have any issues with my IMEI):
1. http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/ & http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/
2. https://androidmtk.com/use-qualcomm-smartphone-write-imei-tool (looks almost to easy, but worth a try?)
Please report your feedback here
hey bro how to the editting modem1st.img
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
now i dont have any connectivity... signal.. wifi etc..
Click to expand...
Click to collapse
Hello!
I made the same mistake. Is there a way to solve this problem?
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
Same problem here. Phone doesn't work correctly now. Boots, freezes and reboots. :crying:
persist image problem
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
thank you very much broo my device is fixed freezee and reboots problem
Ok. But what is the persist partition? Someone tried already? Doesn't want to brick my phone completely.
how to the editting qcn file beacuse my imei 0 null please help me editting brother
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
The freeze and reboot problem is fixed. Thanks. Still one problem. IMEI1 is 0 and IMEI2 is null. Anyone has an idea?
Nordland_ua said:
Hello!
I made the same mistake. Is there a way to solve this problem?
Click to expand...
Click to collapse
Me tooo
Sent from my Mi A1 using Tapatalk
https://www.androidfilehost.com/?fid=673956719939818468
Replace the IMEi with UR Own IMEI . if not it's illegal to use this QCN
Password : testnreport
if you don't know how to change IMEI Using hex editor , try my method . DO NOT use QCN to restore .
(hex and imei provided in order for u to find n replace)
i lost my imei n spent me about 6days n 8 hours per day to find a way to fix it .
actually it's easy to fix the problem .
My own method
1. download the older rom (7.8.23) Link
2. Use flash_all.bat
3.reboot into fastboot mode , erase modemst1 and modemst2 .
fastboot erase modemst1
fastboot erase modemst2
4. reboot
5. go to phone , enter *#*#717717#*#*
6.got to settings enable USB Debugging (ADB)
7. disconnect your phone n connect it back
8.Use WriteDualIMEI(W+G_eMMC) Remember run as administrator , enter your IMEI .
9.if success , go to phone enter *#*#717717#*#* to disable the diag port
10. reboot
Done .
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Edit: flashed persist partition only via Mi Flash with modified rawprogram0 and flash_all script. Sensors working now
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
Now I have the same problem as you
Could you please share your persist.img to save my phone xiaomi note3?
I would really appreciate it if you do this.
Please
Hello! I did the TWRP persist.img flash as described, but all the sensors still not working... Do you have any idea?
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
Hi, same problem here! Can you explain better how do i get the persist img and where i can download the fastboot img. Thanks
---------- Post added at 09:58 AM ---------- Previous post was at 09:24 AM ----------
Manwex said:
Edit: flashed persist partition only via Mi Flash with modified rawprogram0 and flash_all script. Sensors working now
Click to expand...
Click to collapse
Can you make a guide on what to do?
freddyededdy said:
Hi, same problem here! Can you explain better how do i get the persist img and where i can download the fastboot img. Thanks
---------- Post added at 09:58 AM ---------- Previous post was at 09:24 AM ----------
Can you make a guide on what to do?
Click to expand...
Click to collapse
Sorry, I already deleted scripts so you will have to waste a couple of minutes and do it by yourself. You can take a look at this video how it works, I've checked and it's explained well.
https://www.youtube.com/watch?v=Qf0XhhnpQEo
Just download fastboot ROM for Mi Note 3 (jason) and follow the video.
Persist.img is in fastboot rom archive (unpack). Flash with twrp
i found this tutorial and this work perfectly
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
this maybe can help u
https://alfa-roid.blogspot.com/2019/05/fix-sensor-mi-note-3-jason.html
Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Why flash April update? You can enable camera2api on any ota update! :/
WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.
Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.
sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?
michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Hi, i'm stuck in this fastboot limbo but can't find some of these files you mentioned: logo.img and misc.img
Where do i get them?
edit: nevermind, solved flashing fastboot miui with miflash pro.
EDIT 2: after flashing a rom i get stuck in fastboot everytime. How to avoid this?
Also tried flashing those files in that exact sequence but still stuck in fastboot.
My persist.img is shown not writable in cmd if I try to flash it. If I flash a rom using TWRP an error pops up saying "failed to mount /persist' (Invalid Argument).
SOLVED- Flashing persist.img from twrp "Install Image" works.
farhan20 said:
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Click to expand...
Click to collapse
Could you (or anyone) please provide these files.
Reep1324 said:
Could you (or anyone) please provide these files.
Click to expand...
Click to collapse
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
farhan20 said:
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
Click to expand...
Click to collapse
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Dr.Dinel said:
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Click to expand...
Click to collapse
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
farhan20 said:
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
Click to expand...
Click to collapse
thanks for replying
i finally solved it, used a chinese twrp that has the option to install on persist partition and the rest was easy
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
hamidezat20 said:
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
Click to expand...
Click to collapse
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
like me please help me after installing miui 11 Chine version
hamidezat20 said:
like me please help me after installing miui 11 Chine version
Click to expand...
Click to collapse
U r stuck on fastboot right and u said u can't flash fastboot rom because u r getting anti roll back error so I gave u solution
How to fix this problem
Hello same me how to fixed step by step
First you need fastboot rom extract fastboot rom on your pc after extract find 3 file
1-boot
2-recovery
3-system
Flash with fastboot
Turn off your phone and going to fastboot
Type
Fastboot devices
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Done device can't boot but you can install twrp China version link ?
https://www.lanzous.com/i6ahykh
after installation you can go to twrp
Download fastboot miui install from twrp
Sorry for me English
Oh my god, you saved me!
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
timbook2 said:
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
Click to expand...
Click to collapse
You're able to flash miui 11 after such long time or just 9.8.15?
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
lucifer said:
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
Click to expand...
Click to collapse
Hi, u deleted from flash all. Bat right and what's the error u r getting?
farhan20 said:
Hi, u deleted from flash all. Bat right and what's the error u r getting?
Click to expand...
Click to collapse
well it worked after i moved the file to c:/ drive but after flashing i lost widewine L1
When I got 9.8.15 working I stopped at least I got a working phone now, I will try and flash stock later.
I got anti rollback error trying to flash stock with miflash tool.