yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] dlearin:
Yes, ive tried It (was my daily ROM at a12.1 so thought would be the same with a13) but have found aospa more stable (no headphone problems when received a call, less idle drain, fixed round corners, etc)

The only thing that i miss is the hbm.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] wesleysf55:
Excellent ROM! but only few notification and call ringtones working, others are causing error and crash.

BUG REPORT. Thanks for the work!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] HidekiRyuga:
Aospa Alioth Supremacy.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mi_guel:
I cannot agree more, I'm sticking with this ROM for a while, my only issue is that I can't hide the pill bar, even with magisk and for some reason orange fox is not working with the rom
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Can you please share what's not working with orange fox? I think about moving to PA and I'm currently using orange fox as recovery. Thank you!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mi_guel:
So it's kinda weird, I first tried to install the rom with orange fox and got stuck in the splash screen, then installed the rom from fastboot, all good but I tried to do fastboot boot to orange fox and just got stuck in a black screen, fastboot boot worked with TWRP but could not mount system so flashing magisk failed, but patching the boot image and flashing it from fastboot worked, so I'm using the rom and it's rooted but with no custom recovery
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Did you format the data partition after flashing the ROM from recovery?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mi_guel:
Yes, before and after, tried a couple of times, if you wanna flash from recovery I would sugest to use the rom's stock recovery
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Did anyone succeed flashing this through recovery? If so, what recovery did you use?

Thank you for sharing! :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Well, I flashed it successfully with OrangeFox (my current working build - I haven't tried with the latest released version, but I don't see how that would make a difference).

I guess that the trick is to format data before flashing the ROM, and, immediately after flashing the ROM, reboot OrangeFox (ignoring any errors that might be shown), and then format data again. Then reboot to system (again ignoring any errors be shown).

BTW: I flashed it successfully two different times, just to satisfy myself that the first success wasn't a fluke (it wasn't a fluke).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Sorry to bother you but do you think I could just boot into R11.1_1_5_A12 and install ofox after booting into it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
It doesn't seem that you can "fastboot boot" a recovery at all on this ROM.

You might have to flash it via "fastboot flash boot recovery.img", and then run "fastboot reboot recovery".

BTW: why would you want to use a Beta 11.1_1_5_A12 release that has been superseded by a subsequent Stable release?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Thanks for your reply, that´s what I learned as well. You can´t fastboot boot any recovery on PA yet. I didn´t try fastboot flash yet since everything else works pretty fine and installing my phone from scratch again is something I try to avoid for at least a month now ;)

Regarding the beta build: I wasn´t aware of the stable release. I had the beta image file somewhere and gave it a try.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mi_guel:
Fastboot boot worked for me with TWRP
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Can you please share the URL of the TWRP version you used? Thanks in advance! :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
I think he might be referring to this: https://eu.dl.twrp.me/alioth/

It does succeed in booting with "fastboot boot", but that is about all it does. There are tons of errors (visible in red on the console screen), it can't decrypt, it can't mount any partition, etc.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Ok, thank you for your warning :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] grret:
Just wanna say thanks guys! This rom is the best I've seen so far in terms of speed, responsiveness and stability!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blasev:
can you guys show me the geekbench 5 result?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sirnonox:
https://browser.geekbench.com/v5/cpu/20572069

https://browser.geekbench.com/v5/compute/6422569

https://browser.geekbench.com/v5/compute/6422623
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
This ROM uses vendor_boot-as-recovery. That is the cause of all the issues with custom recoveries.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] grret:
NFC quick toggle is missing.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sirnonox:
Very good rom in terms of speed battery life and responsiveness thouogh I had some strange reboots at night which disabled my alarm clock x( .

Not rooted... So still beta I think... I tried to get a crash report but could not identify anything (probably do not know enough how to :) )

Need to wait for next release I believe.

Great work by the way.

Thanks to support our device

ps: It seems than stable releases already exist for other devices (eg berylium)

