[GUIDE] How to trigger the Nokia 3.2 to EDL mode - Nokia 3.2 Guides, News, & Discussion

In case HMD blocked the Allowing "OEM unlocking" function on Nokia 3.2, or if you bricked the phone accidently, here's how to trigger the phone to EDL mode:
- Power off the phone
- Remove the SIM tray
- Peel off the back cover with fingernails, or something like small jailbar
- Unscrew screws on the top
UPDATE:
According to @JFDee , Nokia 3.2 00EEA variant doesn't have the test point on the right. You may need to connect the only point you've seen to the ground, for example the RF shield is grounded.
According to @deadman96385 , Nokia 3.2 V completely removed the test point - so this guide may unsuitable for it.
Now you have access to the motherboard. I highly recommend you to disconnect the battery for further procedure.
Then use tweezers to connect points mentioned on the picture below, then connect the phone to PC.
{
"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"
}
Once you get the point, you can get to the next procedure of bootloader unlocking.
You can follow the bootloader unlock guide for Nokia 4.2 then.
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402

no EDL on 00EEA
I also have the Nokia 3.2 00EEA variant.
The connection from the only left point to ground is not working for me!
Hope for more possibilities in future!
UPDATE:
After removing the solder vanish from the second point on the right side and shorting the points, EDL mode finally works!

page1875 said:
I also have the Nokia 3.2 00EEA variant.
The connection from the only left point to ground is not working for me!
Hope for more possibilities in future!
UPDATE:
After removing the solder vanish from the second point on the right side and shorting the points, EDL mode finally works!
Click to expand...
Click to collapse
Could you show pictures how you did it?

BorisNahka said:
Could you show pictures how you did it?
Click to expand...
Click to collapse
I too would greatly appreciate a picture or diagram of what to short/solder on the 3v version! Been lurking this forum for a few days waiting for an update

I'm not at home actually for longer time.
But you see the second point directly next to the one open point (see picture above). This you have to open a little bit with a knife or something sharp, but be careful not to damage the copper from the point!
But also when you are already in Fastboot Mode you can take the Fastboot.exe which is included in the global image files in the other thread and boot your phone directly into edl mode without open it!

page1875 said:
I'm not at home actually for longer time.
But you see the second point directly next to the one open point (see picture above). This you have to open a little bit with a knife or something sharp, but be careful not to damage the copper from the point!
But also when you are already in Fastboot Mode you can take the Fastboot.exe which is included in the global image files in the other thread and boot your phone directly into edl mode without open it!
Click to expand...
Click to collapse
HOWWW????

FastBoot mode Stuck
hikari_calyx said:
In case HMD blocked the Allowing "OEM unlocking" function on Nokia 3.2, or if you bricked the phone accidently, here's how to trigger the phone to EDL mode:
- Power off the phone
- Remove the SIM tray
- Peel off the back cover with fingernails, or something like small jailbar
- Unscrew screws on the top
UPDATE:
According to @JFDee , Nokia 3.2 00EEA variant doesn't have the test point on the right. You may need to connect the only point you've seen to the ground, for example the RF shield is grounded.
According to @deadman96385 , Nokia 3.2 V completely removed the test point - so this guide may unsuitable for it.
Now you have access to the motherboard. I highly recommend you to disconnect the battery for further procedure.
Then use tweezers to connect points mentioned on the picture below, then connect the phone to PC.
Once you get the point, you can get to the next procedure of bootloader unlocking.
You can follow the bootloader unlock guide for Nokia 4.2 then.
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
Click to expand...
Click to collapse
Hi fella could you help me on my problem? I'm stuck in fastbood mode and my computer doesnt recognise it.

I guess either driver problem in windows or usb cable damaged!
Try Linux!

ranafasihzubair said:
HOWWW????
Click to expand...
Click to collapse
YEAH HOW PLEASE?

ranafasihzubair said:
HOWWW????
Click to expand...
Click to collapse
Fastboot reboot edl

Related

[Q] Android phone with real walkie + app

