Hi everyone,
(Sorry if my english is bad) I recently saw Crosscall device must have a key to unlock their bootloader with fastboot (common way), and most of Crosscall devices are SnapDragon except the S4 Core, because there's an universal way for MTK to unlock the bootloader, without waiting time and key needed.
Requirements :
PC or Laptop (at least running Windows 10)
Crosscall Core S4
USB cable
/!\IMPORTANT/!\ : THIS PROCESS WILL WIPE ALL YOUR DATA, SO IF YOU HAVE IMPORTANT FILES BACKUP THEM BEFORE DOING THIS
Ready ? Go !
First : Install USBDK (depends on your processor arch download x64 for 64 bits and x86 for 32 bits)
Download MTKClient extract it and copy the extracted folder on your C: drive folder
Ok now open a Powershell session (if you're on W11) or a cmd session (if you're on W10)
{
"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 type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Related
Tutorial: How to transfer files to/from our Moto G while in TWRP recovery
This tutorial have been tested in 7, 8, 8.1 and 10 Windows versions. It can work with other devices beside Moto G.
{
"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"
}
Sometimes we need to transfer files to our device while we are in recovery mode. When we forget to copy the zip we were going to flash, when we are installing a
GPE based ROM (we must format /data and erase all files), to transfer a backup... ect. In many cases we need this function.
The purpose of this tutorial is to make our PC succesfully recognize our Moto G as a storage device being in TWRP recovery.
Many users have reported that their devices are not being recognized.
Requirements:
-Have installe the last TWRP recovery version.
-Have installed ADB drivers in PC. You can try this ones Universal ADB Drivers or Motorola Mobile Drivers 64 bits
-USB data cable.
-PC runnig Windows 7, 8, 8.1 or 10 (can work with older versions).Steps: Sorry for spanish images, if you can provide me english captures would be great.
1) Boot into recovery mode and connect to PC with USB data cable.
2) Being completely sure your device is not being recognized, otherwise this tutorial will be totally useless to you.
3) Open Control Panel and click on Hardware and Sound
4) Go to Device Manager.
5) Look for 'Android Device' or 'Android Phone' or any related name, open the list, rigth-click on the device and click on 'Update driver software'.
6) Now click on the second option.
7) Now click on the option below:
8) Make sure 'ADB composite device' is there and click next.
9) Once this is donde, reboot your PC and it will be in capacity to recognize your device as a storage device while you are in TWRP recovery. We can freely transfer files.---------------------------------------------------
Last Update: 17-07-2015
Reserved
Thanks
My phone is completely dead when I'm flashing RAW file using ASUS Flash Tool. Cannot do anything except pressing volume down and power to bring it to Cloverviewplus mode.
Flashing it with xFSTK also didn't work.
{
"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"
}
It will end with Timeout to detect the device.
HELP please!
Use this link https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
But don't use (3. Dowload and install iSocUSB driver: http://www.mediafire.com/download/7u...etup-1.0.4.exe).
Download iSocUSB-Driver-Setup-1.7.0.
what did you mean? forget step 3??
Tran Xuan Thuy said:
Use this link https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
But don't use (3. Dowload and install iSocUSB driver: http://www.mediafire.com/download/7u...etup-1.0.4.exe).
Download iSocUSB-Driver-Setup-1.7.0.
Click to expand...
Click to collapse
so you mean don't use step 3???
i'm stuck in file debrick.bat the massage is "isoc detecting device fail #attemp 0
than reconecting -- debrick.bat force close
what the problem?
1. Use the instructions at the link https://forum.xda-developers.com/zen...tboot-t3377455
2. But don't use (3. Dowload and install iSocUSB driver: http://www.mediafire.com/download/7u...etup-1.0.4.exe).
Dowload and install iSocUSB-Driver-Setup-1.7.0. (because iSocUSB-Driver-Setup-1.7.0 is the newer than iSocUSB-Driver-Setup-1.0.4 )
If you dowload and install iSocUSB-Driver-Setup-1.0.4 in windows 10, you stuck in file debrick.bat the massage is:
isoc detecting device fail #attemp 0
isoc detecting device fail #attemp 1
........
isoc detecting device fail #attemp 19
and close command prompt windows.
---------- Post added at 07:10 AM ---------- Previous post was at 06:52 AM ----------
You need to check if your PC has received your phone in cloverview mode.
Open Computer Management -> Device Manager - > Intel Soc : CloverviewPlus Device and Intel Soc USB Device.
SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 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"
}
Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.
Have you tried using cmd (administrator) istead of PowerShell?
Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes
It's really strange... Have you unlocked the bootloader?
Yes " Device State - Unlocked "
It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.
Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.
I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"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"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks
Same problem here. Please help.
Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.
If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"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"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.