How do I write IMEI along with baseband version back to my phone? I really don't want to risk bricking it again, that's enough stress for me in the past two days
I heard that I can only flash IMEI 2 back to it, and if I want flashing IMEI 1 as well I'd need to install a custom rom on the phone. So if that's a solution I'd love if someone could help me with it. MIUI 13 is slow and laggy af (which is the reason I bricked the phone in the first place, to install a better ROM).
But here's something, when I flash the phone's firmware through fastboot, issues start to rise (as per my experience with it so far), but through SP Flash Tool, it's alright. So I'd love to know if installing custom ROMs using the tool would be alright, if not then if recovery is required or if fastboot is fit for the job. If that's an issue I'd love if someone could give me advice when it comes to it.
Old post 1: (not my current situation)
"Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated."
Old post 2:
"It happened after manually installing engineering ROM on it, now I can only doubt it's BROM mode that's working and nothing else, but I'm not sure. SP Flash Tool doesn't want to work with the phone since I want to flash the stock rom back. I really need help please."
YLTN said:
Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated.
Click to expand...
Click to collapse
Install Engineering ROM and then write imei using available tools.
mvikrant97 said:
Install Engineering ROM and then write imei using available tools.
Click to expand...
Click to collapse
I fear that if I install the ROM, the phone might brick again
YLTN said:
I fear that if I install the ROM, the phone might brick again
Click to expand...
Click to collapse
Why?
mvikrant97 said:
Why?
Click to expand...
Click to collapse
The reason why my phone broke in the first place was due to flashing a misc.bin file after following a YouTube tutorial. It was part of a process to download twrp on the phone unofficially. Since then I started looking for ways to fix it until I finally found a post that had to do with fixing nvdata corruption (which was the error I had prior to fixing the phone) which helped.
So yeah, I don't think I can trust flashing ROMs on my phone as much as before, but I'll still try the engineering ROM thing.
mvikrant97 said:
Why?
Click to expand...
Click to collapse
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
YLTN said:
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
Click to expand...
Click to collapse
Does it shows up in device manager?
mvikrant97 said:
Does it shows up in device manager?
Click to expand...
Click to collapse
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
YLTN said:
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
Click to expand...
Click to collapse
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
YLTN said:
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
Click to expand...
Click to collapse
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
YLTN said:
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
Click to expand...
Click to collapse
Please install LIB USB drivers.
Visit this tutorial here on xda
mvikrant97 said:
Please install LIB USB drivers.
Visit this tutorial here on xda
Click to expand...
Click to collapse
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
YLTN said:
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
Click to expand...
Click to collapse
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
mvikrant97 said:
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
Click to expand...
Click to collapse
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
YLTN said:
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
Click to expand...
Click to collapse
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
Alright then, I'll follow the steps and tell you the results once I'm done.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
YLTN said:
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
Click to expand...
Click to collapse
Try flashing the ENG rom and try fixing your IMEI
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
So I ran into another issue. it tells me I need "exaid-verified.img" and that verified boot is enabled, which is not present in the ENG ROM folder.
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
Btw one more thing, I can update my phone right? Like, it won't break my phone? I'm good with MIUI 11 but I wonder if updating it would fix baseband version.
Related
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
sk3lt said:
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
Click to expand...
Click to collapse
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
otonieru said:
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
Click to expand...
Click to collapse
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
sk3lt said:
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
Click to expand...
Click to collapse
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
otonieru said:
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
Click to expand...
Click to collapse
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
sk3lt said:
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
Click to expand...
Click to collapse
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
otonieru said:
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
Click to expand...
Click to collapse
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
sk3lt said:
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
Click to expand...
Click to collapse
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
sk3lt said:
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
Click to expand...
Click to collapse
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
tsongming said:
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
Click to expand...
Click to collapse
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
sk3lt said:
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
Click to expand...
Click to collapse
use testpoint method, and flash it using QFIL.
otonieru said:
use testpoint method, and flash it using QFIL.
Click to expand...
Click to collapse
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
sk3lt said:
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
Click to expand...
Click to collapse
root cause of your issue is that you play with wrong qcn and messed up the nv,
wince you cant plugged to qpst, you need someone to make EFS backup for you torestore from twrp
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
How can I do this? Can you help me please?
jokerm90 said:
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
Click to expand...
Click to collapse
How can I do this? Can you help me please?
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
sk3lt said:
How can I do this? Can you help me please?
Click to expand...
Click to collapse
You need backup EFS and Modem via TWRP first(better with OrangeFox). After you need Magisk first and some manipulation with QCN file via QPST. I will write it later
MohamedYousri said:
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
Click to expand...
Click to collapse
Maui Meta is for MTK cpu phones. You need QPST
Note 8 Pro is MTK Device
Hello does anyone has Redmi note 10 5g engineering firmware?
thetank3393 said:
Hello does anyone has Redmi note 10 5g engineering firmware?
Click to expand...
Click to collapse
hi ,
I didn't try but those who tried confirmed it
Google Drive - Virus scan warning
drive.google.com
cdenizs said:
hi ,
I didn't try but those who tried confirmed it
Google Drive - Virus scan warning
drive.google.com
Click to expand...
Click to collapse
thank you so much i'll give it a try ...
cdenizs said:
hi ,
I didn't try but those who tried confirmed it
Google Drive - Virus scan warning
drive.google.com
Click to expand...
Click to collapse
thank, i going to prove
yonatanAraque27 said:
thank, i going to prove
Click to expand...
Click to collapse
Yes this is eng rom camellian, i've been trying to fix my imei
Saracawalk said:
Yes this is eng rom camellian, i've been trying to fix my imei
Click to expand...
Click to collapse
if work please reply
Saracawalk said:
Yes this is eng rom camellian, i've been trying to fix my imei
Click to expand...
Click to collapse
i fix imei only Second with out Disarm
dont care about if you have lost imei. phone could work anyway. and you have lost guaranted when u have unlocked. so if you sim work, dont waste your time for restoring original imei. one of my old phone have both imei erased to 00000000000 and works perfectly
wetito said:
dont care about if you have lost imei. phone could work anyway. and you have lost guaranted when u have unlocked. so if you sim work, dont waste your time for restoring original imei. one of my old phone have both imei erased to 00000000000 and works perfectly
Click to expand...
Click to collapse
Only a few carriers do accept registering devices with imei=0. so, it is a valid effort to recover it.
I updated to 13.0.2 with bootloader unlocked and magisk installed working fine. I like this last update.
*And my device id barcode also reappeared.
Gio1906 said:
Only a few carriers do accept registering devices with imei=0. so, it is a valid effort to recover it.
Click to expand...
Click to collapse
in italy imei 0 is not a problem. but with mtk chipset is easy recover it
wetito said:
in italy imei 0 is not a problem. but with mtk chipset is easy recover it
Click to expand...
Click to collapse
In Brazil, it kinda is. Only one carrier allow a imei 0 device to connect, and voice calls doesn`t work either.
And mate, It is easy. Meta mode, modem meta or maui meta, write it, disconnect, and you`re done. But making that **** boot after using maui meta is the hard part.
(btw, CDS info mode doesn`t work on camellia variant)
Gio1906 said:
In Brazil, it kinda is. Only one carrier allow a imei 0 device to connect, and voice calls doesn`t work either.
And mate, It is easy. Meta mode, modem meta or maui meta, write it, disconnect, and you`re done. But making that **** boot after using maui meta is the hard part.
(btw, CDS info mode doesn`t work on camellia variant)
Click to expand...
Click to collapse
i'm talking about camellian. if you have downloaded camellian firmware it's normal you have problems with camellia variant
wetito said:
i'm talking about camellian. if you have downloaded camellian firmware it's normal you have problems with camellia variant
Click to expand...
Click to collapse
No, the last bit I`m talking about camellia firmware, mate. CDS Info doesn't even appear on MTK EM there.
I just installed camellian engineering firmware due to A - Not finding camellia Eng Firmware anywhere, B - to test a couple of things. I tried to mod MIUI 13.0.4.0 SKSCNXM, and it's been on maintenance SINCE the failure to it. Which I messed up the EFS partition and been trying to fix. Which, by the way, ended on my situation above. Imei 0, can do it through meta mode, but it ends in a bootloop whatever the firmware I load up after.
Might need to borrow someone else's NVRAM, flash it, change the IMEI to mine, and see if it works.
Right now, to actually keep it "usable", it's on 12.5.5.0 RKSCNXM.
PS: The only differences between Camellian and Camellia are: The former got three cams, and NFC.
Oddly, Camellia's MTK Engineering Mode got a NFC tab, despite not oficially supporting it. Maybe SW disabled?
Gio1906 said:
No, the last bit I`m talking about camellia firmware, mate. CDS Info doesn't even appear on MTK EM there.
I just installed camellian engineering firmware due to A - Not finding camellia Eng Firmware anywhere, B - to test a couple of things. I tried to mod MIUI 13.0.4.0 SKSCNXM, and it's been on maintenance SINCE the failure to it. Which I messed up the EFS partition and been trying to fix. Which, by the way, ended on my situation above. Imei 0, can do it through meta mode, but it ends in a bootloop whatever the firmware I load up after.
Might need to borrow someone else's NVRAM, flash it, change the IMEI to mine, and see if it works.
Right now, to actually keep it "usable", it's on 12.5.5.0 RKSCNXM.
PS: The only differences between Camellian and Camellia are: The former got three cams, and NFC.
Oddly, Camellia's MTK Engineering Mode got a NFC tab, despite not oficially supporting it. Maybe SW disabled?
Click to expand...
Click to collapse
how did u do, it's very difficult i have updated from miui 12 to miui 13, changed EEA to global, rooted, installed some gsi for testing... Without problems. your brick is incredible. you made the impossible possible
wetito said:
dont care about if you have lost imei. phone could work anyway. and you have lost guaranted when u have unlocked. so if you sim work, dont waste your time for restoring original imei. one of my old phone have both imei erased to 00000000000 and works perfectly
Click to expand...
Click to collapse
Did you try on incoming or outcoming calls?
Voice calls will never work without IMEI.
wetito said:
how did u do, it's very difficult i have updated from miui 12 to miui 13, changed EEA to global, rooted, installed some gsi for testing... Without problems. your brick is incredible. you made the impossible possible
Click to expand...
Click to collapse
It's... Not bricked? Mate, not sure if you understand me, but the problem arised from my attempt to dev a custom rom based on miui china. And I'm literally using it to talk here.
Tried to make a lightweight version of miui for Camellia and ended messing up a few stuff, so I had to nuke the device.
Root, swapping camellia( n ) software back and forth, childs' play. But I messed up the code when messing with the internals of software. Get it now?
Gio1906 said:
It's... Not bricked? Mate, not sure if you understand me, but the problem arised from my attempt to dev a custom rom based on miui china. And I'm literally using it to talk here.
Tried to make a lightweight version of miui for Camellia and ended messing up a few stuff, so I had to nuke the device.
Root, swapping camellia( n ) software back and forth, childs' play. But I messed up the code when messing with the internals of software. Get it now?
Click to expand...
Click to collapse
ah ok sorry
VD171 said:
Did you try on incoming or outcoming calls?
Voice calls will never work without IMEI.
Click to expand...
Click to collapse
on my hold phone sure. the custom rom i have installed deleted original imei
th
cdenizs said:
hi ,
I didn't try but those who tried confirmed it
Google Drive - Virus scan warning
drive.google.com
Click to expand...
Click to collapse
thank you so much for this. a lot of sites are scamming me to pay for this rom
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.
Long story short, my gf Redmi Note 10 Pro somehow got to MIUI Recovery menu and 3rd party service managed to erase recovery and everything from the phone and gave back the fresh looking brick stuck on Fastboot!!!
I have successfully flashed EEU Sweet ROM (Europe (EEA) latest Fastboot ROM MIUI V12.5.6.0.RKFEUXM) on the Global version though and after that it comes to recovery menu but it shows in red "NV data is corrupted" now I am clueless what to do next. Desperate me tried to flash Global latest Fastboot ROM MIUI V12.5.9.0.RKFMIXM but it gives Anti Rollback error so based on info here https://www.xda-developers.com/xiao...78.2028059671.1642858063-854958160.1642858063 I have checked the Anti_version.txt of the current ROM and the one I try to install and both is on 3 so based on the info I should be able to flash to the same number but it wasn't successful so I tried to edit Flash_all.Bat file and remove the ARB check commands but even after that I still get the ABR error. What should I do? Am I taking a wrong path in solving the issue? Would flashing it again solve the "NV data is corrupted" issue?
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
romuser87 said:
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
Click to expand...
Click to collapse
Thanks, DLin the tool you mentioned atm but yes I did dl a EU version on global which I read it is no issue as long as it is not on Chinese version. It all started suddenly, out of nowhere the phone rebooted on Fastboot so it was taken to a 3rd party service and their they tried to fix it by wiping the phone to an unrecoverable state and said this is a new model so the files are not yet published you better take it to an authorized service!!!Oh I am mad! I'll report after trying the tool. Btw the other solution you mentioned was the 1st thing I tried but the file in 1st step is removed from the hosting server and someone asked the thread creator to reupload but no reply yet :/
Asgharjoon said:
Thanks, DLin the tool you mentioned atm but yes I did dl a EU version on global which I read it is no issue as long as it is not on Chinese version. It all started suddenly, out of nowhere the phone rebooted on Fastboot so it was taken to a 3rd party service and their they tried to fix it by wiping the phone to an unrecoverable state and said this is a new model so the files are not yet published you better take it to an authorized service!!!Oh I am mad! I'll report after trying the tool. Btw the other solution you mentioned was the 1st thing I tried but the file in 1st step is removed from the hosting server and someone asked the thread creator to reupload but no reply yet :/
Click to expand...
Click to collapse
Ok so now I tried with the tool and interestingly I had to make choices which were not easy and obvious anyhow, it didn't work
It gives the below error and seems to be called "sideload" status issue. But the phone now still reboots on Main Menu with the same old "NV data is corrupted"
romuser87 said:
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
Click to expand...
Click to collapse
I could finally flash the latest Global version but the error persists. Accidentally I did flash the phone with clean all and lock ticked Now I cannot even flash anything as bootloader is locked! How can I fix it help please
Here is the wrong selection on MI Flash! Is there anyway to get it unlocked?
Hello guys, after some struggle trying to unbrick my poco m3 pro, i faced a new probem, my IMEI has gone, as a noob that i am, i didn't made any kind of backup, i'm trying alot of ways, and still i didn't had any luck to re-write my IMEI (i still jave the numbem on the box of the phone) to the device, i'm using linux, almost everything that i found is to windows, does jave any kind of tool for linux, or i'll have to put windows on my laptop just for this porpouse?
there is anychance to use mtkdrive tool, the same used to bypass security for sp tools to do this ?
thanks for now
if your mobile services works, write imei is not necessary. and it's a dangerous operation. so if your devices now works fine, my suggestion is DON'T TOUCH ANYTHING
all my old phones that after modding lost originals imei worked without problems
a mobile sim could work also with all imei numbers=0
sadly my mobile service don't work, i keep zero signal, and when i try to get IMEI numbers on Settings > About device, it says unknown on both IMEis
ok
first try your sim into another device to be sure is not damaged
second search xiaomi redmi note 10 5g fastboot engineering rom and flash. this rom should repair some high problems like your.
if boot and all work fine, update to miui13. good luck
wetito said:
ok
first try your sim into another device to be sure is not damaged
second search xiaomi redmi note 10 5g fastboot engineering rom and flash. this rom should repair some high problems like your.
if boot and all work fine, update to miui13. good luck
Click to expand...
Click to collapse
thx, i'll try to find that rom, i already tried my sim on another devices, and works flawless
so... after long searchs and alot of re-bricks, i finally managed to instal an ENG rom, and had found some NVRAM and NVDATA files to flash too, with those i finally made to get some signal, but still my IMEIs is unknown when i get to about phone, and when i type *#06# i get nothing, not even 0000's. now how do i update from eng rom to a more updated version of miui without losing those configuration files
MTK IMEI Repair Tool Download (All Version) Updated 2022 | Mi Account Guide
When you have an MKT Android device, you can use an MTK IMEI Tool to flash or repair IMEI on your device. In order to make your damaged device functional
miaccountguide.com
i found this tool... maybe should work. but u had to test by yourself... this website have other utility that u could try. but now u have signal? data mobile?
wetito said:
MTK IMEI Repair Tool Download (All Version) Updated 2022 | Mi Account Guide
When you have an MKT Android device, you can use an MTK IMEI Tool to flash or repair IMEI on your device. In order to make your damaged device functional
miaccountguide.com
i found this tool... maybe should work. but u had to test by yourself... this website have other utility that u could try. but now u have signal? data mobile?
Click to expand...
Click to collapse
in mtk without box/server patch only sim 2 repair
Yonecloud said:
so... after long searchs and alot of re-bricks, i finally managed to instal an ENG rom, and had found some NVRAM and NVDATA files to flash too, with those i finally made to get some signal, but still my IMEIs is unknown when i get to about phone, and when i type *#06# i get nothing, not even 0000's. now how do i update from eng rom to a more updated version of miui without losing those configuration files
Click to expand...
Click to collapse
not work nv data/ram with out patch firmware ect,you only can return imei 2 for original.
shinobusensui said:
not work nv data/ram with out patch firmware ect,you only can return imei 2 for original.
Click to expand...
Click to collapse
U tryed put SIM on slot 2 with imei2 restored? Coul be a solution? Could u post a screenshot of phone information? (Tap 4 time internal storage
wetito said:
U tryed put SIM on slot 2 with imei2 restored? Coul be a solution? Could u post a screenshot of phone information? (Tap 4 time internal storage
Click to expand...
Click to collapse
its only information and you can use Maui Meta in Meta mode if you enter edl/testpoint, for me the first time lost two imei only return The Second imei, but send to waranty and change the Phone.
of coursed use a Semi Profesional Tools.
Did you find a fix? And where did you go wrong? Please let us know the mistakes you made so that we don't.
shinobusensui said:
its only information and you can use Maui Meta in Meta mode if you enter edl/testpoint, for me the first time lost two imei only return The Second imei, but send to waranty and change the Phone.
of coursed use a Semi Profesional Tools.
Click to expand...
Click to collapse
ok, so at least one of yours sims work. goog luck
Yonecloud said:
so... after long searchs and alot of re-bricks, i finally managed to instal an ENG rom, and had found some NVRAM and NVDATA files to flash too, with those i finally made to get some signal, but still my IMEIs is unknown when i get to about phone, and when i type *#06# i get nothing, not even 0000's. now how do i update from eng rom to a more updated version of miui without losing those configuration files
Click to expand...
Click to collapse
can i ask where did you get the eng rom?