Database Info

[GUIDE] QCN File for Redmi 4 Prime

Dear Xiaomi Redmi 4 Prime User.​
A Guy Name Dragonii Requested For a QCN File. and its Procedure. So now you Guys can restore IMEI by the Following Guide.
1: Download IMEI Converter.
2: Download QPST from here.
3: Download ADB Fastboot drive.
4: Download Qualcomm Driver.
5: Download NotePad++.
6: Download Redmi 4 Prime QCN File.
Follow the following steps to solve IMEI error on Redmi 4 Prime device :
1: Run Minimal ADB and Fastboot setup and following commands to enable diag mode.
adb shell
su
getprop sys.usb.config
OR​Dial on the Keypad - *#*#13491#*#*
2: Launch IMEI converter and enter Your original IMEI number and convert this number in a specific format. Same thing do for slot 2 IMEI and note down these converted string in notepad.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: Find this string in QCN file “08 8A 36 82 05 83 67 33 28” and replace with the number which you convert via IMEI converter tool.
4: Find again for sim slot 2 “08 8A 36 82 05 83 67 33 09” and replace with the string which you convert for SIM 2.
5: Again launch Minimal ADB and Fastboot and run Following commands.
adb shell
su
dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst1
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst2
dd if=/dev/block/mmcblk0p20 of=/sdcard/fsg
These commands will create a backup of the existing images.
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p20
reboot
These commands will wipe off the modemst1 modemst2 and fsg partitions.
6: Again follow first step to enable diag mode.
7: Now run QPST software and select the Ports tab.
8: You should see the port added automatically.
9: Now Click on the Start Clients option on the Top Menu bar. and select Software Download.
10: Click on the restore tab and then browse to the file that you just saved.
11: Now click the start Button.
12: Once it is done Reboot your system and You should have your IMEI restored.