omg just released (02/17) in fact .

i submitted to the Telegram group to get notified as soon as the release come.

I hope it will come soon :)

Thanks
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] denyo81:
Does this mean in plain language that we cannot flash the PA via OF or TWRP correctly?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Until a proper vendor_boot-as-recovery build of OrangeFox is released, yes.

I was able to flash it with the standard OrangeFox builds (coming from another ROM). But I wouldn't recommend it. Once you have flashed it, you would be then need a vendor_boot-as-recovery build, else you will get all the problems that have been described.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
Is this rom in development still? Is been more than a month from last release. I want to use it as daily driver.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
It is still in development, yes. But PA isn´t known for their rapid updates. If you´re looking for a solid ROM with amazing battery life, this could be your daily driver. If you´re looking for weekly or monthly updates, this might not be for you.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Akse_o:
Lhdc codec supported?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Veiranx:
I just successfully installed it, with OrangeFox coming afterward. Initial setup fails due to timing out on connecting to Google services. Wifi and data connection are just fine.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] grret:
Can't send chats in snapchat, same problem as this guy:

https://www.reddit.com/r/SnapchatHelp/comments/10vbryz
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Akitake:
Installed Topaz 1 Stable (from website)

First impressions: This is stupidly fast, raw android experience with Google Apps pre-installed. I've tested almost every ROM out there nothing feels this snappy. Best first impressions I've had on alioth.

Will be trying out this rom for a while, I'll report any issues I encounter.

This thread should probably be re-done with a better more long-term title as it's no longer in beta.

With better instructions, a non-broken image, etc..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] dave.c:
Poco F3 - M2012K11AG

aospa-topaz-1-alioth-20230426.zip

Little rom reviser, rom very fluid, duration is similar to the use I had with MIUI.

AOSPA comes with the google go camera is good but I prefer the port of gcam or the version of the Leica camera, the sound is heard a little canned, you miss the equalizer of miui or dolby I do not know what possibility there is to include this and if it does not go against the "philosophy" of the rom as happens with lineageos.

Finally customization is little perfect for me, many like a system full of features but if you prefer something more basic and functional this rom is perfect for you.

Bugs:

The first boot I encounter an infinite cycle of reboots the solution was to use a different carrier as the main one, it is a known bug that certain phone carriers probocan a bug with the networks of the bit and in some roms cause reboots.

The health application in

>get help quickly > get started > start setup >next.

It doesn't go past this button I've noticed it on other roms so maybe it's something in the app.

It would be interesting that people try to reproduce errors try to reproduce the errors that I have and see if it is something general or a bug of mine, if someone knows how to make a log of errors could send it or teach me to me.

Many thanks to the developer and the Paranoid Android team.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] grret:
Snapchat doesn't work on latest version (Stable 1, April). Known bug but no fix yet.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ext23:
Can anybody else provide usage impressions on this ROM? I'm tempted to jump over from CrDroid because Paranoid Android has AptX Adaptive support.

Also support the idea of making this an [OFFICIAL] thread.

Do we need to install this recovery before flashing the ROM? Will it cause problems with backing up/restoring my current CrDroid?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
https://xdaforums.com/t/vendor_boot-roms.4575777/#post-88415979
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ext23:
@DarthJabba9, thanks, OK, so if I'm understanding this right, and I wanted to backup CrDroid, and install Paranoid Android, I would have to:

1. Make relevant backups of CrDroid using the standard OrangeFox.

2. Save these somewhere on my PC or whatever.

3. Format and factory reset my device.

5. Flash Paranoid Android.

6. Without rebooting anything, flash the vendor_boot OrangeFox.

7. Reboot to recovery.

8. Format data.

9. Boot into Paranoid Android and play around with it.

Then, to go back to my initial CrDroid:

10. Format and factory reset my device...in fastboot? Or in vendor_boot OrangeFox?

11. Flash standard OrangeFox in fastboot.

12. Restore CrDroid backup.

