Database Info

[OFFLINE UPDATE] WP8.1 To W10 Mobile [ATT] [Verizon] [T-Mobile] (Build 10586.107)

Prerequisites:
Your PC must be at least Windows 7 Service Pack 1, although you must install every Visual C++ Redistributable Runtime and the Windows Device Recovery Tool.
Your Phone OS version must be at least 8.10.14219.341 or newer. If not, please update it using the windows insider app.
Have registered your device as a developer with the WP SDK.
Remove pin lock and turn off reset protection before the update procedure.
{
"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"
}
:fingers-crossedlease follow this guide at your own risk as I am not responsible for bricked devices, dead SD cards or thermonuclear war:crying:.
Instructions:
1. Backup Your device.
2. Download Iutool (WP_CPTT_NT-x86-fre.msi) from the attachments section and install it. The default install directory will be
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
3. Download the M8.Rar that reflects your Carrier and extract the contents to C:\ on your PC.
M8ATT
M8Verizon
M8TMobile
Code:
C:\M8ATT
Code:
C:\M8Verizon
Code:
C:\M8TMobile
4. Open Command Prompt as administratior and change directory to where Iutool is installed.
Code:
cd C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
5. Plug your M8 into your PC and check to see if Iutool discovers your device by typing
Code:
iutool -l
If your device appears then you are ready to continue
If you met error 80070490 when executing iutool -l then disconnect your device and remove it from the Devices & Printers section of Control Panel
6. Assuming you extracted the correct zip into C:\ you are either going to type
Code:
iutool -V -p C:\M8ATT
Code:
iutool -V -p C:\M8Verizon
Code:
iutool -V -p C:\M8TMobile
That command will push the update to your device and it will prepare for the installation! Once the update is ready, take it! You'll want to find something to occupy your time as the process will take 40 minutes.
8. Once booted into W10 open Settings and navigate to the "For Developers" menu and enable Developer Mode.
9. Download and install Interop-Tools from it's respected thread and follow the For All other OEM Devices section to Interop/Cap Unlock your M8 if you had planned on doing so.
Interop-Tools https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
10. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
11. Now enable Windows insider preview builds and set to either slow or release ring.
12. Go into phone update and search for update. You should be brought to build 14393 or later. Updating to this build will fix critical issues/bugs you met earlier.
13. I also recommend a factory reset after all updates as that will reset Registry values to defaults and fix other things as well.
A HUGE thanks to @hikari_calyx for the Offline Update package V4.1 that he had put together over on the Windows 10 Mobile forums!
Another HUGE thanks to @gus33000 for Interop-Tools!​

RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.

hikari_calyx said:
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
Click to expand...
Click to collapse
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.

AnierinB said:
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
Click to expand...
Click to collapse
In some case, without modifying them, you can't search any update.

I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe

I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
Click to expand...
Click to collapse
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...

zagreo said:
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
Click to expand...
Click to collapse
ThIs is normal as I've encountered the same issue.
Bugs I know of:
Front facing camera sometimes causes reboot (switching from back in most cases)
Sound will sometimes only go through one speaker (works itself out but happens every now and then)
Flashlight toggle in quick settings has a long delay and sometimes doesn't work at all
Dot view doesn't work (but I personally delete the "extras" apps as the update process somehow made that possible for me)
Other than all that I'm pretty amazed at the way this devices handles the OS... every time I've gone back to 8.1 I'd instantly regret it after the setup

Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.

Cokefrevr said:
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Click to expand...
Click to collapse
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me

Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
Click to expand...
Click to collapse
Everything work out?

AnierinB said:
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Click to expand...
Click to collapse
Yea trying to install from the store, sorry for being stupid really tired but device hub?

Cokefrevr said:
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile

AnierinB said:
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
Click to expand...
Click to collapse
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.

I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.

Cokefrevr said:
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
Click to expand...
Click to collapse
rayxanber said:
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Follow the for all other OEM Device section. Interop tools has changed a bit since I last used the device.
And yes that reminds me.. In worst case you can't get interop tools to work I'm afraid you'll have to change it before you do the offline update via The modified preview for developer's.. But no worries as the WDRT tool can bring you back to 8.1 NP.
Besides that.. How's the experience with w10 on the m8 for you guys?

AnierinB said:
[*]Your PC must be at least Windows 7 Service Pack 1, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool. Windows 8/8.1/10 are also acceptable.
Click to expand...
Click to collapse
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
AnierinB said:
(If you met error 80070490 when executing iutool -l, disconnect your phone, and delete your phone from Device & Printers section of control panel. Then reconnect your phone again)
Click to expand...
Click to collapse
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
AnierinB said:
Besides that.. How's the experience with w10 on the m8 for you guys?
Click to expand...
Click to collapse
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
AnierinB said:
11. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
Click to expand...
Click to collapse
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...