Some corrections needed:
- The keypad code to trigger diag mode is *#*#13491#*#* on the Redmi 4 Prime
- Step 3: the dummy IMEI codes are 800000000000000, both for SIM1 and SIM2
- To edit the QCN file, you should NOT use Ultraedit but Hex Editor to keep the original file format intact
- Step 10: you probably have to check the box "Allow phone/file ESN mismatch" (I don't remember anymore if I had to do it) if you encounter an error when restoring
Thanks for the effort!

Useful guide, a lot of people asking for QCN files lately...

Just a heads up that messing with the imei is illegal in many countries and even owning the tools to do it is a crime. As such xda has banned all talks about how to do it.
There are only 2 acceptable ways on xda.
1. Restore the backup that you should have made or flash stock rom
2. Return to oem to fix

Brich phone
I follow all steps, and after theese commands:
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p20
reboot
my phone is dead ((
what happened?

Please help

onogost said:
Please help
Click to expand...
Click to collapse
Now what is the current status of your mobile.
Do you get Fastboot mode? Or EDL? Do you have unlocked bootloader?

SAFI_AFRIDI said:
Now what is the current status of your mobile.
Do you get Fastboot mode? Or EDL? Do you have unlocked bootloader?
Click to expand...
Click to collapse
I managed to revive my phone (through EDl mode, qualcomm 9008 port, mi flash). After that, I found another Redmi 4 Prada phone, done a backup qcn file, then restore that qcn file on my redmi 4 Prada phone. Now it's Baseband ok, IMEI is ok, phone recognizes my SIM card, but I still do not have bluetooth, wifi, fingerprint, gps ....

onogost said:
I managed to revive my phone (through EDl mode, qualcomm 9008 port, mi flash). After that, I found another Redmi 4 Prada phone, done a backup qcn file, then restore that qcn file on my redmi 4 Prada phone. Now it's Baseband ok, IMEI is ok, phone recognizes my SIM card, but I still do not have bluetooth, wifi, fingerprint, gps ....
Click to expand...
Click to collapse
Basically i posted this for redmi 4 prime and you need to follow a prada device. Following is the link.
http://en.miui.com/thread-2100147-1-1.html

@SAFI_AFRIDI I can't find my phone on any port in step 7

DannGD said:
@SAFI_AFRIDI I can't find my phone on any port in step 7
Click to expand...
Click to collapse
Repeat step one or enter the device in diag mode first.

SAFI_AFRIDI said:
Repeat step one or enter the device in diag mode first.
Click to expand...
Click to collapse
I've already tried this before step 7
adb shell
su
getprop sys.usb.config
OR
Dial on the Keypad - *#*#13491#*#*
there's no phone in any port

DannGD said:
I've already tried this before step 7
adb shell
su
getprop sys.usb.config
OR
Dial on the Keypad - *#*#13491#*#*
there's no phone in any port
Click to expand...
Click to collapse
Check Device Manager wether there is any port detected or not?

SAFI_AFRIDI said:
Check Device Manager wether there is any port detected or not?
Click to expand...
Click to collapse
There's a Qualcomm usb composite device 901D in device manager with a yellow box of warning

DannGD said:
There's a Qualcomm usb composite device 901D in device manager with a yellow box of warning
Click to expand...
Click to collapse
Your Device is connected but there is a problem in your Driver. Please uninstalled it and install it again

SAFI_AFRIDI said:
Your Device is connected but there is a problem in your Driver. Please uninstalled it and install it again
Click to expand...
Click to collapse
I updated and finish the steps... I restore my imei... But still without service

DannGD said:
I updated and finish the steps... I restore my imei... But still without service
Click to expand...
Click to collapse
Strange. Now given a try by resetting it. It might work.

SAFI_AFRIDI said:
Strange. Now given a try by resetting it. It might work.
Click to expand...
Click to collapse
Nothing

@SAFI_AFRIDI I figure out that my MEID number is wrong, do you Know any way to change it ?

DannGD said:
@SAFI_AFRIDI I figure out that my MEID number is wrong, do you Know any way to change it ?
Click to expand...
Click to collapse
Just copy the original IMEI code from mobile box. And repeat the above method and another thing you can do is just flash another modem via twrp and check it.

[GUIDE] How to Downgrade / Unbrick /Flash Stock Firmware Nokia 5.1 Plus.

This guide is for downgrading /Unbrick /Flash Stock Firmware Nokia 5.1 plus to Android Pie or Oreo.
This is STRICTLY for Global Nokia 5.1 plus variant NOT for Chinese variant Nokia X5. If you want to downgrade Chinese variant then follow this guide by hikari_calyx
Guide For Chinese Variant (X5).
What you need ::
1.MTK- Smart Phone Flashing tool which can be downloaded here. (v5.1804) Download
2.Android platform tools and ADB and fastboot drivers . Download
3. MTK Port drivers , For windows only. Download
4.FIRMWARE -
Oreo - PDA-1100-0-00WW-B01_unpacked.7z from . Download
Pie - PDA-214A-0-00WW-B01.full.zip from here . Download
STEP 1 : Backup your important files from internal storage and remove all google accounts from your phone to prevent FRP lock.
STEP 2 : Install all drivers and files mentioned above and extract your desired Firmware .
STEP 3 : Create a full backup using SP Flash tool (must do).
Open Smart Phone Flash Tool, choose the Download Agent file and Scatter File from the unpacked firmware.
DO NOT USE DOWNLOAD AGENT FROM THE FLASH TOOL ITSELF, USE ONLY THE ONE PROVIDED IN THE FIRMWARE.
Should look like this-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TROUBLESHOOTING.
If you get this error
Then go to options and disable "Check LIB DA Match".
Click to expand...
Click to collapse
Then move to "Readback" and tap on add and choose you location where you want save you backup after that you double click on the created readback section and you will see this :
Use any text editor to open the scatter file from extracted firmware , and find "userdata". You'll need the start address of userdata as the length of the full backup.
And change the length from the address you found under "userdata" in scatter file like this and tap ok.
Click on "Readback" and the connect you phone in flashing mode with both volume button pressed and release upon the readback process starts ( you can see it in the lower progress bar).
STEP 4 : Upon completion of the readback process , close SP Flash tool and unplug you phone and trigger it to fastboot mode and change your Active partition to "a" by this command.
Open cmd to use this command.
Code:
fastboot --set-active=a
After this process completes , power off you phone .
STEP 5 : Flashing your firmware.
Open SP Flash Tool and check that DA and Scatter is loaded from your extracted Firmware.
Choose "DOWNLOAD ONLY" mode , not any other or you will loose important partitions.
Then click on download and connect your phone in flashing mode by both volume button pressed and release upon the download process starts ( you can see it in the lower progress bar).
After its finished, it will show "Download OK" popup.
Now just close SP Flash tool , unplug you phone and reboot.
Enjoy your downgraded/ Unbricked Nokia 5.1+.
Special thanks to :
hikari_calyx for Firmware and solving all the errors.
Someone , Someone and Someone for testing this guide.
Hit Thanks if it worked for you.

Tested, guide works perfectly. Also, the given Android version in this guide is 9 (February SP) for those who want to know.

For some reason, the wifi doesn’t work for me, it just falls off and connects again (how to fix it?

Pelmewek said:
For some reason, the wifi doesn’t work for me, it just falls off and connects again (how to fix it?
Click to expand...
Click to collapse
Check your imei and baseband...is it there???

Readback not processing
Cant compltete the readback prccess what should i do?

xdriv3r said:
Cant compltete the readback prccess what should i do?
Click to expand...
Click to collapse
Which version of SP flash tool are you using ??

bx2_nero said:
Which version of SP flash tool are you using ??
Click to expand...
Click to collapse
I used the latest version. I'm going to try again with the recommended version. Thank you .

xdriv3r said:
I used the latest version. I'm going to try again with the recommended version. Thank you .
Click to expand...
Click to collapse
Use Sp flash tool version 5.1804 or 5.1824.
Read the instructions carefully ..

How to backup using sp flashtool?
How to backup using sp flashtool?
bx2_nero said:
Use Sp flash tool version 5.1804 or 5.1824.
Read the instructions carefully ..
Click to expand...
Click to collapse

xdriv3r said:
How to backup using sp flashtool?
Click to expand...
Click to collapse
You must backup your personal data and remove Google account before starting.
The readback process is the backup process in SP flash tool.

Android 10 firmware not available
bx2_nero said:
Pie-PDA-214A-0-00WW-B01.full.zip from here https://androidfilehost.com/?fid=1899786940962585502 (recommended if you are downgrading to root and install Androdi 10).
Click to expand...
Click to collapse
Alas, no mirror found:

mll2 said:
Alas, no mirror found:
Click to expand...
Click to collapse
https://tpedutw-my.sharepoint.com/:...dFks--5G6V4vYBGTwLw1BsthbtIuJqMUN3tQ?e=wOfytH
Try from here
Make sure you download the file mentioned.
PDA_214A_0_00WW_B01_full

bx2_nero said:
https://tpedutw-my.sharepoint.com/:...dFks--5G6V4vYBGTwLw1BsthbtIuJqMUN3tQ?e=wOfytH
Try from here
Make sure you download the file mentioned.
PDA_214A_0_00WW_B01_full
Click to expand...
Click to collapse
Thank you!

I tried downgrading from Android 10 Internal Beta and cannot skip the update screen on reboot. How to fix this?

xdriv3r said:
I tried downgrading from Android 10 Internal Beta and cannot skip the update screen on reboot. How to fix this?
Click to expand...
Click to collapse
Did you follow step 1 - remove Google account to prevent FRP Lock.
Try hard resetting, reset from recovery.

bx2_nero said:
Did you follow step 1 - remove Google account to prevent FRP Lock.
Try hard resetting, reset from recovery.
Click to expand...
Click to collapse
It's just one compulsary update. Around September 2019 sp. I'm good now. I thought I had hardbricked the device when I changed primary partition to b and got stuck in bootloop unable to go into recovery. Then I used volume down + power and usb to directly get into fastboot.

xdriv3r said:
It's just one compulsary update. Around September 2019 sp. I'm good now. I thought I had hardbricked the device when I changed primary partition to b and got stuck in bootloop unable to go into recovery. Then I used volume down + power and usb to directly get into fastboot.
Click to expand...
Click to collapse
Why did you changed your primary partition to B.

bx2_nero said:
Why did you changed your primary partition to B.
Click to expand...
Click to collapse
I'm noob.

xdriv3r said:
I'm noob.
Click to expand...
Click to collapse
Your phone is fine right now?

bx2_nero said:
Your phone is fine right now?
Click to expand...
Click to collapse
Yeah now on feb sp with mtksu and suboot.

:: Cubot Quest { get rid off annoying red watermark "not verify" } ::

Morning all... after spending almost a whole day to solve a very annoying issue to my Cubot Quest smartphone I decided to write here a short procedure hoping to save headaches in future
When flashing from SP_Flash_Tool can happen that after formatting all partitions and installing/upgrading a new firmware both IMEI are lost and when you reboot the device you have a very annoying red watermark that sounds: not verify
so the only way to get rid off that red line/watermark is to reflash imei + correspondant google key
ATTENTION: this method works and was tested only for Cubot Quest
so let's hope to save someone from future headache:
0. turn off device and do NOT plug
1. download (and unzip) latest stock firmware/rom from cubot website: https://www.cubot.net/platform/Support/detail/id/129/cid/16.html
2. download (and unzip) latest SN Write Tool: https://androidmtk.com/download-sn-write-tool (look at the bottom of the page)
3. launch SN_Writer.exe (from SN Write Tool decompressed folder)
4. go to "Key Files" in the program menu >> Attestation Key >> Attestation Key & browse in the decompressed ROM folder looking for file: a798_cq_8123c_62_p0_0_100000_S1220.bin >> OK
5. go to "system config" , ensure that on left is checked just "IMEI" and at the bottom "Dual IMEI" (do NOT check other options)
6. at the bottom in Database section check "Load Modem DB from DUT"
7. always at the bottom in AP_DB look for file in the ROM folder: APDB_MT6765_S01__W1925 (pay attention do NOT choose APDB_MT6765_S01__W1925_ENUM)
8. save
9. click Start & give correct/correspondant IMEI1 and IMEI2 (they are printed in the device's box, but if you have lost the box I think could work also a fake imei)
10. plug the device and flashing will start in few seconds, wait and if all goes as should be a green pass warning should appear in the program
11. turn on the device and the red watermark should be vanished
anyway with correspondant/correct files the same procedure should work for almost all Cubot devices with the same issue, both files (point 4 & 7) are in the rom folder
ps: do not "play" with SN Write Tool... you can brick the device
Regards,
Davide

suiller said:
Morning all... after spending almost a whole day to solve a very annoying issue to my Cubot Quest smartphone I decided to write here a short procedure hoping to save headaches in future
When flashing from SP_Flash_Tool can happen that after formatting all partitions and installing/upgrading a new firmware both IMEI are lost and when you reboot the device you have a very annoying red watermark that sounds: not verify
so the only way to get rid off that red line/watermark is to reflash imei + correspondant google key
ATTENTION: this method works and was tested only for Cubot Quest
so let's hope to save someone from future headache:
0. turn off device and do NOT plug
1. download (and unzip) latest stock firmware/rom from cubot website: https://www.cubot.net/platform/Support/detail/id/129/cid/16.html
2. download (and unzip) latest SN Write Tool: https://androidmtk.com/download-sn-write-tool (look at the bottom of the page)
3. launch SN_Writer.exe (from SN Write Tool decompressed folder)
4. go to "Key Files" in the program menu >> Attestation Key >> Attestation Key & browse in the decompressed ROM folder looking for file: a798_cq_8123c_62_p0_0_100000_S1220.bin >> OK
5. go to "system config" , ensure that on left is checked just "IMEI" and at the bottom "Dual IMEI" (do NOT check other options)
6. at the bottom in Database section check "Load Modem DB from DUT"
7. always at the bottom in AP_DB look for file in the ROM folder: APDB_MT6765_S01__W1925 (pay attention do NOT choose APDB_MT6765_S01__W1925_ENUM)
8. save
9. click Start & give correct/correspondant IMEI1 and IMEI2 (they are printed in the device's box, but if you have lost the box I think could work also a fake imei)
10. plug the device and flashing will start in few seconds, wait and if all goes as should be a green pass warning should appear in the program
11. turn on the device and the red watermark should be vanished
anyway with correspondant/correct files the same procedure should work for almost all Cubot devices with the same issue, both files (point 4 & 7) are in the rom folder
ps: do not "play" with SN Write Tool... you can brick the device
Regards,
Davide
Click to expand...
Click to collapse
Hello,
I have the not write Googlekey/not write TEE watermark on top of the screen, the device is a Blackview Max 1. It happened after unbricking it , flashed the stock rom with flashtool.
What's the bin file I should look for?
I saw a method replacing systemui apk in priv-app folder but it corrupts my system ui, no nav bar and no top pulldown notification bar. So I don't know what to do, I have even rooted it patching the boot file.
Let me know for more advice, I will try your posted method. Thanks

Morphine1 said:
What's the bin file I should look for?
Click to expand...
Click to collapse
honestly I dunno...
but you don't have many .bin files and the dimension isn't big... about 10k, should be easy to identify it

Hey,
Thanks for the help, I have a Cubot QUEST too, I followed your steps and recovered my IMEI from the box however i still have the red NOT VERIFY text, the IMEI is recovered so im not sure what is left to do.
Any suggestion?

tragidyx said:
Hey,
Thanks for the help, I have a Cubot QUEST too, I followed your steps and recovered my IMEI from the box however i still have the red NOT VERIFY text, the IMEI is recovered so im not sure what is left to do.
Any suggestion?
Click to expand...
Click to collapse
What's your Serial Number like?

Morphine1 said:
What's your Serial Number like?
Click to expand...
Click to collapse
It's messed up like Abcde1234

same here still have the watermark cubot quest

im joining you with my dogee s88 pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi!
It works for the Ulefone Armor X6.
Although I had to flash the Stock-ROM V1 before I succeeded.
After that I managed to get rid of the message.

This method helped me. I can recommend for everyone, if you have root accces of course.
Sadly, what you described here are not worked for me, because every time when I did that, it failed. But it's a good try.

Here's another possible fix if you have magisk with zygisk support! It has to do with dynamically turning the ro.mtk_tee_check_support build prop to 0. More here https://forum.xda-developers.com/t/not-verify.3870242/post-87713751.

Same like my doogee android, after flash, i just want red mark on top screen gone, but i like dont have imei because this phone from another country if i have imei this phone not work

Error after update firmware

no one has encountered such an error when updating to firmware
L79031_ROW_SECURE_USER_Q00114.1a_Q_ROW_12.0.332_ST_210202_qpst.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How did you get the update? Did you install it yourself from the rescue application. Or did you upload with q file

I uploaded with QPST_2.7.496.zip

LeshaRB said:
I uploaded with QPST_2.7.496.zip
View attachment 5236277View attachment 5236279View attachment 5236281View attachment 5236283View attachment 5236285
Click to expand...
Click to collapse
go to edl mood by holding volume up and volume down button when restarting phone
now use flat build instead of meta build

mrgreapes said:
go to edl mood by holding volume up and volume down button when restarting phone
now use flat build instead of meta build
Click to expand...
Click to collapse
Can you help?
What I must choose in RawProgramm & Patch??
I have such rawprogramm
"rawprogram_unsparse0.xml"
"rawprogram_unsparse0_retain_userdata.xml"
"rawprogram1.xml"
"rawprogram2.xml"
"rawprogram3.xml"
"rawprogram4.xml"
"rawprogram5.xml"
And patch
"patch0.xml"
"patch1.xml"
"patch2.xml"
"patch3.xml"
"patch4.xml"
"patch5.xml"

mrgreapes said:
go to edl mood by holding volume up and volume down button when restarting phone
now use flat build instead of meta build
Click to expand...
Click to collapse
II tried to reflash to FlatMode and again the CrashDump error
May be problem in - Erase all before download?

LeshaRB said:
Can you help?
What I must choose in RawProgramm & Patch??
I have such rawprogramm
"rawprogram_unsparse0.xml"
"rawprogram_unsparse0_retain_userdata.xml"
"rawprogram1.xml"
"rawprogram2.xml"
"rawprogram3.xml"
"rawprogram4.xml"
"rawprogram5.xml"
And patch
View attachment 5237811
"patch0.xml"
"patch1.xml"
"patch2.xml"
"patch3.xml"
"patch4.xml"
"patch5.xml"
Click to expand...
Click to collapse
chose
rawprogram_unsparse0
then 1 2 3 4 5
select the patch files from 0 to 5

mrgreapes said:
chose
rawprogram_unsparse0
then 1 2 3 4 5
select the patch files from 0 to 5
Click to expand...
Click to collapse
do not chose both rawprogram_unparse0 files

LeshaRB said:
II tried to reflash to FlatMode and again the CrashDump error
May be problem in - Erase all before download?
View attachment 5237833
Click to expand...
Click to collapse
settings are ok

LeshaRB said:
II tried to reflash to FlatMode and again the CrashDump error
May be problem in - Erase all before download?
View attachment 5237833
Click to expand...
Click to collapse
if still in crash dump mood then switch your mobile into edl mode go to tools in qfil tool click on file manager select persist partition erase it then click on load and chose the persist partition from your rom folder also delete "modem" partition and load NON_HLos.bin from your rom files folder and then turn on your phone

mrgreapes said:
if still in crash dump mood then switch your mobile into edl mode go to tools in qfil tool click on file manager select persist partition erase it then click on load and chose the persist partition from your rom folder also delete "modem" partition and load NON_HLos.bin from your rom files folder and then turn on your phone
Click to expand...
Click to collapse
in this case you are gonna lose your imei then you have to restore it using qcn file

i have found a solution for those who have lost imei after flashing or for those who want to change imei
here is the link to qcn file Enjoy i have removed my imei from it you can add yours by using this tool : https://mega.nz/file/LixWmY5T#ki4MXHtf0XKNovI7Iz3DQ8o2inrIPc3aTDgrwE_WpcI
QCN : https://mega.nz/file/yypwHQLC#96sIs97z_nkOSyn8U7U-1bRikrk1ipBDt2HFcXb1sLY
use the below guide to restore imei and everything you have lost : https://forum.xda-developers.com/t/guide-backup-edit-and-restore-qcn-fixing-lost-imei.4101611/

mrgreapes said:
i have found a solution for those who have lost imei after flashing or for those who want to change imei
here is the link to qcn file Enjoy i have removed my imei from it you can add yours by using this tool : https://mega.nz/file/LixWmY5T#ki4MXHtf0XKNovI7Iz3DQ8o2inrIPc3aTDgrwE_WpcI
QCN : https://mega.nz/file/yypwHQLC#96sIs97z_nkOSyn8U7U-1bRikrk1ipBDt2HFcXb1sLY
use the below guide to restore imei and everything you have lost : https://forum.xda-developers.com/t/guide-backup-edit-and-restore-qcn-fixing-lost-imei.4101611/
Click to expand...
Click to collapse
just add your imei using this above mentioned software then dial
*#*#33284#*#*
you will see a menu
click on qmi test
you will see a port with the name of 901D or 91D in qfil tool then just go to tools backup and restore qcn enable multi sim option and restore the qcn file i have provided after this your fingerprint + y triggers are gonna stops working but everything else is going go work fine do at you own risk

mrgreapes said:
do not chose both rawprogram_unparse0 files
Click to expand...
Click to collapse
Hello, I had the same problem and I did the same explanation on my phone, but it was stopped on the black screen. It does not work and does not respond to the computer. Is there a solution??

How To Guide Guide to Remove Orange State Error Fix For Realme GT Neo 2 (Android 13 RUI 4.0)

Guide to Remove Orange State Error Fix
Tested on Indian region
(May not work on another region)
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS IS DONE BY YOUR OWN JUDGEMENT IF YOU WANT TO DO THIS OR NOT.
It's possible to flash. Modified partition/image file without a bootloader unlock but I'm not 100% positive. .
Requirements:-
Qfil Tool (QPST)
Qualcomm EDL Mode Drivers
Firehose Programmer SDM870
abl.img (new edited)
Steps:-
Step 1: Download the given files.
Step 2: Install Qfil (QPST)
Step 3: Make sure you go to configuration then firehose settings and change from emmc to ufs and do the same as shown in below image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4: Turn off your phone and boot into edl mode
Step 5: Install the Qualcomm drivers by right clicking on the qbulkhub thing and click properties then the driver tab click update then search automatically.
Step 6: Open Qfil tool then load the firehose file in programmer path
Step 7: don't worry about the XML path and stuff just go on the top click tools and partition manager
(NOTE: if there's no port open or the partition manager won't open, try rebooting into edl mode again)
Step 8: Window should pop up with a list of partitions, right click on the abl that you want to flash and then click on Manage Partition Data option then click on Erase option (abl partition will be erased) then click on load image and select and load the given abl.img file
Step 9: Exit from the Qfil tool
Step 10: Reboot your phone
Enjoy!

@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
​

nikoum said:
@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
​
Click to expand...
Click to collapse
What firmware version were you on before you fixed orange state?

ESD444 said:
What firmware version were you on before you fixed orange state?
Click to expand...
Click to collapse
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09

nikoum said:
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09
Click to expand...
Click to collapse
So following this post you got rid of orange state?

ESD444 said:
So following this post you got rid of orange state?
Click to expand...
Click to collapse
He is saying he got orange state after updating to rui 4 Android 13 "not in Android 12"

Just to inform anybody, I received a new update RMX3370_11_F.03 and after the update I got the orange state warning back again. So I had to apply the fix again.

Yes you have to apply it again

hi,
i'm triying to fix this orange state problem but can't find abl partition in partition manager, can you please tell me what is the partition i have to erase and flash?
Edit: Ok in fact i don't have to check "customize fysical partition" in configuration. abl is in LUN 4 but i only seen LUN 0 when this case is check.