I have an android phone model with built-in walkie talkie (UHF 400-470MHz) but the leading software is very limited. Anyone is encouraged to modify the program to be able to autoscan and other functions? This is the application: http://www.crocko.com/903E0046F8BC4EC796E0A3A033C82DC7/Intercom_1.0.rar
The model of walkie is runbo x3, it is a china mobile and is possible buy in aliexpress.
anyone?
Did anyone interested in reverse engineering done?
appear this in app:
{
"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"
}
but autoscan function is not implemented in the application
ok, it is the app decoded with apktool: http://www.crocko.com/F2C4E96EA3464EC182958D2BC27F4EEF/Intercom_1.0.apk.rar what need modify for that autosearch function appear in the app?
did you get the ROOT? or enter into recovery mode?
in recovery yes and respond to fastboot commands but with adb not. Drivers is broken, not detect the phone, no possible root, the android version is android 2.3.5 updated, drivers and updates is possible download in this page: www.runbo.net/web/down.php or download all pack from: http://www.mediafire.com/?n1xgdq0o8mu253i
wuebas said:
in recovery yes and respond to fastboot commands but with adb not.
Click to expand...
Click to collapse
how to enable the recovery?
vol up + power, laser light is powered, connect usb and work fastboot.
wuebas said:
vol up + power, laser light is powered, connect usb and work fastboot.
Click to expand...
Click to collapse
vol up + power - fastboot mode. no problem with it
I mean mode of recovery.
the firmware file is recovery.img, then somehow it is possible to include
sorry, what is the key combination for entry in recovery mode?
wuebas said:
sorry, what is the key combination for entry in recovery mode?
Click to expand...
Click to collapse
not found by experience, the manufacturer has not yet responded
work for you adb drivers?
ok, this update is with rooted image,
added superuser
deleted googleplay (recommended use applanet)
deleted bauidu chinesse app
deleted default launcher
added adwlauncher
added busybox
gingerbread 2.3.5 rooted for runbo x3:
http://www.mediafire.com/?cpsnn5h5l63q9rw
(if you like delete user data add this lines in flash_all.bat
fastboot erase userdata
fastboot flash userdata AP\userdata.img
)
Good daytime
Can you repost please decompiled Intercom APK?
How are you guys liking your runbo phones? I am really wanting one but I just needing a push to make the jump to buy one.
josefcrist said:
How are you guys liking your runbo phones? I am really wanting one but I just needing a push to make the jump to buy one.
Click to expand...
Click to collapse
Jump now
I've had one for a week now, I can really recommend this phone for anyone who needs a rugged phone with up-to-date features. I even wash it daily without turning it off
Short pros and cons:
+good display with adequate brightness
+very loud speaker
+fm radio works without headset +(walkietalkie antenna required)
+HUGE battery, with my other phones I'm out of battery before evening, this lasts -over two days
+good camera
+very nice keypad
+doesn't weigh as much as it looks (300grams)
+dual standby sim works great
+hasn't crashed yet (haven't even turned it off for a week)
-needs a big pocket
-android keys get accidentally touched when using touchscreen
-usb port behind cumbersome door
-earpiece is very selective, needs to be placed accurately, otherwise good
-no focus action on camera button (hard to take pics in tight and dark places)
That's my 5cents
/VM
Well I made the jump and I am loving the runbo x3.
Runbo x3
have anyone rooted this phone!?? i need it badly.. anyone tried Bin4ry's tool to this phone? thanks to anyone who replies..thanks
sp0nge22 said:
have anyone rooted this phone!?? i need it badly.. anyone tried Bin4ry's tool to this phone? thanks to anyone who replies..thanks
Click to expand...
Click to collapse
I did. Just use the method described in this thread: http://forum.xda-developers.com/showthread.php?t=1886460

(GUIDE) A2017U Desbrickear/UnBrick ZTE AXON 7

I can not be held responsible if you do not follow the instructions and your phone explodes in your face, you get wings and fly, your microsd smoke etc. EVERY PROCEDURE YOU MAKE ON YOUR PHONE IS ONLY YOUR RESPONSIBILITY.
{
"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"
}
As you notice, this process also enables fastboot commands.
This is a step-by-step tutorial to get the Brick phone
I leave a video as a reference that I recorded in addition to the files and drivers you need.
Either because of bad flashing, you were wrong with bootstacks or ROM.
1.- See that the phone is off
2.- Press Volume + and Volume - and the Power key at the same time until the LED turns on and off in Red, that means that you are already in EDL Emergency mode.
3.- Connect the phone and Install the Drivers
4.- When you see that Qualcomm HS-USB QDLoader 9008 and a COM port have been installed
5. Open MiFlash and copy the address of the unpacked A2017U_B19-NOUGAT_TWRP_EDL package into the address bar.
click on Refresh and when the COM port of your phone comes out click on Flash.
If everything goes well you will see that the process begins and at the end it will say Ready, then you have to disconnect the phone and press power about 10 seconds later and press power again until it turns on. You should be able to enter TWRP to restore your backup or flash a new ROM.
Even it is very likely that the rom you had installed start.
https://www.youtube.com/watch?v=dHB61cMurG4&t=10s
Link MiFlash: http://www.mediafire.com/file/25fu9boj245wynz/MiFlash20161222.zip
LinkB19 EDL TWRP: https://build.nethunter.com/misc/axon7/A2017U_B19-NOUGAT_TWRP_EDL.zip
Link Drivers Qualcomm: https://androidfilehost.com/?fid=745425885120754986
Link Drivers ZTE: http://phoneusbdrivers.com/zte-axon-7-usb-driver/
Update: All Links in 1 uploaded by me: https://drive.google.com/file/d/16Szwb4paI-aBH-v8gxbuVi0xMf-NdxLp/view?usp=sharing
TheDarkKnightSM said:
I can not be held responsible if you do not follow the instructions and your phone explodes in your face, you get wings and fly, your microsd smoke etc. EVERY PROCEDURE YOU MAKE ON YOUR PHONE IS ONLY YOUR RESPONSIBILITY.
As you notice, this process also enables fastboot commands.
This is a step-by-step tutorial to get the Brick phone
I leave a video as a reference that I recorded in addition to the files and drivers you need.
Either because of bad flashing, you were wrong with bootstacks or ROM.
1.- See that the phone is off
2.- Press Volume + and Volume - and the Power key at the same time until the LED turns on and off in Red, that means that you are already in EDL Emergency mode.
3.- Connect the phone and Install the Drivers
4.- When you see that Qualcomm HS-USB QDLoader 9008 and a COM port have been installed
5. Open MiFlash and copy the address of the unpacked A2017U_B19-NOUGAT_TWRP_EDL package into the address bar.
click on Refresh and when the COM port of your phone comes out click on Flash.
If everything goes well you will see that the process begins and at the end it will say Ready, then you have to disconnect the phone and press power about 10 seconds later and press power again until it turns on. You should be able to enter TWRP to restore your backup or flash a new ROM.
Even it is very likely that the rom you had installed start.
&t=10s
Link MiFlash: http://www.mediafire.com/file/25fu9boj245wynz/MiFlash20161222.zip
LinkB19 EDL TWRP: https://build.nethunter.com/misc/axon7/A2017U_B19-NOUGAT_TWRP_EDL.zip
Link Drivers Qualcomm: https://androidfilehost.com/?fid=745425885120754986
Link Drivers ZTE: http://phoneusbdrivers.com/zte-axon-7-usb-driver/
Update: All Links in 1 uploaded by me: https://drive.google.com/file/d/16Szwb4paI-aBH-v8gxbuVi0xMf-NdxLp/view?usp=sharing
Click to expand...
Click to collapse
Crap forget what I said, it was right on the title...
Would be much better if you:
a) made it for all 3 models with a link to WesTD's EDL package thread
b) said something about DFU (if you make it for the other models) and how this will not work on them if the driver is the dfu one (zte handset diagnostic interface)
Add somewhere on the guide that it is only for the U just in case.
Choose an username... said:
Crap forget what I said, it was right on the title...
Would be much better if you:
a) made it for all 3 models with a link to WesTD's EDL package thread
b) said something about DFU (if you make it for the other models) and how this will not work on them if the driver is the dfu one (zte handset diagnostic interface)
Add somewhere on the guide that it is only for the U just in case.
Click to expand...
Click to collapse
both in the title and in the guide in the mention of the package, it is said that it is only for A2017U, even though I will have a clarification in red and great, if any. Thank you.
Sent from my ZTE Axon 7 using XDA Labs

Help with fixing hard bricked MTK phone (PhonePad Duo S7/M-PPAS7)

Hello everyone, i have hard bricked my PhonePad Duo S7 / ppxs7 (MT6737) while installing firmware update by accidentally unhooking the cable. I am wondering if anyone can help me fix this issue. The phone hardware is all in good condition but the software seems to be completely wrecked, the phone doesn't start at all no matter what combination of buttons and how long i hold it. I tried to flash it again, to no avail because my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized", you can see it in the image i attached below ( also image of what it looks like now in device manager ). I am confident there is a way to fix this, i just need to find a way to make it recognizable once more. Ive sent an email to the manufacturer as well but i hope i might in the meanwhile find a solution as they are not guaranteed to respond, i do not have warranty on this phone. I would be extremely super thankful to any input related to my case.
{
"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"
}
As long the the hardware is not damaged, it is recoverable. First, are you unchecking preloader when flashing? If still it doesn't work., then keep phone charging overnight to see if you get a response. Other than that, you might have to get your motherboard replaced. :good:
minute214 said:
Hello everyone, i have hard bricked my PhonePad Duo S7 / ppxs7 (MT6737) while installing firmware update by accidentally unhooking the cable. I am wondering if anyone can help me fix this issue. The phone hardware is all in good condition but the software seems to be completely wrecked, the phone doesn't start at all no matter what combination of buttons and how long i hold it. I tried to flash it again, to no avail because my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized", you can see it in the image i attached below ( also image of what it looks like now in device manager ). I am confident there is a way to fix this, i just need to find a way to make it recognizable once more. Ive sent an email to the manufacturer as well but i hope i might in the meanwhile find a solution as they are not guaranteed to respond, i do not have warranty on this phone. I would be extremely super thankful to any input related to my case.
Click to expand...
Click to collapse
Hope I helped.
I was experimenting on an old device (lenovo tab 2 a7 30hc) and hard bricked it.
I've been trying to install the stock rom from SP Flash tool and installed the mtk vcom preloader drivers but the phone still won't get detected.
Someone please help me out here please.
rishabhrocks said:
I was experimenting on an old device (lenovo tab 2 a7 30hc) and hard bricked it.
I've been trying to install the stock rom from SP Flash tool and installed the mtk vcom preloader drivers but the phone still won't get detected.
Someone please help me out here please.
Click to expand...
Click to collapse
Install vcom and Lenovo drivers.
minute214 said:
my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized",
Click to expand...
Click to collapse
I had similar soft brick problem with MTK tablet. Generally you need to remove battery (or unplug the battery connector) and install (plug) it back. If your battery has soldered wires you need to unsolder Vcc (usually red) wire and solder it back after a while (like a couple minutes after). If your battery is not able to remove/unsolder/unplug your only solution is discharge the battery and it can takes a long time.

GUIDE EDL POINTS and TOOL (no fake points)

Hi , here's how i managed to start edl on my bricked Poco X3
- The true points are hidden by the usb map , and NOT at the place mentionned in many "putaclic" web pages.
- This place make it really harder to connect than in other know devices.
- Here is my solution :
01 remove cover ..
{
"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"
}
now remove green screws on the top+orange screw in order to remove plastic cover and access mother board.
02 unplug power map (in red) + usb map (in green)
03 now you see test points (in green) and fakes ones (in red)
04 make a tool using aluminium or coper paper and adhesive
05 place the tool in order to contact points like this :
06 reconnect usb map
you will have to press with your favorite nail to get edl start
Thx and Credits:
@mahajant99 (XDA and telegram) for found the points
Myself for the tool and method without remove mother board
Thanks for sharing, Btw "putaclic" is a very french way to say "clickbait" haha
Xfirstname said:
Thanks for sharing, Btw "putaclic" is a very french way to say "clickbait" haha
Click to expand...
Click to collapse
?
Wow this is some scary **** when you bricked your phone. Hope i wont be included with the unlucky ones. How do we prevent from getting hard bricked. Any tips?
olujnap316 said:
Wow this is some scary **** when you bricked your phone. Hope i wont be included with the unlucky ones. How do we prevent from getting hard bricked. Any tips?
Click to expand...
Click to collapse
For my personal tips, I would avoid flashing custom ROMs and stick with the stock one until at least a stable version of recovery and ROM had been released. I had 4 devices prior to this present Poco X3 and none of them I had hard bricked. Only bootloops.
Anybody now about THE edl point for note 9 pro is? I test it from pictures om Google but it didnt work
Thank you very much for this helpful guide. I hope I do not need it. Very deceptive of people to publish false EDL points. Thanks for that tip ??
I'm curious, can the back panel be easily removed and attached again or is it glued?
Ungeskriptet said:
I'm curious, can the back panel be easily removed and attached again or is it glued?
Click to expand...
Click to collapse
Glue like Poco X2
terror_rest45 said:
For my personal tips, I would avoid flashing custom ROMs and stick with the stock one until at least a stable version of recovery and ROM had been released. I had 4 devices prior to this present Poco X3 and none of them I had hard bricked. Only bootloops.
Click to expand...
Click to collapse
Planing to buy this device.
Can u confirm the stable version of recovery and rom for this?
Ps: from India, belive flipkart had only non NFC model
vygavedha said:
Planing to buy this device.
Can u confirm the stable version of recovery and rom for this?
Ps: from India, belive flipkart had only non NFC model
Click to expand...
Click to collapse
Not yet, while there are official roms (could be stable). Recovery is a disaster, many bugs and flaw because all of them are still at Alpha version. So i think you gotta wait for another month
Speedo.thc said:
OP
Click to expand...
Click to collapse
So what do you do after that? What did you do to recover the phone? What software? What rom? Please explain more, I'm sure more people will get stuck there...
Like myself.
Don't the old xiaomi edl cable method work anymore??
Me 2 bro
Pleas help
By which software can we flash the phone in edl point mode?
So what do you do after that? What did you do to recover the phone? What software? What rom? Please explain more, I'm sure more people will get stuck there...
Like myself.
Jacccob said:
Me 2 bro
Pleas help
By which software can we flash the phone in edl point mode?
So what do you do after that? What did you do to recover the phone? What software? What rom? Please explain more, I'm sure more people will get stuck there...
Like myself.
Click to expand...
Click to collapse
My device was too much hard bricked and it didn't work after paid the flash by authorized account
Hi, i have the same problem. Phone is dead, only recognized by the Qualcomm EDL driver, but i don't know how to use their software and what files i need. Any help would be nice.
Hi,
I have a Poco X3 with a Locked Bootloader and is Bricked. Can someone please guide me on how to unbrick it or unlock the bootloader. I've tried the EDL method and it works but I don't know what to do after that. Do I keep the aluminium foil in and then flash it?, or press the power button? or something else? Any help is appreciated with steps. I don't wanna lose this phone so I hope someone can help me out. Thank you!!
By any chance do you happen to know edl points for Motorola edge 20
Would be helpful ಥ‿ಥ

Question Nord 2 Hard brick

Available: there is a phone, 12/256, DN2103, black screen, recovery and fastboot do not turn on (but the buttons are working), when charging is connected via a USB tester (measures volts, amps and transmitted mAh) and when the power button is pressed for a long time, charging stops for a moment and starts again (restarts?). When you press all the buttons on the smartphone (volume minus and plus, the power button), the "USB Serial Interface Device (COM4)" ("Устройство последовательного интерфейса USB (COM4)) appears in the device manager. Yes, the drivers are installed.
Spoiler
{
"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"
}
The MTK Auth Bypass Tool V7.8.0.5 program shows disable device security fail! when connecting a smartphone and pressing all the buttons for a long time.
Spoiler
MTKClient Program
When all the buttons or volume buttons are held down for a long time, it gives out:
Handshake failed, retrying...
Spoiler
And so it repeats several times, with the system sound of the connected device.
Are there any ways to recover?
From GitHub, where the MTKClient program is located, I downloaded the disk image, booted from it. The phone began to be determined, but even here to no avail
Spoiler
Maybe you have the same issue as we have?
In my case I got it to show the oneplus logo then black and bootloop, but as you no fastboot or recovery or brom access
bootloop,bricked device after trying to do local ota update
so i have tried updating my phone os by using local ota because i have root, i downloaded the zip with oxygen updater and tried flashing it with twrp but it said its wrong device twrp was reporting denniz and the update was for OP515BL1 but when...
forum.xda-developers.com
username_my_name said:
Available: there is a phone, 12/256, DN2103, black screen, recovery and fastboot do not turn on (but the buttons are working), when charging is connected via a USB tester (measures volts, amps and transmitted mAh) and when the power button is pressed for a long time, charging stops for a moment and starts again (restarts?). When you press all the buttons on the smartphone (volume minus and plus, the power button), the "USB Serial Interface Device (COM4)" ("Устройство последовательного интерфейса USB (COM4)) appears in the device manager. Yes, the drivers are installed.
Spoiler
The MTK Auth Bypass Tool V7.8.0.5 program shows disable device security fail! when connecting a smartphone and pressing all the buttons for a long time.
Spoiler
MTKClient Program
When all the buttons or volume buttons are held down for a long time, it gives out:
Handshake failed, retrying...
Spoiler
And so it repeats several times, with the system sound of the connected device.
Are there any ways to recover?
From GitHub, where the MTKClient program is located, I downloaded the disk image, booted from it. The phone began to be determined, but even here to no avail
Spoiler
Click to expand...
Click to collapse
Join this telegram group theres a diffrent mtkclient on there - https://t.me/OnePlusNord2GlobalOfficial/
Search for mtkclient in that group
i am in the same boat as you , i use mtk bypass auth v6 and it does bypass but then after sometime the phone is getting disconnected , Giovix himself said he is going to look into this issue of black screen and me and giovix are in talks regarding the same , his laptop is in service center so waiting for his laptop so me and him can discuss and work on it .
Note : i am no developer i am just a normal guy like you .
I suggest you to join that group on telegram and tag giovix and have a talk with him and let him know that there are many people with this problem .
Meanwhile ill wait till he gets his laptop back to me and him can start experimenting what the problem is , i think he will definitely solve the problem .
Hi there, I'll try to summarize everything:
Unfortunately, the new bootloader doesn't actually provide a way to enter BROM mode like it did before, nor access fastboot. If y'all were on/upgraded to C.10/11, then there's no chance for now.
I've tried to contact bkerler, MTKClient's dev (here, github issue) regarding this specific problem, and as of now it affects both Nord 2 and Nord 2T.
There isn't really a way to recover it, cause it would need a signed preloader (at least that's what I'm assuming, since the preloader itself spits an authorization error), like any Xiaomi device.
If you can, go to a service center and get it repaired. If you can't, I'm afraid the only thing you can do is to wait for a possible solution.
Nonetheless, I'll try to see if there's a way to bypass that.
Giovix92 said:
Hi there, I'll try to summarize everything:
Unfortunately, the new bootloader doesn't actually provide a way to enter BROM mode like it did before, nor access fastboot. If y'all were on/upgraded to C.10/11, then there's no chance for now.
I've tried to contact bkerler, MTKClient's dev (here, github issue) regarding this specific problem, and as of now it affects both Nord 2 and Nord 2T.
There isn't really a way to recover it, cause it would need a signed preloader (at least that's what I'm assuming, since the preloader itself spits an authorization error), like any Xiaomi device.
If you can, go to a service center and get it repaired. If you can't, I'm afraid the only thing you can do is to wait for a possible solution.
Nonetheless, I'll try to see if there's a way to bypass that.
Click to expand...
Click to collapse
Thank you for your input Giovix .
Giovix92 said:
If you can, go to a service center and get it repaired.
Click to expand...
Click to collapse
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
username_my_name said:
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
Click to expand...
Click to collapse
Absolutely for both questions.
username_my_name said:
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
Click to expand...
Click to collapse
SVC will revive your phone rightaway , no need to buy another board , they have diffrent tools for flashing , they revived my phone but for some reasons i deleted my system partition so they were not able to flash my imei partition which is weird .
But in your case SVC will definitely solve your problem without needing to buyba motherboard , just ask them to flash your phone .

Categories

Resources