reukiodo said:
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
Click to expand...
Click to collapse
Glad you got it working.. Haven't logged in to xda in a while because i'm using micro g on my Android device so sorry about the absence of help. How you liking it so far? HTC should have supported this huh? p.s lumia 735 works best for device spoofing.. 950 is unnecessary

I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?

nar001 said:
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
Click to expand...
Click to collapse
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.

AnierinB said:
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
Click to expand...
Click to collapse
Am I supposed to do all this on my computer, or the phone? And I don't have the "NDTK" button on Interop 1.9 on my M8 (It's the AT&T version, if that helps)

[UNLOCK] Tuliptool: unlock, TWRP, and custom boot

First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).

first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:

Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.

I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Meme Queen said:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Click to expand...
Click to collapse

tdm said:
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Click to expand...
Click to collapse
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"

Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse

tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.

I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?

pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again

Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?

There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
MrWhite0429 said:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
Click to expand...
Click to collapse

tdm said:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
Click to expand...
Click to collapse
Device Shows connected and drivers installed under device manager.
Command prompt is being run as so:
Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator
cd C:\users\admin\desktop\tuliptool
C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status
Device Not Detected
---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------
UPDATE:
I found that I had to use a USB 3.0 hub in order to get the phone to be detected.
Once detected I ran commands as followed.
tuliptool-win64.exe lock unlock
(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)
tuliptool-win64.exe read boot
(This created the backup-boot.bin file in the directory)
Tuliptool-win64.exe read recovery
(This created a backup-recovery file in the directory)
tuliptool-win64.exe write boot
Its at this point here I get a Runtime Error as well. The entire process comes to a halt.

Thsnks, tried that, but no luck. It's still stuck on the splash screen.
Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
rombdeta said:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Click to expand...
Click to collapse

tdm said:
This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device.
[/B][/COLOR]
Click to expand...
Click to collapse
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol
Can't wait to see the roms @tdm, keep it up and I think the mini is going to get a lot more interesting.
I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.
New roms without MiFavor would be awesome too and ones that improve performance!

ZTE
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.

CRAFTER0302002 said:
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
Click to expand...
Click to collapse
First post:
"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."

Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.

tdm said:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
Click to expand...
Click to collapse
as in rename to recovery.bin?

Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse

Unlocking Bootloader [Incomplete]

