I just got it 2 days ago,unlocked the bootloader and rooted the device. So i went to flash a custom rom and i wiped system,cache and data,then when i tried to flash i gets stuck at Updating partition details... And then says Failed! in red letters. What can i do to unbrick my device?
Try another ROM. You may have tried ROM not compatible with your device, or just may be a corrupt download. Or you may have an outdated firmware or TWRP version.
If we had more details, we might be able to tell why it failed. Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also post what TWRP version number. And what ROM (exact name, version number, etc.) you tried.
redpoint73 said:
Try another ROM. You may have tried ROM not compatible with your device, or just may be a corrupt download. Or you may have an outdated firmware or TWRP version.
If we had more details, we might be able to tell why it failed. Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also post what TWRP version number. And what ROM (exact name, version number, etc.) you tried.
Click to expand...
Click to collapse
Thank you. I fixed my phone the way you told me how,but i ran into QHSUSB_BULK and i fixed that,so while i was in recovery i flashed InsertCoin and now its working! Thank you! :highfive: :angel:
filipkosteski said:
but i ran into QHSUSB_BULK and i fixed that
Click to expand...
Click to collapse
QHSUSB_BULK is really just a symptom, rather than a single defined problem. It just means your computer can't "talk" to the phone. It may mean the phone is simply not powered on, or that it's hard bricked. The latter is not fixable, so I'm guessing it's simply the former (not powered on) that caused the QHSUSB_BULK message.
In any case, glad to see you sorted it out.
Related
hello, can anybody help me to change back serial number, i flased my dhd several times with custom roms, sommehow my serial number have changed, now is sommeting like :
device serial number: is with symbols;
i unrooted my device, now i use wwe 2.2.1 , stock rom,
i dont know how to restore the original serial number from case.
any advice is wellcome.
thank you in advance
bibiii79 said:
hello, can anybody help me to change back serial number, i flased my dhd several times with custom roms, sommehow my serial number have changed, now is sommeting like :
device serial number: is with symbols;
i unrooted my device, now i use wwe 2.2.1 , stock rom,
i dont know how to restore the original serial number from case.
any advice is wellcome.
thank you in advance
Click to expand...
Click to collapse
Did You solve problem? If yes, how you did that?
Tried this? http://forum.xda-developers.com/showthread.php?t=1761707
iopetja said:
Tried this? http://forum.xda-developers.com/showthread.php?t=1761707
Click to expand...
Click to collapse
How to use it for DHD? This is guide for SGS II
Sorry, didn't go through text....
iopetja said:
Sorry, didn't go through text....
Click to expand...
Click to collapse
thanks anyway. So maybe U know if the wrong serial can be the reason that i can't find any networks GSM, and can't choose my language, like i always could, when i flash official ROM (WWE - with Polish language)?
To try to fix the upper useless post:
"The device serial number (as reported by 'adb devices') appears to be set in the kernel, under arch/arm/plat-s5p/devs.c (look for 'device_serial'). This may be different for your device, I'd suggest a grep through the kernel sources for the device ID that is reported by adb devices. Change the string, rebuild the kernel and flash it on...
Looks to be different on ICS by the way..."
edit: you need a dev to give you an answer. If adb uses s/n to verify the phone, and it does, rom dependables wouldn't be a surprise.
Have you tried to play a bit in adb?
iopetja said:
To try to fix the upper useless post:
"The device serial number (as reported by 'adb devices') appears to be set in the kernel, under arch/arm/plat-s5p/devs.c (look for 'device_serial'). This may be different for your device, I'd suggest a grep through the kernel sources for the device ID that is reported by adb devices. Change the string, rebuild the kernel and flash it on...
Looks to be different on ICS by the way..."
edit: you need a dev to give you an answer. If adb uses s/n to verify the phone, and it does, rom dependables wouldn't be a surprise.
Have you tried to play a bit in adb?
Click to expand...
Click to collapse
I tried to find device_serial and similar in kernel sources (different kernels) but no success. What do you mean with 'Have you tried to play a bit in adb?"
Just wondering if there's an option inside adb to modify...but don't have the knowledge to support you directly.
Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Hi everyone. I got a problem with my HTC M8.
First of all, I didn't make with it any changes (as unlock bootloader, root or installing any custom OS or recovery etc.) Week ago I left device, connected to PC for all night, and, I gess, with "bad" micro-USB cable.
Next day I couldn't boot this phone. I connected it to charger and after little time it was loaded to fastboot. But up today I can't do anything with phone: I can't unlock it, can't factory reset, can't boot to recovery etc...
I tried to find any same simptomes in google, but found nothing
As you can see on screenshots, I made steps for unlock bootloader but on device I didn't see notification about unlocking.
Click to expand...
Click to collapse
Could you help me with advices? Thanks.
I'm taking a bit of a guess but some how system has got wipe but that seems a bit off for a locked phone but since it's locked I would take it back to where you got it from and get them to sort it.
Sent from my One M8 using Tapatalk
Darknites said:
since it's locked I would take it back to where you got it from and get them to sort it.
Click to expand...
Click to collapse
I would normally say the same. But the OP mentioned in another thread posted in the wrong forum section (linked in his post) that he bought from Canada but lives in Ukraine, so I think warranty is not valid. It would have been helpful for the OP to give all the relevant details in this new post.
I agree, it looks like his OS and possibly recovery have somehow become wiped, corrupted, or damaged. Not common for a stock device, but not unheard of, either.
MaggiMag363 said:
Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Could you help me with advices? Thanks.
Click to expand...
Click to collapse
Hi
I had a similar problem to you where I was stuck in fastboot mode and the only command it would execute was POWER DOWN and when switched back on it returned to fastboot mode. However I ended up in that state due to making a mistake in trying to unlock and root my phone. Also I believe my display showed the RADIO and OpenDSP details rather than the INVALID_VER_INFO that your's is showing.
I thought I had deleted the rom and recovery on my device and I had bricked my phone however I was able to recover my phone by getting a new unlocktoken from HTC and flashing it.
Once I had successfully unlocked my phone I had access to my rom and recovery.
I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
If it doesn't work, it shouldn't do anymore harm either!
Best of luck.
I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
Click to expand...
Click to collapse
Yes, I did this And in consol I saw that everything was fine, but on device I didn't see standart notification about unlocking.
A found some topics about "INVALID_VER_INFO" - and they said that it can be ok for some devices (guys checked this on their worked devices, booted to fastboot and saw the same).
http://forum.xda-developers.com/showthread.php?t=2715056 here is the topic about "INVALID...".
btw - I tried unlock phone after another man. He did the same - receive .bin from dev. HTC site etc. I did the same, but from another HTC dev. account and result was the same Phone didn't unlock.
It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk
Darknites said:
It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I have the riff box but without needed pin-outs (http://i01.i.aliimg.com/wsphoto/v0/...x-Flex-font-b-cable-b-font-for-Samsumg-LG.jpg I'm talking about these pin-outs). And my previous experience with riff box and Samsung S3 was not very good)))) I had been fixing it during 2 months
https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Does cwm boot?
Sent from my One M8 using Tapatalk
[/COLOR]
Darknites said:
Does cwm boot?
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve
elawady.2014 said:
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve
Click to expand...
Click to collapse
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk
Darknites said:
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
but how can i work wifi and camera ?
elawady.2014 said:
but how can i work wifi and camera ?
Click to expand...
Click to collapse
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk
Darknites said:
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
ok thanks but i can't install other custom recovery
i have 3 backup by cwm and nandroid to my old rom
but when i restore it it not restore
do u know why ?
if other way to restore backup ?
elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Hey man. Sorry but your problem not the same. You installed custom OS and it could be the reason of this. I install nothing. I have full stock device. And my problem not the same with your problem. Could you create new topic please?
Venomtester said:
https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.
Click to expand...
Click to collapse
Thanks. But my skill too low for soldering these small parts I talked about completed pin-out connectors for JTAG. I tried to find them on EBAY and other JTAG stores, and failed (look at screenshot with these pin-outs higher).
Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)
MaggiMag363 said:
Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)
Click to expand...
Click to collapse
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.
Darknites said:
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.
Click to expand...
Click to collapse
Ok. And Can I flash version with unlocked bootloader and custom recovery, for example? (I said that there are a lot of recovery but they are custom. Is it ok for me or I should find pack with all stock?)
guess mid
Click to expand...
Click to collapse
It's unknown letters for me. Would you describe what did you mean? Thanks.
Hi guys. I'm having a bit of a problem. I want to preface this by saying I know almost nothing about modding Android.
A while back I bought a used HTC M8, and I guess it had a bunch of modifications to it because it was rooted and boots into a weird screen (says something about being for developers only?) before booting into a screen that it waits on for about 5 (says ROM: Internal) and then boots the OS.
Well recently I had an issue where Maps wouldn't work and would lockup my phone when I launched it. So I decided to do a factory reset. After the reset was complete it was impossible for me to log into my Google account as the app would crash every time I tried to log in. Not logging in = unable to use the play store, etc. I tried factory resetting twice more and kept having the same problem.
So I decided maybe the phone had some weird custom OS installed that caused the phone to act weirdly. I decided I'd go to the HTC website and download their ROM and install it. However the phone doesn't seem to accept the ROM since the installation encounters an error and crashes at the beginning of the install.
So I decided I might as well try to flash a custom ROM since the phone had already had all the modifications done. It had some TeamWin recovery thing installed, S-ON enabled, and the bootloader unlocked. I downloaded the latest nightly of CyanogenMod and tried to flash it in recovery mode. It seems to complete okay as it says "success" after flashing. But when I try to boot the device it just boots directly into recovery mode and I can't seem to figure out what I've done wrong?
Any help would be super appreciated.
post the result of fastboot getvar all after removing serialno and imei
ahmed.ismael said:
post the result of fastboot getvar all after removing serialno and imei
Click to expand...
Click to collapse
Sorry, could you please be a bit more detailed on how exactly I'd do that?
Edit: Seemed to have fixed it by flashing the latest version of TWRP and then flashing Cyanogen mod again. Thanks!
Firepower01 said:
I decided I'd go to the HTC website and download their ROM and install it. However the phone doesn't seem to accept the ROM since the installation encounters an error and crashes at the beginning of the install.
Click to expand...
Click to collapse
Just for your knowledge, you can't just install just any RUU. It has to match your phone's carrier version (CID), which is one of the reasons ahmed asked for your getvar data (and those details of the phone can also affect what TWRP version to use, what ROMs you can install, etc.). Plus, you need to relock the bootloader to RUU, unless the phone is s-off.
The process of doing fastboot getvar all, has been described on this forum too many times to count. So its not his responsibility to describe that process to you; when you can easily find it by searching and learning for a few minutes.
I'm actually out of town now so I don't really have any way of knowing of the ROM I used is compatible with my carrier. My phone is unlocked so I wonder if that matters?
Regardless, I'll look into posting my getvar all when I get home. Thanks.
Firepower01 said:
I'm actually out of town now so I don't really have any way of knowing of the ROM I used is compatible with my carrier. My phone is unlocked so I wonder if that matters?
Click to expand...
Click to collapse
I'm not talking necessarily about your carrier or if the SIM is unlocked. The official RUUs will only run, if they match the CID of the phone.
We may be able to determine the version direct from the device, if you have an OS number listed on the bootloader screen. Is there an OS number listed there, and if so, what is it?
I couldn't install the HTC ROM, so I installed CyanogenMod.
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
If you have already flashed Pie Rom (including bl、 baseband), you will not be able to return to Oreo
Hello.
I am trying to research the imei bricks on Sprint models after Verizon pie update. In short, everything we understand says this should not be happening, and yet it is.
Can you, for research purposes, describe the state of your device when you applied the update? Was it running full verizon firmware down to the bl, modem, and gpt? I may have an experimental fix but I need to gather more info about the bricks.
Also, it is impetative that you don't flash any further modems for my fix to have a good chance to work. Thanks.
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
hqureshi said:
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
Click to expand...
Click to collapse
What firmware did you flash from? Stock? Do you have an unlocked bootloader?
If yes to all the above, I can give you some experimental things to try.
Yes to all and bootloader is unlocked.
btw i have flashed firmware in this order
1. i flashed NASH_PPX29.159_19_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
then
2. XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and now on
3. NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
hqureshi said:
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
Click to expand...
Click to collapse
That's really odd. Sorry, I have nothing right now for you but will look into this as best I can.
Thanks, btw whenever i flash stock nougat i am getting verification failed error during flashing of bootloader.img
EDL
R-T-B said:
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
Click to expand...
Click to collapse
I can see the qualcomm device in twrp on my device manager. how to i get to edl mode. there is no reboot edl option in twrp. do i command fastboot reboot edl when device in twrp screen? when i run the qboot blank-flash it says wating for device
Please use latest TWRP from here https://dl.twrp.me/nash/ load it using fastboot and the in TWRP click reboot and select EDL.
Let me know if you face any issue.
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Everyone keeps trying to flash pie firmware that isn't for their variant and this is the result, no baseband. Plus once you upgrade to a pie modem, you can't go back to an oreo modem. Maybe something will come along and remedy that, that's a big maybe too. The devs are trying to find a solution, but there just might not be one. You can't blankflash your way out of it, and if you're not careful you can brick your phone for real. Not 9008 brick, paperweight. Not trying to be an ass, just trying to warn others. If it isn't pie for your phone, don't flash it.
Blankflash doesn't work anyways.
Stand by we are working on another fix.
R-T-B said:
Blankflash doesn't work anyways.
Stand by we are working on another fix.
Click to expand...
Click to collapse
Let me know if you need this fastboot_nash_verizon_oem_vzw_user_9_PCX29.159-21_10d9a_release-keys-cid2_vzw.tar.gz. I have got it from @oslov a member of discord.
I have tried this in this sequence but still zero IMEI.
1. Nougat Blank flash
2. Flashed Stock Verizon Oreo and then staying in bootloader mode I flashed above Pie Update using Flash-All batch file.
Phone successfully booted with Verizon sim activation warning but IMEI was 0.
I thought I should update you guys.
Thanks
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
R-T-B said:
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
Click to expand...
Click to collapse
Lol. Wow!
Thanks again for doing this. Best
un1ocked said:
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Click to expand...
Click to collapse
Have restored IMEI # with the help of @oslov, We will share the solution in a while.
hqureshi said:
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
Click to expand...
Click to collapse
I have resolved the 0 IMEI issue with the help of R-T-B, by doing undo Sim/network Unlock. changing CHMOD of id_00 to 0770
so now I am facing sim/network locked,
So whenever i unlock the sim/network lock i get 0 IMEI issue.
I will appreciate if someone now can help me to unlock SIM/network lock while keeping IMEI
I am currently on Retail pie with Sim/Network Locked. Phone Model is Sprint XT1789-03, dual sim enabled
Hello.
Tried Ubuntu Touch on my device - it was working excellent (for linux). Decided to try Pixel Expirience ROM, but on a step of flashing stock global ROM I found that IMEIs are lost. Blame myself for not making backup and probably pressing "format all" somewhere, but I have again installed Ubuntu Touch and it did have IMEIs (both) and they match numbers on a sticker. Why does manufacturer's firmware does not "see" IMEIs and why Ubuntu Touch does?
Flash ENG ROM, than flash stock or custom rom.
ENG ROM has IMEI's right, official ROM (fastboot images, oldest available on android 9 from different regions) does not.
ENG ROM looks cool but can't understand anything in mandarin
Maybe I am doing something wrong? Should I try recovery (not fastboot) images after ENG ROM?
avi9526 said:
ENG ROM has IMEI's right, official ROM (fastboot images, oldest available on android 9 from different regions) does not.
ENG ROM looks cool but can't understand anything in mandarin
Maybe I am doing something wrong? Should I try recovery (not fastboot) images after ENG ROM?
Click to expand...
Click to collapse
If you want to find out reason, maybe you will need to wait lots of time. Or maybe you just use new temporary IMEI fix module, and just let it go
Phone was turned off for a week
Using ENGinnering ROM (thanks dzli) I get into Engineering menu using *#*#3646633#*#*
Tried to use AT+EGMR command with same IMEI1 (ENG ROM does see IMEIs correctly) but it failed with error 100.
Decided to fix my WiFi MAC being weird sometimes by setting it to correct one but with last digit changed (+0x01 to see if it works)
Flashed old global official firmware that was not showing IMEIs previously even after ENG ROM (firmware is the oldest that I have found on some weird site that gives links to miui dirrect downloads). Also I have removed anti_rollback check and lock command from flashing script (how my phone is not bricked? guess I am lucky with that)
Suddenly IMEI are correct and everything is working, I don't know which of this steps fixed my issue (probably WiFi MAC).
Anyway. I don't know if my phone is clean (there is non-zero chance I flashed some backdoored image somewhere before). Probably should
Kirasu2080 said:
just let it go
Click to expand...
Click to collapse
:sad: