Database Develop

[Q] flashed rom now Phone Number is 000000000 in About Phone

Is this an easy fix, or just ignore it?
Thanks

Desd1nova said:
Is this an easy fix, or just ignore it?
Thanks
Click to expand...
Click to collapse
you can ignore this, it says nothing
but maybe delete this numbers in build.prop

Sorted!
Turns out I'd forgotten I'd had a replacement sim and they hadnt done it their end. Asked EE for a network refresh and now its back
Thanks!

WiFi NVRAM WARNING err 0x10 in wifi

Hi, I don't remember exactly when this started, but its been a few months. Pretty much when I go to my wifi settings one of the available wifi networks is named "WiFi NVRAM WARNING err 0x10". By now its obvious its something about the phone and not an actual network, but what is causing this and is there a way to fix this? Thanks!

lil chickenz said:
Hi, I don't remember exactly when this started, but its been a few months. Pretty much when I go to my wifi settings one of the available wifi networks is named "WiFi NVRAM WARNING err 0x10". By now its obvious its something about the phone and not an actual network, but what is causing this and is there a way to fix this? Thanks!
Click to expand...
Click to collapse
This is from a lost or corrupted nvram data.
Is you phone imei correct?

How do I check if it's correct?

I used some online thing and it looked normal except it said it was for r1 hd 2018 and I bought mine in 2017. Does that matter?

lil chickenz said:
How do I check if it's correct?
Click to expand...
Click to collapse
the numbers are on the box the phone came in , And on stick that covers the battery.
I did just mean that it had numbers and not all 000
Are you on one of the stock roms, or some custom one?

Yeah it was a bunch of numbers so normal, and im not using the rom that came with the phone but I'm using a stock one another user posted

The original 6.1 from here https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672

mrmazak said:
the numbers are on the box the phone came in , And on stick that covers the battery.
I did just mean that it had numbers and not all 000
Are you on one of the stock roms, or some custom one?
Click to expand...
Click to collapse
I also ran the debloat script but I don't think it should matter

lil chickenz said:
I also ran the debloat script but I don't think it should matter
Click to expand...
Click to collapse
I had only seen this issue after "format all" was done in spft. or when testing some Lineage ports. And on the posts it only happened with a phone that used my bootloader roll-back script.
Did you do the bootloader roll-back?
If so , will need to search back in the forum to see when this was posted and what fix i used.
this was post i was refering to. Not sure if it is gonna be same or similar to your current issue, but read it and perhaps give it a try. But remember any thing you modify can break your device further or fix it, There are no guarantees here .
https://forum.xda-developers.com/showpost.php?p=73231462&postcount=99

[Crossflash] - AT&T V405UA10 to Korean V409NUA

Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.

Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg

77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.

abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?

oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here

abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?

oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish

This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers

abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.

advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers

AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.

advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.

advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up

AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.

So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers

abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI

So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers

Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?

fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers

Thanks man!

Current Version is not available for user. Error on startup.

Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.

Gurkenbeat said:
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Click to expand...
Click to collapse
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers

Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?

Gurkenbeat said:
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Click to expand...
Click to collapse
No

AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?

FreeSoftwareServers said:
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
Click to expand...
Click to collapse
No, it doesn't cause safetynet to fail, they are completely different things.

AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
What partitions do I select?

blowtorchhonor said:
What partitions do I select?
Click to expand...
Click to collapse
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers

AsItLies said:
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
Click to expand...
Click to collapse
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.

blowtorchhonor said:
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
Click to expand...
Click to collapse
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.

blowtorchhonor said:
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
Click to expand...
Click to collapse
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers

AsItLies said:
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
Click to expand...
Click to collapse
I was using an outdated common DLL, thanks for helping me! Let's see if this works!

blowtorchhonor said:
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
Click to expand...
Click to collapse
Nope

I have this message that pops up on my V450VM. I assume it was related to Navigation Gestures that I used, and loved, on my V405QA7. When activating and setting it up, my V50 downloaded Nav Gestures from backup and when the phone updated to A11 I found the app was incompatible. I deleted the app and key. Ever since, rebooting has brought up the notification and I assume something didn't delete from the app. Guess I may have been wrong. I'm living with it and it doesn't seem to cause any issues but my OCD flares everytime :/

Question Redmi note 10 5g engineering firmware

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