Develop Bugs

Managed to Root Xtouch X817 Tablet (Rooting method should work on all xtouch)

Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
{
"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"
}
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg

Well Done!
ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.

irisgenx said:
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.
Click to expand...
Click to collapse
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted

ananjaser1211 said:
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted
Click to expand...
Click to collapse
Okay Thanks brother. I don't have access to the tablet as of now. When I get it back , I will try this and bug you again if there's any issue.
Thanks for the WiFi tip too. I'll see if that connection is maybe damaged.

ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi

xinixi said:
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi
Click to expand...
Click to collapse
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet

ananjaser1211 said:
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet
Click to expand...
Click to collapse
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:

xinixi said:
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:
Click to expand...
Click to collapse
I just checked the UAE site. and yeah apperantly they removed the device . pretty bad, but i think if you contacted the support they may give you the link to the download site ( it is in Chinese so i don,t really think you will find it in ease)
I had the files before but the HDD the contains them died.

Asus Zenfone 2 Imei repair way with Rezasedgi!

hello , all of you.
i'm from Iran and i repair my imei successfully!
i want to share my solution way to you , my dears!
if your imei repaired with my way , please pray for me.
solution:
you need to use digma sofia (phone tool 191).
first , root your phone.
second , install intel drivers for your pc
thirth , use adb to set your phone to diag mode.with this command: adb shell
su (after enter this , grant supersu from phone)
setprop system.at-proxy.mode 1(1 for sim 1 and 3 for sim2)
After this commands , in pc's device manager , you see the intel virtual android port.if you see , continue.
open phone tool and use it with sofia's pdf help(use google:repair imei asus zenfibe 2 and find digma sofia (phonetool).
Note:for who persons that port dont open (freeze in settings(1/3) : You are using android 6.Yes?!
Android 6 dont allow to ports to open.you will need to downgrade to android 5.just in android 5 you will be able to use phone tool and ports will be active.
My this Note , saves you life , man.yes?!i tried one week in android 6 and ports Dont active.Dont try my brother.just Downgrade to 5 and use phone tool.
Downgrade:
Download this downgrade firmware with your pc and transfer it with cable to your phone.unplog cable and system will be show notification to update.accept it.or you can use adb sideload or use sd card update wia recovery.just flash that downgrade zip file and you will be in lollipop.after use phone tool in lollipop and repair imei with that , upgrade to marshmallow again with above way and use factory reset after upgrade!
Downgrade m to l firmware:
search google: how to downgrade asus zenfone 2 and download UL-Z00A-WW-52.20.40.196-user.zip from asus site.
Note: for sim 1 , use setprop 1 and for sim 2 , use setprop 3
i'm from iran!

Rollback EMUI from 10 to 9 to bypass FRP

Hi all,
Got a mobile that we dont know the previous Gmail account this was registered with. Therefore, I need to bypass the FRP to recover the mobile and use it for testing purposes. Accidentally, I upgraded it to EMUI 10 and after fixing several softbricks, I have no clue how to downgrade it to EMUI 9.
Goals:
Rollback EMUI 10 to 9 on Huawei 20x C185
Abuse flaws on EMUI 9 to bypass FRP
Do all via Linux tools (preferably console)
Firmware
EVR-L29 C185 EMUI 10
https://mega.nz/#F!zRUGFKyZ!je09cCOdJRPePDvykLwJCQ
http://www.mediafire.com/file/m7l6xlqe4se0u7s/dload.zip/file
Fail attempts
Enter upgrade mode and dload a previous C185 EMUI 9.0.x or EMUI 9.1.x (via OTG cable + microSD card). This always produces the same error: Software upgraded failed!
Try to change country to have chances to flash different firmware.
Logs:
Code:
> fastboot oem get-build-number
...
(bootloader) :EVR-L29 10.0.0.180(C185E6R3P3)
OKAY [ 0.011s]
finished. total time: 0.011s
> fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
Any idea?

Try Hisuite

sunrider07 said:
Try Hisuite
Click to expand...
Click to collapse
hey @sunrider07,
apparently you need to enable HDB options to use HiSuite, right? Tested HiSuite on Linux emulated via Wine. I was able to use the Huawei tool but I couldn't hook up the mobile to the app. Have you used HiSuite to downgrade the bootloader? If so, it is really needed to have adb connection? Remember my phone is protected via FRP.
This is the way to enable HDB (Huawei ADB dev options):
4. Go to device setting and enable USB Debugging. You can follow our guide on how to enable USB Debugging on Huawei phones.
5. Connect HiSuite to your mobile.
6. HiSuite will automatically shows a system update on your device.
Click to expand...
Click to collapse
Being blocked by FRP, HDB switch cannot be enabled so i am not sure if HiSuite can be used
{
"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"
}

My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected

sunrider07 said:
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, I do need to find another way to perform a downgrade on the bootloader and base image to EMU 9.0 where there are public and known vulnerabilities to overcome FRP. Otherwise, I will need to wait until a FRP bypass is public, or reverse engineering the HiSuite software to find some fastboot commands to see if I can leverage any of these. It seems I am stuck with it.

Apparently I found this video from 5 days ago: https://www.youtube.com/watch?v=USvi-1O2Y6o
Anyone knows well the mode USB upgrade?

--

mac231us said:
I saw that too. I too need to downgrade but cannot as usb is not connecting. I can connect to one of the Hisuite versions through wlan option but it cannot be used to change the system (only through usb). Cannot do system recovery (says take it to service center)
Yes video shows if you go into usb mode through recovery (which I can) you can use the MRT tool to flash the rom. I plan to look into it. Otherwise I might just take it to a service center in an upcoming overseas trip (still almost 2 months away)
Click to expand...
Click to collapse
Do you know where to download this MRT tool? It seems like super unprofessional tool without github repo.
mac231us said:
Separately in my case-The device is not recognized when connecting through usb to the computer (usb ports, cable, windows version, drivers etc all tried-the device type and name is not recognized. OTG usb works but that is only for backups, backup restore and dload method to upgrade-which cannot be used to downgrade to 9.1 or 9.0 from 10.0) Fastboot commands are severely limited in 10 as my device country vendor is unknown. The device works fine otherwise (calls, mms, apps, internet, themes) Device cannot be registered at Huawei as unknown device though I can register in themes. With dload I can switch back and forth between 10.0.0.180 and 183 or even a lower 10 but not to 9 series.
Click to expand...
Click to collapse
Dont own a Windows10 laptop to use HiSuite, looking for one to see if I can connect it via WiFi. Did you mention you can use all these calls, mms, apps, internet, themes? In this case, we have different issue.
Can you run this command?
Code:
$ fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
mac231us said:
Surprised there is no way to fastboot erase and install firmware-I heard you need a service rom to completely redo the phone.
Click to expand...
Click to collapse
The MRT tool must use a fastboot command too. We can always reverse this tool to extract the command. Do you have the tool?

In this video there are downloading links:
MRT sw

--

anyone able to bypass the frp?

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

OnePlus 8 Pro (EU) - Repair from scratch guide... SMT - QC Flash, IMEI repair, fingerprint...

AS LONG AS PHONE CAN BE TURNED ON - WHETHER IT IS RECOVERY, FASTBOOT, QUALCOMM CRASHDUMP OR SOMETHING SIMILAR YOUR DEVICE CAN BE FIXED...
WARNING:
Regarding QC MSM Flash tool - make sure you back up persist.img before flashing device otherwise you won't be able to recover fingerprint sensor...
Regarding QC SP IMEI Write tool - You can only use IMEI that is on the box...
Your data will be lost, obviously...
This guide is for EU devices (download links have EU firmware), but it is applicable for other as well as long as you have required firmware...
Required stuff:
Download from GDrive
Passwords:
IMEI TOOL: ustest
MSM TOOL: te123
1.) Make sure to back up EFS, if you don't you will lose ability to make or receive calls.
If you didn't backup EFS that's not problem, I found temp. solution... After doing MSM SMT clean installation your imei wil be 0 but you will be able to make calls. At this point you MUST BACK UP: mdm1m9kefs1, mdm1m9kefs2, mdm1m9kefs3 and mdm1m9kefsc...
After updating your IMEI and OS to latest version you will lose ability to make or receive calls but, you can than do:
fastboot flash mdm1m9kef
fastboot flash mdm1m9kef
fastboot flash mdm1m9kef
fastboot flash mdm1m9kefsc
fasboot flashing lock_critical
...and boom your device is now fixed!!!
1. A) Backing up persist.img DIFFICULTY: 3/5
Download and extract: MSM TOOL 10.5.4, open "MsmDownloadTool V4.0.exe" -> Other -> Next
We're just gonna flash your OS so do not use SMT mode yet (If you don't know what is SMT mode then just follow steps)
Click on TARGET and select EU, click start and wait for it to say "Waiting for device", now when your device is powered off, hold volume up and volume down button and connect it to the cable, MSM should now start flashing your OS
After it's completed (around 5 minutes) you will be able to boot into OS, go to developer options (after setting up device), go to developer options and enable "OEM Unlocking"... Now update your system using local files: UPDATE 10.5.5 on GDrive (extract it, you are gonna find OnePlus zip FullOTA and magisk boot.img) and reboot to fastboot after update, connect your phone to adb and do "fastboot flash boot <magisk.img - from gdrive>" now set up magisk.apk and make sure root is working, go back to adb on your computer and run these commands:
adb shell
su (there will be pop-up and you need to grant root access to shell)
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
Now store that persist.img to your pc
1.B) If your device looks like this and you didn't back up persist.img you will have to play around because I don't know if you can get your fingerprint sensor back without it but if you do please let us know in the comments, you will need to flash using SMT mode...
{
"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"
}
To flash it via SMT, you need to open MSM V4.0 and click Verify, after you get MD5 Check... you need to click on SMT download mode
and now press SMT on top
then COM Setup and enable your ports. After you click start it will ask you for password: te123, and also you need to put your original storage size, now press volume up and down on your device and connect it to pc...
Your system will be flashed on chipset level...
2. Repair fingerprint sensor DIFFICULTY: 3/5
Follow steps on this video: Fingerprint Repair
But instead of holding finger on all test except BLACK RUBBER test, you need to hold it only when testing FLESH RUBBER, do not cover sensor with anything on other tests. And you should get red error saying: FAIL GF ERROR BAD POINT CLUSTER... and now you can proceed with copying data and engineermode to persist via root explorer (in GDrive) just like in the video...
3. Repair IMEI DIFFICULTY: 4/5
Download IMEI repair, open settings and input password: ustest, enable dual IMEI and write MEID as well... apply settings and connect your device,
go to dialer app and enter *#801# enable Diag,Adb and Serial, go to GDrive and download QC Important Driver.zip
Go to device manager and you should see your phone in COM/LPT section, IN2023 or something like that... There could be like two devices IN2023 and you must install this driver on both! Right click on it and select update driver, Browse computer>Let me pick...>Show All> Have disk and now go to qcser.inf_amd64 and select qcser.inf and click OK, from all the drivers from the list you need to select Qualcomm HS-USB Diagnostics 90B6 and now go to IMEI write tool and click Write. Your IMEI should now be written... You can go back to *#801# and disable diag,adb serial and you just need to restart device to reload new IMEI
Sources:
Repar IMEI
Fingerprint Repair

vrabaci said:
Qualcomm HS-USB Diagnostics 90B6
Click to expand...
Click to collapse
@vrabaci Can you specify the right Driver for the IMEI WRITE tool? There is no "Qualcomm HS-USB Diagnostics 90B6" , only "Qualcomm HS-USB MDM Diagnostics 90B6". "MDM" is missing from your post. Is that the right one?
I tried with this and IMEI WRITE tool say "Connecting to smart phone".... then Fails with timeout. It doesnt connect.
Can you help with connection?

mimix2ppp said:
@vrabaci Can you specify the right Driver for the IMEI WRITE tool? There is no "Qualcomm HS-USB Diagnostics 90B6" , only "Qualcomm HS-USB MDM Diagnostics 90B6". "MDM" is missing from your post. Is that the right one?
I tried with this and IMEI WRITE tool say "Connecting to smart phone".... then Fails with timeout. It doesnt connect.
Can you help with connection?
Click to expand...
Click to collapse
Yes that is the correct driver, check if there is another IN20223 in device manager there should be one in COM&LPT and one should appear like IN2023 or OnePlus (with yellow triangle), click on it and update driver to MDM906B

vrabaci said:
Yes that is the correct driver, check if there is another IN20223 in device manager there should be one in COM&LPT and one should appear like IN2023 or OnePlus (with yellow triangle), click on it and update driver to MDM906B
Click to expand...
Click to collapse
I did that many times... I still cannot connect....
setprop sys.usb.config diag,adb,serial​​OR *#801# , enable Engineer Mode and Serial​​both ways, no result.... write tool doesnt connect.​​Maybe the setprop doesnt work right? How do I check it?​​is there Another Write Tool I can use?​​also. I have a MEID found from system logs. but it says Parity Bit Error. does it mean that the MEID I found is wrong? is MEID necessary to have a working phone for sim/calls ?​​Also. what is interesting. Fingerprint works, persist.img survived the flashes. but IMEI and MEID etc are all wiped out. ​​any ideas...​

you should enable only serial and diag,adb, rest of them should be disabled...
i also used only this tool but i've been unsuccessful in finding new one

I
mimix2ppp said:
I did that many times... I still cannot connect....
setprop sys.usb.config diag,adb,serial​​OR *#801# , enable Engineer Mode and Serial​​both ways, no result.... write tool doesnt connect.​​Maybe the setprop doesnt work right? How do I check it?​​is there Another Write Tool I can use?​​also. I have a MEID found from system logs. but it says Parity Bit Error. does it mean that the MEID I found is wrong? is MEID necessary to have a working phone for sim/calls ?​​Also. what is interesting. Fingerprint works, persist.img survived the flashes. but IMEI and MEID etc are all wiped out. ​​any ideas...​
Click to expand...
Click to collapse
If you put your IMEI1/imei2 and MEID from the box it should not give any parity errors, also don't check save to access database and also I had IMEI 0 and MEID 0 and I could make calls so I don't think it's really required but I have no idea how that system works...

vrabaci said:
If you put your IMEI1/imei2 and MEID from the box it should not give any parity errors, also don't check save to access database and also I had IMEI 0 and MEID 0 and I could make calls so I don't think it's really required but I have no idea how that system works...
Click to expand...
Click to collapse
I dont have the box........ only what I find from filesystem.....
can you check this file in your phone /mnt/vendor/persist/engineermode/engineermode_config to see if the IMEI there is the correct IMEI1 of your phone?
can you check /data/opdiagnose and search for "meid" with ripgrep https://github.com/BurntSushi/ripgrep , "rg -i -M 1000 meid" command. is the meid in these logs the same as your real MEID?
also. How long was "Connecting to the smart phone" in Write Tool for you? or was it instant for you?

how did you find the right driver qcser.inf_amd64_da2bdde674bc3d1e ? there are too many drivers in your zip...

what choice in USB Preference? No data transfer, or USB Tethering, or File Transfer?

mimix2ppp said:
I dont have the box........ only what I find from filesystem.....
can you check this file in your phone /mnt/vendor/persist/engineermode/engineermode_config to see if the IMEI there is the correct IMEI1 of your phone?
can you check /data/opdiagnose and search for "meid" with ripgrep https://github.com/BurntSushi/ripgrep , "rg -i -M 1000 meid" command. is the meid in these logs the same as your real MEID?
also. How long was "Connecting to the smart phone" in Write Tool for you? or was it instant for you?
Click to expand...
Click to collapse
Sorry, I sent my device to repair to CTDI because they perform such repairs:
And then those incompetent idi**s sent me this:

mimix2ppp said:
what choice in USB Preference? No data transfer, or USB Tethering, or File Transfer?
Click to expand...
Click to collapse
File transfer is required for IMEI writing to work I believe...

mimix2ppp said:
I dont have the box........ only what I find from filesystem.....
can you check this file in your phone /mnt/vendor/persist/engineermode/engineermode_config to see if the IMEI there is the correct IMEI1 of your phone?
can you check /data/opdiagnose and search for "meid" with ripgrep https://github.com/BurntSushi/ripgrep , "rg -i -M 1000 meid" command. is the meid in these logs the same as your real MEID?
also. How long was "Connecting to the smart phone" in Write Tool for you? or was it instant for you?
Click to expand...
Click to collapse
Connecting to the smart phone was instant...
mimix2ppp said:
how did you find the right driver qcser.inf_amd64_da2bdde674bc3d1e ? there are too many drivers in your zip...
Click to expand...
Click to collapse
Driver qcser is under:

necesito una copia del qcn del in2025 oneplus 8 pro me quede sin imei

I need a copy of the qcn of the in2025 oneplus 8 pro I ran out of imei

vrabaci said:
Make sure to back up EFS
Click to expand...
Click to collapse
I don't know how to do it

Hi, I hv one plus 8 tmob. In converting to global ans dual sim I tried to repair IMEI and the tool I used messed up efs I think. Now it doesn't repair IMEI neither any network. In just a locked state. I want to use your guide but it is for eu and my bootloader is locked too. I hv unlock token but after that mess my OEM unlock is grayed too. Any suggestions