This seems super complicated and easy to mess up...have I got anything wrong?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] knowledge@heart:
So, in case if i want to move from a "Vendor boot as recovery rom" to a "normal boot as recovery rom" like say lineage.

What should be done?

You imply that flashing a boot recovery will trash the boot partition. So a normal recovery will trash the boot partition.

What to do in such cases?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
That should work.

But - depending on what happens when you first try to boot the ROM (ie, if it just returns you to recovery), you might have to format the data partition using "fastboot -w" at the bootloader prompt.

Also, sometimes (depending on the ROM) it works better to reboot straight into the ROM's recovery, after step [5], and then do a factory reset there, then boot into the ROM and configure it, before having a modified step [6] - reboot to the ROM's recovery, and flash the vendor_boot OrangeFox using adb sideload.

There can sometimes be an amount of trial and error involved.

Nope. It is more complicated than this. You have to do a completely clean flash of crDroid (and GAPPs if you were using that) using the current vendor_boot OrangeFox. Then flash the standard OrangeFox, reboot to OrangeFox, format data, and then reboot to system. After this you can reboot to OrangeFox and restore the crDroid backup.

It is. Another Google bright idea ...

The most important thing to remember is that, once you are running a vendor_boot ROM, you must not flash a standard recovery until you have first flashed a standard ROM.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ext23:
Bloody hell OK. This is making me start to think the whole effort probably just isn't worth it. Just how good is Paranoid Android anyway? lol

Thanks, I tried my best but apparently didn't understand this bit properly.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
https://xdaforums.com/t/vendor_boot-roms.4575777/#post-88415981

I don't just imply. I state it categorically as a fact.

The most straightforward way to recover the brick for most people would be to flash a MIUI fastboot ROM, using the Mi Flash tool. This is of course a drastic solution (and people must be careful to not accidentally re-lock the bootloader in the process).

There is a less drastic solution, but this is not realistic for most people, because it involves already having some good, flashable images from the vendor_boot ROM (boot.img, dtbo.img and vendor_boot.img). For those who have them, all that is needed is to boot to bootloader, and then flash those images:

fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot reboot recovery

This should make both the vendor_boot ROM and its recovery bootable again.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] knowledge@heart:
Sorry if i came across in a wrong manner.

Lets say, Im on AOSPA right now which is a Vendor Boot ROM.

Now, if i wish to move to a non Vendor Boot ROM, say like LineageOS.

What should i do??

Normally, i would simply flash the lineage recovery and the ROM using the lineage recovery.

But now, in this case, how to i migrate from AOSPA to LOS? (safely)?

You replied "The most straightforward way to recover the brick.............."

I'm asking how to avoid the brick? What steps need to be taken?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Ok, I misunderstood your question. I thought you were asking what to do if you'd already bricked your device.

The answer to your question is here:

https://xdaforums.com/t/vendor_boot-roms.4575777/#post-88415981
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Akitake:
Been on this rom since May 3rd (Topaz Stable) from paranoidandroid.co and I can't say I've faced a single issue, even rooted without trouble. Still the smoothest experience I've had and probably also the best battery life I've had on Poco F3 across lots of roms!

That said there's no instructions on the website and this post really sucks with that, so newbies beware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] grret:
Nice ROM unfortunately snapchat doesnt work. Only big bug but dealbraker for me.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Moiap:
For now great rom, smooth and good bb.

The only problem i face is some games don't work (magic arena, icewind dale, slay the spire..) anyone knows how to fix? Just put a black screen and goes to launcher
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ApexPrime:
Try changing kernel
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Moiap:
Wich one is recommended?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ApexPrime:
Try infinir or realking. If rooted try nogravity and opmitize using its app
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Hexadiius:
Hello , about 2 weeks a go I installed this ROM , everything is amazing till I a got to the Google pay/nfc problem ,when I try to pay with my device the Google pay doesn't activate or when I open the wallet and press the card nothing happens, is this a bug ? Can anybody help me ? Thank you in advance
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nguyengk:
Can anyone help me, i was installing the rom using fastboot method with base rom miui eu latest. I ran the fastboot update install but always ended up with the error: fastboot: error: ANDROID_PRODUCT_OUT not set. Can anyone help me, thanks.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kusay_1:
Hey all.

wanted to share my experience with this ROM:

-wifi networks in initial setup took quite a while to pop up

-telegram instantly knew my phone number and i logged in without a code

-telegram couldn't install any apk,nor open a NOVA launcher backup file,but after downloading to phone storage and opening through a file manager did it work

-i couldn't find HIgh brightness mode,annoying notifications(notifs dont make a sound nor vibrations when screen is on),slide on status bar to change brightness not double tap on statusbar to sleep

-a LEICA camera integration would be very good

-in fastboot instructions i couldn't format using fastboot command,perhaps you should update it

thank you
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] muil:
I'm trying to sideload the orangefox vendor_boot recovery but I got a sign related error. Any solutión?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
What exactly is the "sign related error"? In any case, it should be possible to accept an invitation to ignore the error and proceed with the installation.

If you are not offered that option, then you can unzip the OrangeFox zip file, change to the directory into which it has been extracted, reboot to bootloader, and then run ".\flash-whole-image.bat" (this will flash the vendor_boot image using fastboot, and then it will boot into OrangeFox - at which point you can flash the OrangeFox zip with OrangeFox itself, so that all the OrangeFox support files are installed as well).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] muil:
Thx for your answer. It ended in error 21. Anyway, I could flash it by 'fastboot flash vendor_boot recovery.img' command extracting recovery.img from orangefox.zip
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
You mean "fastboot flash vendor_boot recovery.img"
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] healer99mak:
HBM fixed?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Akitake:
I've fallen off this ROM as I've started using Snapchat again, and this ROM still makes it impossible to do anything in the app.

Will come back once it's confirmed the fix has been added to alioth, as I've seen it exists and has been pushed to other devices on Telegram.

Using crdroid in the meantime but not nearly as happy with it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ronald Rosanes:
Trying to install via fastboot method but it goes to fastboot in the middle of the installation. Pls help.

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.003s]

Setting current slot to 'b' OKAY [ 0.009s]

extracting boot.img (96 MB) to disk... took 0.381s

archive does not contain 'boot.sig'

Sending 'boot_b' (196608 KB) OKAY [ 4.900s]

Writing 'boot_b' OKAY [ 0.261s]

extracting dtbo.img (8 MB) to disk... took 0.021s

archive does not contain 'dtbo.sig'

Sending 'dtbo' (8192 KB) OKAY [ 0.199s]

Writing 'dtbo' OKAY [ 0.026s]

archive does not contain 'dt.img'

archive does not contain 'pvmfw.img'

archive does not contain 'recovery.img'

extracting vbmeta.img (0 MB) to disk... took 0.000s

archive does not contain 'vbmeta.sig'

Sending 'vbmeta' (8 KB) OKAY [ 0.008s]

Writing 'vbmeta' OKAY [ 0.004s]

extracting vbmeta_system.img (0 MB) to disk... took 0.001s

archive does not contain 'vbmeta_system.sig'

Sending 'vbmeta_system' (4 KB) OKAY [ 0.007s]

Writing 'vbmeta_system' OKAY [ 0.004s]

archive does not contain 'vbmeta_vendor.img'

extracting vendor_boot.img (96 MB) to disk... took 0.286s

archive does not contain 'vendor_boot.sig'

Sending 'vendor_boot' (98304 KB) OKAY [ 2.325s]

Writing 'vendor_boot' OKAY [ 0.126s]

extracting super_empty.img (0 MB) to disk... took 0.000s

Rebooting into fastboot OKAY [ 0.004s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] muil:
Hi. I flashed the new orange fox 11.1-1 and got into bootloop. I can get still into recovery but reinstalling the rom ends in error 7 'Kinstalldeviceopenerror'. ADB Sideload install gives same error. Fastboot update doesn't work either. Any idea would be appreciated.

Update: solved the bad way, I had to format data.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] imonshahed:
New update when sir 😶‍🌫️
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] OneDiablo:
I dont understand why this guys don't update this rom omg....... Why he build this rom for don't give people update , wake gkandroid look nothing phone actually stable 6 rom .

So... @imonshahed if u want update with last update with patch month etc ...download here:

https://sourceforge.net/projects/xs-unofficial-builds/files/alioth/roms/a13/pa/dolby/aospa-topaz-unofficial-alioth-20230702.zip/download
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
Is this dirty flashable over the official build? If you post this info, I think it´s crucial to also provide this information. Otherwise people flash this and lose data if they didn´t do a backup before.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] OneDiablo:
Sry i only share the rom , it's not mine , i'm only a user.

I do a clean flash for secure with backup 🤷

Look like all rom i flash on m'y phone i do backup. especially when it's from official to unofficial or unofficial to official.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ultraschorsch:
I understand that you only want to share the updated ROM. But you need to put into consideration, that this is the official thread of Paranoid Android on XDA. And if someone installs the build from your link without reading, she/he will complain about lost data to the dev of the official ROM.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TweaknFreak:
So if I were to flash the Magisk APK from OrangeFox & then use "Direct Install" from the magisk app, will that root successfully? I'm asking since this is a vendor_boot ROM and I'm not used to these. Would really appreciate your thoughts :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] dtbs:
t

Tôi đã làm theo các bước như bạn nói. Tôi đã vào một vòng lặp vô tận

TỶ I followed the steps as you said. It doesn't work
[Nokia 3 Questions & Answers] gurtnyi:
Hi everybody,

A few days ago, I found a way to restore my Nokia 3, because it was dead (at least, I thought that). I flashed the ROM through brom mode, so it's working again. But there's a problem. After I made it up and running, I tried to root it and install TWRP, but I had a few errors, and when I reflashed it, accidentally formatted everything (SP Flash Tool Format all+download). Soo, I lost IMEI, and SN too. I successfully reflashed nvram partition, but I can't restore IMEI, and SN. I found the real SN from a previously opened CMD prompt, but I don't have an idea how to restore it. Unfortunately, with formatting everything, I also locked back the bootloader too, moreover I don't have a real SN on the device (123456789ABCDEF) so I can't unlock it through fastboot. I also made a ROM file for WwR to extract the ROM, so I have the nvdata, nvram, protect1, protect2 and other partitions (attached a picture of them), that 've been copied before fully wiping the device. I was wondering about, is it possible to reflash some partitions to get back the IMEI and SN, and with the real SN on the device unlock the bootloader again?
[Nokia 3 Questions & Answers] mvikrant97:
have you been able to fix it?
[Nokia 3 Questions & Answers] gurtnyi:
Fortunately yes, reflashed protect1, protect2, proinfo partitions from a full phone backup made earlier with WWR MTK (I guess that was its name)

For everybody, who's reading this cause having the same problem:

Instead of trying that as a method (you can, but do it on your own risk), write me a dm and I'll try to preapare some instructions for you iny free time.

Ps.: proinfo contains the SN, so with a hex editor, I was able to check my SN and I could probably rewrite it too.
[Nokia 3 Questions & Answers] tra_ung:
Can’t you help me. My phone is same. Lost imei. And sn is 0123456789ABCDEF
[Nokia 3 Questions & Answers] gurtnyi:
Do you have the original SN somewhere?

Original IMEI is located on the SIM trays.
[Nokia 3 Questions & Answers] tra_ung:
yes. i have got original IMEI
[Nokia 3 Questions & Answers] mvikrant97:
Please delete this IMEI.

Don't mention is here.
[Nokia 3 Questions & Answers] gurtnyi:
Yep, please delete it, it can be used to perform illegal actions.