Note: It would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows
Mac
Linux
Custom Recovery Image (TWRP or some other that you prefer):
(Official TWRP web hosted version) Nokia 6.1 (2018)
Download from American Mirrors
Download from EU Mirrors
USB Cable to Connect the phone to the computer
The Phone: Nokia 6.1 (2018) (preferably Fully Charged)
The device drivers (for Windows and Mac)
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the (Windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Nokia support site), and reboot.
On MacOS
Download the MacOS (Darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the (Linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see (this repository) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at (Nokia Support) to unlock your bootloader, you will need to register at this site with a working/active email to proceed. They'll verify your device using an app to issue a validation code.
Note: If your device is not supported by the Nokia Bootloader Unlock
website, you will need to use an alternative bootloader unlock method.
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. In case you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Nokia 6.1 (2018) does have an official TWRP recovery that you can find here: Nokia 6.1 (2018) [PL2] respectively.
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Boot into TWRP temporarily:
Code:
fastboot boot twrp.img
8. Use adb to push the zip onto your device:
Code:
adb push twrp.zip /
9. Go to `Install` option on the TWRP menu and browse to the zip (Scrolling to the bottom should have the zip) and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidentally flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
This command assumes the recovery image is present in your current working directory (Check using `DIR` on command prompt or `ls` command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
10. Now reboot into recovery to verify the installation:
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)

Reserved

What do you do if oem unlocking in developer is greyed out? TA-1045

@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?

singhnsk said:
@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?
Click to expand...
Click to collapse
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.

cmaxwe said:
.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
Hey now, there is really no need for that level of hostility. He knew they were doing unlocks for at least one Nokia phone, and me may not have known that they didn't have it for the 6.1.
Please don't talk to peope like that if they make a simple mistake when trying to provide info and help out the community. We're all human.

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?

cmaxwe said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
It's not like there isn't a way, there is, just not a transparent method. Somehow those (refer to link in reply) are able to generate and send the signature file allowing you to unlock the phone, how it works or if your bootloader be locked again after updating is unknown to me ATM

mymeatb18 said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?
Click to expand...
Click to collapse
Well the ROM development begins after an Official TWRP recovery, so the chances are there might be some. I'm not clear on the the OTA being able to relock the bootloader either since I was running Pie update when I got to know about it.

thread closed as per OP request

Save data from blocked Android

Hi,
A friend of mine want's to recover some pictures from an old phone of his, but he forgot the pattern to unlock the device...
* The phone is a CAT S41 stock android.
* The phone is in perfect conditions
* The USB debug option of the phone is disabled.
- Because of that, I've been unable to execute any adb commands on the device.
- When the phone is in Recovery Mode, the device is detected by adb, but unauthorized:
[email protected]:~$ adb devices
List of devices attached
S411931008366 unauthorized
[email protected]:~$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
I've tried to set the $ADB_VENDOR_KEYS manually, with no success.
In this situation, I have some questions to ask:
1. Is there a known way of bypassing the pattern lock?
2. Is there a known way of dumping data to any other device, in order to retrieve the pictures
3. Can the debug options be activated somehow?
As a last resource, I'd be willing to open the phone and spend some bucks on whatever hardware is needed to dump the whole disk, if that is relatively feasible to do.
4. Could you give me any feedback/information on hardware methods of dumping the disk of the phone? 0 experience there.
I would greatly appreciate any input you could give me.
If more details of the system or the situation are needed, please ask.
Thank you kindly for your attention,
abocador

Can't offer a solution.
But, even if there is a way to dump the files - what requires phone's Android is got rooted and USB-Debugging is activated , IMO it makes no sense to waste more time in this because since Android 4 data are AES-128 encrypted ( FBE and/or FDE method ) and the encryption probably can't get cracked.

2. + 4. won't work because of encryption, but 1. + 3. is possible on that old android 7 mediatek device.
assuming device runs on FDE full-disk encryption, is encrypted with default_password, one can hack boot.img and authorize usb-debugging. because device decrypts itself on boot that's all you need to get access.
but first install VCOM preloader drivers and make a readback of device with WwrMTK v2.51 + SP Flash Tool (old method) or mtkclient (new method).
I will tell you how to patch and resign boot.img once you made the important backup step. most important partitions are userdata+metadata.
Btw there is maybe another (even more easier) method. Just port TWRP recovery for that device. Because of weak security implementation phone will boot into custom recovery on locked bootloader (I did on Cubot King Kong)

Hi,
Thank you a lot for your reply.
I've been trying to do the backup, but I wasn't able to even use the mtkclient
I think I will just forget about this.

you know device must powered off completely, and preloader only says 'Hello' to computer for ~ 1 second? Did you install VCOM preloader drivers during that second (device manager -> pick device -> Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk) ?

Hello again!
Yes, I'm aware the device must be powered off.
I'm quite sure I have all the drivers I need. I'm working from a Debian system.
Some weeks ago, I posted the log I get when I try to connect mtkclient to the phone:
Error on sending data: DA hash mismatch · Issue #575 · bkerler/mtkclient
Hi! I'm trying to use this tool on a CAT S41 phone, but I'm unable to get any proper connection between the device and my computer. After initializing the GUI with_python mtk_gui_, I get the follow...
github.com
One more time, thanks for your help,
I think I'm going to park this project for a while.
Cheers,
abocador

okay, for linux no need for drivers looks good, have you tried some random cmd line usage just for fun?
Code:
python3 mtk printgpt
python3 mtk rl out
python3 mtk crash
python3 mtk --preloader printgpt
python3 mtk --preloader rl out

"This phone model does not support deep testing." Is it possible to bypass that screen in the Realme's deep testing app?

Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-)
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test my luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).

turistu said:
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test by luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
Click to expand...
Click to collapse
Thank You!
It realy works!

Thanks,
Worked for me with Android 13/RealMe UI 4.0.
Now to magisk...

After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)

Is there a way to use this script on realme 9 pro 5g eu rmx3472?
Edit: It works perfectly and i was also able to change my region to ru.

mister_slowhand said:
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Click to expand...
Click to collapse
Try https://rms01.realme.net/sw/RMX3472GDPR_NN.X.NN_YYYYMMDDHHMM0000.zip,
(replacing the N, Y, etc with the actual version of the firmware).
Also the variants with .7z instead of .zip.

hatbo said:
Thank You!
It realy works!
Click to expand...
Click to collapse
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob

RobertoSt25 said:
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
Click to expand...
Click to collapse
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.

I love you Turistu, thank you for the guide!
I've had the problem, that the device wasn't getting recognized in fastboot mode.
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, settings -> windows update -> advanced options -> reset options -> advanced restart. Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
I have attached the Oneplus drivers i've used for fastboot and a patched boot.img with magisk 26.1 from RMX3311_11.C.10_EU_202303171905.

You did a great job! Thank you!
PS. Dacă ești român, ești foarte tare frate!

turistu said:
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
Click to expand...
Click to collapse
Hello there,
I tried your method, I did everything step by step and it actually worked and it did unlock the bootloader.
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Now I really do not know what to do -.-
Any advice would help.
Thanks Rob

RobertoSt25 said:
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Click to expand...
Click to collapse
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?

turistu said:
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
Click to expand...
Click to collapse
yes top of the screeen is START green, but when I pressed power just keeps rebooting into fastboot.
RMX 3474 REALME 9 5G
Thanks