Database Users

[GUIDE step by step] How To Re-lock Boot loader on Xperia Arc

First of all thanks Blagus for creating magical little file.
If you want your warranty back, follow this tutorial!
Requirements:
1. PC Companion and Update Service installed on your PC
2. FlashTool_0.2.9.1.exe – http://www.multiupload.com/7H4JT35B6G
3. Xperia Relock bootloader.ftf – http://www.mediafire.com/?g1b5j712ajx4yjd
Step by Step Guide:
1. Download the files given above in requirements.
2. Double click on ‘FlashTool_0.2.9.1.exe’ file to extract it, Or you can use free software like ‘7 zip’ to extract it.
3. Few files and folders will be extracted — the one which we’ll be using for flashing “Xperia Relock bootloader.ftf” files is the “firmwares” folder.
4. So copy the “Xperia Relock bootloader.ftf” file that you downloaded above, and paste it inside the “firmwares” folder.
5. Now double click on the “X10FlashTool.exe” file to run the program.
6. Once the program opens — click on the “Flash” button.
7. You’ll see a screen like the image given below — click “Ok”!
{
"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"
}
8. Now it should ask you to connect your phone to the PC. So first plug the USB cable to PC, then pick up your phone and hold the “Back” key (key at the bottom left on your Arc), and then connect the USB cable to your phone. Remember you’ve to hold the “Back” key while connecting the USB cable to phone.
9. Once the phone gets connected — Flashtool will automatically start the flashing process.
10. Keep an eye on the Flashtool’s screen.
11. And once the process gets finished, disconnect your phone from PC and switch it ON.
Enjoy!
ALL CREDITS GOES TO BLAGUS
original thread
http://forum.xda-developers.com/showthread.php?t=1134335

Sony Arc s?
I know this question has been asked a lot, but will this work for sony arc s? and if it works, will sony arc s get the 1% battery problem ? Thank you

I also am interested in this method to close the bootloader is compatible with Xperia ARC S I very interested, there is some kind of problem, if supported, it works again FW update via OTA, SEUS, Pc compation
thanks

DESMOYO said:
I also am interested in this method to close the bootloader is compatible with Xperia ARC S I very interested, there is some kind of problem, if supported, it works again FW update via OTA, SEUS, Pc compation
thanks
Click to expand...
Click to collapse
No joy Flashing tft files from op on my arc s. I chose arc as no option for arc s. Then use this tool http://forum.xda-developers.com/showthread.php?t=1259617 successfully. However i cant turned on my phone( i think because i was on unlock bl kernel) then i use seus to repair. Finally i get relock my bl. Sorry my poor english.

teddymild said:
No joy Flashing tft files from op on my arc s. I chose arc as no option for arc s. Then use this tool http://forum.xda-developers.com/showthread.php?t=1259617 successfully. However i cant turned on my phone( i think because i was on unlock bl kernel) then i use seus to repair. Finally i get relock my bl. Sorry my poor english.
Click to expand...
Click to collapse
So this tool does not work for Xperia ARC S?
thanks

DESMOYO said:
So this tool does not work for Xperia ARC S?
thanks
Click to expand...
Click to collapse
Yes It does. But you should flash stock kernel first unless you intent to use seus directly to get stock rom like i did. I hope you understand what i mean. Once again sorry for my poor english.

teddymild said:
Yes It does. But you should flash stock kernel first unless you intent to use seus directly to get stock rom like i did. I hope you understand what i mean. Once again sorry for my poor english.
Click to expand...
Click to collapse
As I can install stock kernel again, I have only the kernel ...
Thanks for your help friend

Arc S (L18i) Users,
Unlocked Bootloader, and DooMKernel caused Problems for me. My Phone never got identified by PC companion thereafter. I wanted it so bad, So I decided to Reloack the Bootloader again.
Let me Save you lots of time,
Before Locking the Bootloader again,
If you're on DooMKernel, Reflash a Stock Kernel.
You can get the Stock Kernel, by Downloading the Stock FTF package and then Extracting it with 7zip. Find the Kernel.sin file and flash it using the Fastboot commands.
Once its done, If your device Still doesn't connect in USB mode, use SEUS and Update the firmware. No need to upgrade, Just re-install what you have.
SEUS needs the bootloader to be locked.

hi, so are you saying Re-locking your bootloader wont wipe out your phone ?
And Sony Already Took All Your Info When You Unlocked Your Phone So I Am Sure They Will Know That You Just Re-locked It Some How And Refuse To Fix It Either Way If Something Goes Wrong.

When i tried to relock my bootloader flashtool didn't see loader.sin i don't know what's wrong with it please help me...

so i want to ask a question about my kernel. Im using 4.0.3 ICS beta and im very happy with it. But when the time comes i wanna get my update for ICS officially and that's why i want to lock my bootloader again. My Kernel Version on "About Phone" is 2.6.32.9-perf [email protected]#1 . My question is: I know its not a stock kernel when it says SemcUser and stuff but can u explain or atleast give me a link for some instructions how to get my stock kernel back and is it doable with reflashing to a 2.3.4 GB ? Thanks in advance!

Worked like a charm on my Xperia Arc 4.0.2.A.0.62 LT15a.
Also I was able to repair my phone via sony pc companion
Although I was unable to find a way to get DRM files back, I have installed the never version of Sony Track ID from Google Play Store and restore that functionality..
Thanx electrash and Blagus, you guys are awesome!!

what i want to know is if this would work on the Xperia play
and what method of unlocking bootloader does this relock: test point or sony's method?

This is Q&A thread. Please move
Sent from my LT15i using xda premium

Is this suitable for LT18i?
Can the TFT file be used in the latest Flashtool, or does it need this version?

i used Xperia_Relock_bootloader.ftf to unroot my phone,
now when i try to turn it on it only vibrate one time and gives a small green led bling.
connecting to pc works but it only shows a connected phone with the pc companion.
i had Arconium 8.2 with doomkernel installed.

thanks mannnnnnn
thanks man u r the best if i cud press the thanks button 1000 time i will:good:
q\ i did install ics jb remix after that i did stock on sony logo then locked the boot loader with your trk and it works again thanks
do i need a custom kernal for custom roms????????????

After flashing Xperia Relock bootloader.ftf i can't no longer unlock the bootloader on my Xperia Pro,
i am being returned this when i try to unlock the bootloader.
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.004s

does it work wit the latest flashtool?

electrash said:
First of all thanks Blagus for creating magical little file.
If you want your warranty back, follow this tutorial!
Requirements:
1. PC Companion and Update Service installed on your PC
2. FlashTool_0.2.9.1.exe – http://www.multiupload.com/7H4JT35B6G
3. Xperia Relock bootloader.ftf – http://www.mediafire.com/?g1b5j712ajx4yjd
Step by Step Guide:
1. Download the files given above in requirements.
2. Double click on ‘FlashTool_0.2.9.1.exe’ file to extract it, Or you can use free software like ‘7 zip’ to extract it.
3. Few files and folders will be extracted — the one which we’ll be using for flashing “Xperia Relock bootloader.ftf” files is the “firmwares” folder.
4. So copy the “Xperia Relock bootloader.ftf” file that you downloaded above, and paste it inside the “firmwares” folder.
5. Now double click on the “X10FlashTool.exe” file to run the program.
6. Once the program opens — click on the “Flash” button.
7. You’ll see a screen like the image given below — click “Ok”!
8. Now it should ask you to connect your phone to the PC. So first plug the USB cable to PC, then pick up your phone and hold the “Back” key (key at the bottom left on your Arc), and then connect the USB cable to your phone. Remember you’ve to hold the “Back” key while connecting the USB cable to phone.
9. Once the phone gets connected — Flashtool will automatically start the flashing process.
10. Keep an eye on the Flashtool’s screen.
11. And once the process gets finished, disconnect your phone from PC and switch it ON.
Enjoy!
ALL CREDITS GOES TO BLAGUS
original thread
http://forum.xda-developers.com/showthread.php?t=1134335
Click to expand...
Click to collapse
flashtool link is unavailable
do we have to use this version of flashtool or can we use the latest??

[ALL-IN-ONE][HOW-TO][D5803] Bootloader Unlock/Relock/Flash firmware/CWM Recovery/Root

Hello
I have done this on two Xperia Z3 Compact phones this weekend in Bulgaria, bought from local mobile operator. I wanted the latest Sony firmware, so I did the following:
How to install the newest Android 4.4.4 for Sony XPERIA Z3 Compact D5803
CAUTION
There is information, that users who have unlocked the new Xperia Z3 Compact have found that low-light camera performance drops considerably. It turns out to be because of DRM in Sony's image signal processing.
When the bootloader is unlocked, the device loses certain DRM security keys. That means you can't purchase content from Sony's storefronts and a few licensed features won't work, but it apparently also means basic features of the phone are negatively affected. A Sony rep has confirmed that some advanced camera algorithms on the new generation of devices like the Z3 and Z3 Compact are protected by DRM. If you unlock the phone, those features stop working. Apparently that causes photos in low-light to be noisier and poorly balanced.
This isn't the first time Sony's bootloader unlock has come with some major drawbacks—unlocking past devices could actually break camera functionality (this was technically a bug). There have always been a few proprietary features that stop working, but the difference in image quality this time is allegedly noticeable.
Update: Sony has updated the text of the bootloader unlock warning on its website to be clear about the camera impact. It reads, "...the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected."
Relocking your device bootloader will NOT get back the lost DRM Keys... Once locked, they will be lost forever! More info cant be found HERE
More detailed info and explanations can be found HERE
Click to expand...
Click to collapse
1. PREPARATION
1) First of all, check your firmware version (if you already have the newest one, you do not need to download it, so skip step 3) and step 4), that are below. Just proceed with step 2) -> 5) from the PREPARATIONS (this) tutorial . Steps in the other tutrials are absolutely needed! Dont skip any of them!)
2) Download and install latest Flashtool from here (Latest Flashtool for Xperia Devices)
3) Download also latest Sony Original Firmware - 23.0.A.2.105 - Android 4.4.4 ( Mega Download ) for Sony XPERIA Z3 Compact
4) Paste the .ftf file downloaded in step 3 in folder „Firmware“ in your Flashtool installation folder. (for example for me is C:/Flashtool/Firmware)
5) Go on Sony Mobile site and download the Sony PC Companion. You must install it, because it installs some important drivers for your device. Since Sony stopped the Update Service application, now all the job is done from PC Companion.
a) After you installed the PC Companion, you must launch it and download the "Support Zone" addons from the main menu.
b) After that you must go in your Flashtool installation folder and find the Drivers folder. Go in it and install the Flashtool drivers for your device.
IMPORTANT
It is important to install Flashmode and Fastboot drivers with the driver for your device! Otherwise it will cause some problems during the flash procedure.
So now we're going into the real part of the things
2. BOOLADER UNLOCK
1) Go on Sony Mobile Developers website, register, enter your device IMEI and it will generate an unlock key for your device. Write it down!!!
1) Start Flashtool application and click on BLU button on the top
2) Turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
3) Copy the unlock key, that was given to you earlier from Sony Website to Flashtool window and than click unlock button
4) When you are prompted, disconnect your phone and connect the phone again, but this time with holding volume up button when Flashtool shows pop up window
5) Wait the unlock process to finish
6) Disconnect your phone and start it up. If it boots normaly, than all is DONE. Congratulations! You have unlocked your bootloader!
3. BOOTLOADER RELOCK
1) Download and install latest Flashtool from here (Latest Flashtool for Xperia Devices)
2) Start Flashtool and click on BLU button on the top
3) Turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
4) Just click on relock button and your bootloader is locked again
4. Flash Sony XPERIA Z3 Compact Latest Firmware - 23.0.A.2.105 - Android 4.4.4
1) Ensure yourself that you have the .ftf. that you downloaded in the PREPARATION process into the Firmwares folder of your Flashtool
2) Do not connect the phone to the computer yet. You must first open the Flashtool application, click on flash (the thunder) and choose Flashmode, than choose the firmware that you have downloaded and click ok.
3) Now turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
4) After few minutes of flashing, all is done!
IMPORTANT
The process is pretty slow! DO NOT DISCONNECT your phone during the proccess! Leave it still and for it to finish the flashing process! When it is DONE, Flashtool will say Disconnect and turn on your device (not a pop-up, just a line at the bottom of the other lines of words)!!!
If the device boots normaly, it should be factory reseted and it will boot slowly. Much slowly than normal.
Congratulations! You have the lates firmware from Sony!
5. Flashing ClockWorkMod Recovery
1) Download the kernel image with integrated CWM Recovery from HERE
2) Save the boot.img to folder of your choice
3) Open Flashtool, click on the Flash (thunder) and choose Fastboot. Choose "Choose file to flash" under the DooMLoRD "side" of the opened window. Then choose the folder, that you have saved the boot.img in and then choose the .img file itself.
4) Follow the instructions. There are two posibilities - the phone will reboot itself and go into Fastboot mode without you touching it OR you must turn-off the phone, hold the volume up key and connect phone to computer.
5) The flashing will finish verry fast. Wait for it and when it is done, disconnect you phone and turn it on. When Sony logo appears, start pressing the volume down button rapidly, until it enter the recovery mode. And you're ready to go!
6. ROOT
IMPORTANT
You must ensure yourself, that you have falshed the kernel boot.img WITH the CWM Recovery!
1) Once you have flashed the kernel boot.img WITH the CWM Recovery download the latest SuperSU update.zip from: HERE
2) Save the downloaded .zip file on sdcard of device
3) Reboot into recovery and choose "Install ZIP from sdcard" and then "Choose ZIP file to install" (moving thru options is vol up / volume down keys; choosing an option is power button)
4) Choose the .zip file that you have downloaded on your sdcard and the installing should begin
5) After a while the installing should be finished you the recovery will bring you into the menu, that was just before the installation begin. You must choose "Go back" and then "Reboot"
6) The recovery will say you, that the root permisions must be fixed befor rebooting - choose ok / accept or fix (don't remeber what was the opiton really...)
7) If all is OK the phone must boot normaly ( the first time it will say "Upgrading Applications") and after that in the applications menu you must have an applicaion, named SuperSU. If you have it - Congratulations! You have rooted you phone successfully!
7. Installing BusyBox
It is highly recommended to install busybox after rooting!
You must just go to andorid play store and download the busybox installer. Once the installer is downloaded start it and choose to install busybox in /system/xbin. After the installation is done, reboot the device and you're done!
-------
Special thanks (and apologize for using their files) to:
DoomLoRD - CWM Kernel, CWM Kernel Flashing and Rooting / BusyBox installing guide! - Sorry for using your files man, but I think that the users deserve at least one ALL-IN-ONE tutorial! Please, forgive me!
Unknown User from other website - Bootloader Unlock / Relock / Latest Firmware flash (with some additional explanations from me and my expirience! )

nowhere you mention that unlocking loses DRM keys and relocking will not get it back - you really need to include this vital info!

Bäcker said:
nowhere you mention that unlocking loses DRM keys and relocking will not get it back - you really need to include this vital info!
Click to expand...
Click to collapse
Yes, you're right. I've added the info at the begining of the post! Thanks for fast reply!

Moderators, please consider to make this thread an important one! Thank you!

up ^

Is the only downside of missing the DRM keys the camera?? How bad does it actually get?

crxmax said:
Is the only downside of missing the DRM keys the camera?? How bad does it actually get?
Click to expand...
Click to collapse
There is a topic that compares pictures with and without an unlocked BL.
The problem is if you unlock your BL and you send your phone back for repairs, chances are very big that they will refuse to repair your device.
Hence being able to re-lock it and regaining the keys is almost a must.

Thanks!! It works a lot!

Dsteppa said:
There is a topic that compares pictures with and without an unlocked BL.
The problem is if you unlock your BL and you send your phone back for repairs, chances are very big that they will refuse to repair your device.
Hence being able to re-lock it and regaining the keys is almost a must.
Click to expand...
Click to collapse
Well since you unlock your BL through Sonys website they'll know If its been unlocked...regardless If you relock it.

For a guide which details unlocking bootloader, you should probably include backing up TA partition using this tool
Do it after root, before unlocking bootloader. Then if you want DRM stuff back, you can restore the TA backup using the same tool; this automatically relocks the bootloader, then flash a stock kernel (& rom if you need) & it will be in 'factory' condition

Hi, I followed the steps exactly and everything went perfect. However, I downloaded CM nightly and when i try to install it, i get an error msg that says that the nightly zip file is for zc3, while my phone is aries (which i believe is Xiomi MI2). The model number of the phone still says d5803, so I am not sure why its recognized incorrectly.
Any ideas, anyone?

@ThunderBird891 Where did you get the boot.img from under " 2) Save the boot.img to folder of your choice" of flashing cwm ?
Also, the "choose file" option in flashtool isn't there in fastboot mode. There is "select kernel to flash" but it's looking for .sin files and not .img files, am i missing something here ?
I've flashed with cm12, but i'd like a proper recovery and root.

flintfirewalker said:
Hi, I followed the steps exactly and everything went perfect. However, I downloaded CM nightly and when i try to install it, i get an error msg that says that the nightly zip file is for zc3, while my phone is aries (which i believe is Xiomi MI2). The model number of the phone still says d5803, so I am not sure why its recognized incorrectly.
Any ideas, anyone?
Click to expand...
Click to collapse
I believe that, by now, you got the answer to this question... Yeah, I don't know why this is happening, you won't have this issue after flashing CM12 / CM12.1 the first time since all the upgrades will be done through Cyanogen Recovery which seems to work ok for updates.
Anyway, you need to remove the first line (pretty long one, so be careful) in the updater-script. You can find the updater script in the CM12/ CM12.1 zip archive, under META-INF/com/google/android/updater-script. If you're running Windows, please, make sure you edit this script using Notepad++, not Notepad.

Hi guys, i have a problem.
I need to prepare my xperia z3 compact to be stock cause i will carry my telephone for repair my glass.
I had tried to relock the bootloader with flashtool but without success.
When i click on "BLU" button, there is the popup, i power off my z3c and then i plug the usb with the volume button down pressed. The pop up with the instructions disappear for 2 seconds and device seems connected.
But after 2 seconds apear another popup:
{
"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"
}
I've tried to plug the usb cable when i press the menu button (power button, yes?) but device remain powered off and no changement on flashtool.
What is wrong?
Another question: after (i hope) bootloader relocked, how can i restore the drm keys and how can i have a full stock device?
Thank you so much and sorry for my bad english sometimes...
EDITED:
Guys, i am so confused, my bad: i have never unlock the bootloader, so for this i can't reblock it...
So sorry guys

Hiya, when I flash using that boot.img, my phone goes into a restart loop and I have to reflash firmware to have it functional again, losing CWM in the process. Is there another .img file I should be using? I've used both this method and the command line, both causing the same issue, so it's got to be this particular image. Or does this image only work with this firmware? I am updating to 5.1.1....26.

No way to relock bootloader on 6.0 at Z3+ Ivy

Hello guys, I tried to go back to stock today. I relocked the BL using flash tool and flashed 23.5.A.1.291 from https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706. After that the phone stucks in the Blue-wave starting animation.
Any hints how to get this work? I also like to patch the DRM fix. When should I do that?
Edit: Never mind: Just forgot to wipe appslog in Flashtool ^^

Still Can't unlock bootloader
Hello, I've done that, but, my bootloader still says "no" in * # * # 7378423 * # * # how to solve it? Please help ...
of course,I have flashed the kitkat version like the above method.

[RECOVERY] [TWRP] For YU Yunique YU4711

​
{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Code:
[SIZE="3"] * Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.[/SIZE]
Working :
Everything
Procedure :
First Unlock Bootloader
Switch off Device
Copy twrp_yunique.img to ADB Folder in Laptop or PC
Hold Volume Up + Power
Select Reboot to Bootloader
Hold Left Shift + Right Click in ADB Folder
Select Start Command Window Here
Type Command in ADB Shell { fastboot flash recovery twrp_yunique.img }
Then Type Command in ADB Shell { fastboot reboot ]
Phone will restart.
Now Switch Off Device Hold Volume up + power to Boot TWRP
Enjoy !! And press Thanks please.
I hope you all Understand Development is not a easy work, So please press the Thanks Button as much as you can to Encourage Me
Download :
ADB Drivers : LINK
Adb Tools for YU Yunique : LINK
TWRP For YU Yunique : LINK
Stock Recovery in case if you want Revert : LINK
Root Method :
If you Want Root Access then Copy SuperSU.zip to Internal SD Card and Flash wih TWRP : LINK
If you use my work in part of your ROM I have no problem but Give Proper Credits

Reserved 1

Reserved 2

Just got my phone yesterday. Will first check and test hardware and decide if something is amiss so that I can return it.
Then I will try your work. I am so relieved to have a custom recovery and root is available for this handset.
Till now been using only and only HTC since ten years....
This is a kind of 'backup' piece.
Looking forward to a custom ROM ...because though there is no junk OEM installs ...there is only around 4 GB internal memory available.
Thanks Anurag.

Semi-CM ROM on the Way
kalya said:
Just got my phone yesterday. Will first check and test hardware and decide if something is amiss so that I can return it.
Then I will try your work. I am so relieved to have a custom recovery and root is available for this handset.
Till now been using only and only HTC since ten years....
This is a kind of 'backup' piece.
Looking forward to a custom ROM ...because though there is no junk OEM installs ...there is only around 4 GB internal memory available.
Thanks Anurag.
Click to expand...
Click to collapse
Wait for Few Hours Semi-CM ROM will be up any moment for YU Yunique
Checks Screenshots for Now and Keep Patience !! & Press the Thanks Button

TWRP not working even after flashing thrice.

arunmcops said:
TWRP not working even after flashing thrice.
Click to expand...
Click to collapse
Try fastboot boot twrp_yunique.img
and in fastboot mode check fastboot devices

anuragdc said:
Try fastboot boot twrp_yunique.img
and in fastboot mode check fastboot devices
Click to expand...
Click to collapse
it gets booted in twrp but after i restart my device and again go back to recovery stock recovery comes up.

vinaysalunke said:
it gets booted in twrp but after i restart my device and again go back to recovery stock recovery comes up.
Click to expand...
Click to collapse
Download the image file of recovery and try flashing with rashr or flasher tool. It will get installed.
Hit thanks button if helped.:fingers-crossed::good:
---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------
anuragdc said:
Wait for Few Hours Semi-CM ROM will be up any moment for YU Yunique
Checks Screenshots for Now and Keep Patience !! & Press the Thanks Button
Click to expand...
Click to collapse
Anurag, it would be awesome if yunique gets full cm rom. Semi-cm rom is good but still lot of bugs like the stock rom. Hope you will be working for it and we get it soon.

I'm having a bit of an issue which i hope one of you can help.
I got the phone today, everything was working, so I decided to Unlock and install TWRP
everything went good
but when I pressed Volume Up + Volume Down + Power
The phone just stays on black screen
I get no ADB or FASTBOOT anymore
PC detects some "QHUSB_BULK" device
I can't turn it off, it won't respond to anything
did i just kill it by install TWRP ?

Sefy said:
I'm having a bit of an issue which i hope one of you can help.
I got the phone today, everything was working, so I decided to Unlock and install TWRP
everything went good
but when I pressed Volume Up + Volume Down + Power
The phone just stays on black screen
I get no ADB or FASTBOOT anymore
PC detects some "QHUSB_BULK" device
I can't turn it off, it won't respond to anything
did i just kill it by install TWRP ?
Click to expand...
Click to collapse
On the black screen you get fastboot mode. On pc, you need to install the drivers. Google qhusb_bulk drivers installation and follow the instructions. After installing the drivers, you will get fastboot and adb.
Installing custom recovery doesn't affect this.
Hit thanks button if i helped.

vikphogat said:
On the black screen you get fastboot mode. On pc, you need to install the drivers. Google qhusb_bulk drivers installation and follow the instructions. After installing the drivers, you will get fastboot and adb.
Installing custom recovery doesn't affect this.
Hit thanks button if i helped.
Click to expand...
Click to collapse
Even after installing the drivers, the phone wasn't accessible from ADB or Fastboot.
However, after pressing the Power Button for atleast 15 sec, the phone decided to turn on
So I was able to flash CWM and then TWRP and installed CM 12.1 :silly:

Sefy said:
Even after installing the drivers, the phone wasn't accessible from ADB or Fastboot.
However, after pressing the Power Button for atleast 15 sec, the phone decided to turn on
So I was able to flash CWM and then TWRP and installed CM 12.1 :silly:
Click to expand...
Click to collapse
You may not access adb after doing tha, but fastboot is available. You can connect to pc and install stock firmware by doing that.
Restart your phone into fastboot and check if the pc is showing you same "qhsbulk_usb" device. Also tell me the version of your pc windows.

vikphogat said:
You may not access adb after doing tha, but fastboot is available. You can connect to pc and install stock firmware by doing that.
Restart your phone into fastboot and check if the pc is showing you same "qhsbulk_usb" device. Also tell me the version of your pc windows.
Click to expand...
Click to collapse
As i've mentioned, the problem was resolved but keeping the Power Button pressed for 15 sec and the phone turned on again.

Sefy said:
As i've mentioned, the problem was resolved but keeping the Power Button pressed for 15 sec and the phone turned on again.
Click to expand...
Click to collapse
Can u please clearly tell me what your problem was?
I think you said fastboot and adb is not working.
Is it working now?

Need help to unbrick my yunique
Hi Anurag,
After successful flashing Jalebi CM12.1 recovery image, I am unable to browse through internal or external storage.
Can you please help me.

I need someone to test a MM AOSP ROM for me. I don't own the device. Email me or hangouts me at [email protected] Please, need to get feedback asap.

Someone please try this rom. Tell me if it works. If not, logcats are amazing. http://desolationrom.com/aosp_jalebi-ota-eng.root.zip
It's aosp marshmallow

Issue with the recovery
anuragdc said:
​
TWRP is an open source .....
....
TWRP For YU Yunique : LINK
Stock Recovery in case if you want Revert : LINK
Root Method :
If you Want Root Access then Copy SuperSU.zip to Internal SD Card and Flash wih TWRP : LINK[/SIZE]
If you use my work in part of your ROM I have no problem but Give Proper Credits
Click to expand...
Click to collapse
Hey dude,
Thanks for the recovery and fabulous work.. However I am having some trouble with it. Whenever I am trying to flash a CM Nightly, It keeps on failing Saying this package is for device Yunique and this device is YU4711!! Just dosen't allow me to flash. I have unchecked signature verification. I have attached the log with this post, would you be so kind as to please look into it and let me know?
Cheers!
EDIT:
You can take a look at this ongoing thread on CyanogenMod forum to get the full picture of the issue I am facing.

ashhem said:
Hey dude,
Thanks for the recovery and fabulous work.. However I am having some trouble with it. Whenever I am trying to flash a CM Nightly, It keeps on failing Saying this package is for device Yunique and this device is YU4711!! Just dosen't allow me to flash. I have unchecked signature verification. I have attached the log with this post, would you be so kind as to please look into it and let me know?
Cheers!
EDIT:
You can take a look at this ongoing thread on CyanogenMod forum to get the full picture of the issue I am facing.
Click to expand...
Click to collapse
thats because this recovery is NOT for your device! there are 2 things you must check:
CHECK THEM CAREFULLY OR YOU GET A HARDBRICK
1. are all partitions set correct in recovery? /system /data /cache and /boot ?
2. why you use this recovery and not your own? us there a recovery for your phone?
if you are 100% sure partitions are set correctly.... then do the following ON YOUR OWN RISK :
go to advanced-> terminal
there enter:
setprop ro.product.device YUNIQUE
setprop ro.build.product YUNIQUE
then try to flash the rom.... like i said above be 100% carefully because if partitions are seted wrong you may get a hardbrick!!!
btw (to the dev) the terminal gets flooded by a mtp error
Sent from my Xperia T using XDA Free mobile app

***[Tutorial]Meizu MX4 Flash Factory KITKAT Test Firmware***

Disclaimer
We are not responsible for bricked devices,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Hard. A lot.
MX4 ANDROID VERSION:
DONWLOAD THE ROM
https://mega.nz/#!JQ0zHJLb!6Z_zL3SglvKh3r7BDjiiITe0S4ARR0zUgKo-Ifx1VyE
AND FLASH IT VIA RECOVERY
MX4 UBUNTU VERSION:
- MEIZU MX4 16/32
- SP FLASH TOOL
- DRIVERS
- FACTORY FIRMWARE
ALL THE FILES CAN BE DOWNLOADED FROM THIS LINK: https://mega.nz/#F!MkNnETAZ!GYPnBc8B_LMgdR1fNI0c_g
1
- TURN OFF THE PHONE
- OPEN DEVICE MANAGER
- PLUG THE PHONE TO THE PC AND HOLD VOLUME UP + POWER BUTTON (HOLD IT AND WATCH DEVICE MANAGER A UNKNOWN DEVICE POPUP FASTY)
- WHEN POPUP UPGRADE THE DRIVER OF THIS UNKNOWN DEVICE (FASTY) FROM THE FOLDER "Drivers Hard Reset"
- WHEN YOU DO IT TURN OFF THE PHONE BUT LEAVE IT UNPLUGGED
2
-UNZIP FACTORY FIMRWARE
- UNZIP SP TOOL "SP_Flash_Tool_exe_windows_v5.1424.00"
- UNZIP "DLL" AND INSTALL IT
- OPEN SP TOOL
- CHOOSE THE SCATTER (FROM factory_m75_1.5.0.21.test-signed)
- CHOOSE "FIRMWARE UPGRADE" (IF YOU DO DOWNLOAD YOU BRICK YOUR PHONE)
- CHOOSE THE DONWLOAD AGENT "DA_SWSEC.bin"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3
- PUSH "DOWNLOAD" ON SP TOOL
- ON PHONE TURNED OFF HOLD VOLUME UP + VOLUME DOWN AND PLUG IN IT (WHEN THE BAR COME RED KEEP OLD THE BUTTONS, WHEN THE BAR COME WHITE AND THE PROCESS START LEAVE VOLUME BUTTONS)
When the process finish you have an factory unlocked Meizu MX4 with KitKat. If you want try Ubuntu Touch look this thread----> http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
Thanks to Taras. Thanks to me for the tests. :good: :highfive:​

Naphtha said:
Disclaimer
We are not responsible for bricked devices,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Hard. A lot.
YOU NEED:
- MEIZU MX4 16/32
- SP FLASH TOOL
- DRIVERS
- FACTORY FIRMWARE
ALL THE FILES CAN BE DOWNLOADED FROM THIS LINK: https://mega.nz/#F!MkNnETAZ!GYPnBc8B_LMgdR1fNI0c_g
1
- TURN OFF THE PHONE
- OPEN DEVICE MANAGER
- PLUG THE PHONE TO THE PC AND HOLD VOLUME UP + POWER BUTTON (HOLD IT AND WATCH DEVICE MANAGER A UNKNOWN DEVICE POPUP FASTY)
- WHEN POPUP UPGRADE THE DRIVER OF THIS UNKNOWN DEVICE (FASTY) FROM THE FOLDER "Drivers Hard Reset"
- WHEN YOU DO IT TURN OFF THE PHONE BUT LEAVE IT UNPLUGGED
2
-UNZIP FACTORY FIMRWARE
- UNZIP SP TOOL "SP_Flash_Tool_exe_windows_v5.1424.00"
- UNZIP "DLL" AND INSTALL IT
- OPEN SP TOOL
- CHOOSE THE SCATTER (FROM factory_m75_1.5.0.21.test-signed)
- CHOOSE "FIRMWARE UPGRADE" (IF YOU DO DOWNLOAD YOU BRICK YOUR PHONE)
- CHOOSE THE DONWLOAD AGENT "DA_SWSEC.bin"
View attachment 3588241 View attachment 3588242
3
- PUSH "DOWNLOAD" ON SP TOOL
- ON PHONE TURNED OFF HOLD VOLUME UP + VOLUME DOWN AND PLUG IN IT (WHEN THE BAR COME RED KEEP OLD THE BUTTONS, WHEN THE BAR COME WHITE AND THE PROCESS START LEAVE VOLUME BUTTONS)
When the process finish you have an factory unlocked Meizu MX4 with KitKat. If you want try Ubuntu Touch look this thread----> http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
Thanks to Taras. Thanks to me for the tests. :good: :highfive:​
Click to expand...
Click to collapse
Give firmware flashtool 1,4,1

thanks for your job .can I flash it on my Android MX4?

CN_Victor said:
thanks for your job .can I flash it on my Android MX4?
Click to expand...
Click to collapse
Yes try

Cyka blyat'
Your method dosen't work on Meizu MX4 32Gb Android Edition from China (M460)

MEIZU MX4
dude it dose not work !
OK IM A BIT SUSPICIOUS AT THIS POINT ,, SO YOU SAY THAT YOUR INSTRUCTION WILL UNBRICK AND UNLOCK OUR BRICKED MEIZU MX4 PHONES BUT WHY DONT YOU SHOW US A SCREENSHOT OF SP FLASH TOOL WITH THIS FANCY RED LINE THAT PROVES THAT YOUR INSTRUCTION ACTUALLY WORKS

BROM ERROR: S_BROM_CMD_STARTCMD_FAIL(2005)
[BROM] Can not pass bootrom start comand! Possibly target power up too early.
[HINT]:
Hi Naphtha, this error appear to me when I connect the phone after to push download in sp flash tool. Any idea? Thank's a lot.
Edit: Other error.
BROM ERROR: S_AUTH_HANDLE_IS_NOT_READY(5000)
[User] This is a secure base-band chip! Please select the authentication file first
[HINT]

MeNa82 said:
BROM ERROR: S_BROM_CMD_STARTCMD_FAIL(2005)
[BROM] Can not pass bootrom start comand! Possibly target power up too early.
[HINT]:
Hi Naphtha, this error appear to me when I connect the phone after to push download in sp flash tool. Any idea? Thank's a lot.
Edit: Other error.
BROM ERROR: S_AUTH_HANDLE_IS_NOT_READY(5000)
[User] This is a secure base-band chip! Please select the authentication file first
[HINT]
Click to expand...
Click to collapse
You have it! Try to "format whole bootloader" on SP flash tool. Hold volume up + volume down.

Naphtha said:
You have it! Try to "format whole bootloader" on SP flash tool. Hold volume up + volume down.
Click to expand...
Click to collapse
What do you mean? In section "format" appear:
validation start stop
auto format flash
manual format flash
auto format flag
format whole flash
format whole except bootloader
I tried the 2 last options and appear the same 5000 error

you have 2 errors : 1 for auth and 1 for fast-start up. The first come because you don't hold good volume down and volume up the second can come for the partitions damaged.
Use volume down ad volume up and choose format whole except bootloader". Try this.

Naphtha said:
you have 2 errors : 1 for auth and 1 for fast-start up. The first come because you don't hold good volume down and volume up the second can come for the partitions damaged.
Use volume down ad volume up and choose format whole except bootloader". Try this.
Click to expand...
Click to collapse
may i ask you how much cost to repair meizu mx4 in Italy ?
P.S. your instruction work because you have/had unlocked boot-loader and thats why you can easily install any firmware .. meanwhile me and other users who have locked bootloader from the factory can not install any of those firmware .. we can't even flash firmware via sp flash tool because MEIZU locked our phones in the factory .

ertog said:
may i ask you how much cost to repair meizu mx4 in Italy ?
P.S. your instruction work because you have/had unlocked boot-loader and thats why you can easily install any firmware .. meanwhile me and other users who have locked bootloader from the factory can not install any of those firmware .. we can't even flash firmware via sp flash tool because MEIZU locked our phones in the factory .
Click to expand...
Click to collapse
Yes but this is an factory firmware with factory tools. Is impossibile.

Naphtha said:
you have 2 errors : 1 for auth and 1 for fast-start up. The first come because you don't hold good volume down and volume up the second can come for the partitions damaged.
Use volume down ad volume up and choose format whole except bootloader". Try this.
Click to expand...
Click to collapse
Forget de first error, may be I didn't press the botons correctly. But now , always appear the second error:
BROM ERROR: S_AUTH_HANDLE_IS_NOT_READY(5000)
[User] This is a secure base-band chip! Please select the authentication file first
[HINT]
Any one with brick phone can try it?

MeNa82 said:
Forget de first error, may be I didn't press the botons correctly. But now , always appear the second error:
BROM ERROR: S_AUTH_HANDLE_IS_NOT_READY(5000)
[User] This is a secure base-band chip! Please select the authentication file first
[HINT]
Any one with brick phone can try it?
Click to expand...
Click to collapse
Error known by many people here.
You will find many people in your case here http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
No solution to date.

ouigo said:
Error known by many people here.
You will find many people in your case here http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
No solution to date.
Click to expand...
Click to collapse
Bad news
Enviado desde mi GT-I8260 mediante Tapatalk

On SP flash tool you have another preloader and scatter, try to flash it

Naphtha said:
Yes but this is an factory firmware with factory tools. Is impossibile.
Click to expand...
Click to collapse
WHAT PHONE MODEL YOU HAVE ???
IS THIS MEIZU UBUNTU EDITION ?
WHERE YOU BOUGHT YOUR MEIZU PHONE ?
HAVE YOU VISITED BEFORE SERVICE CENTER TO FIX YOUR PHONE ?
ITALIAN
COSA MODELLO DI TELEFONO HAI ???
E 'QUESTA EDIZIONE MEIZU UBUNTU?
Dove è stato acquistato IL TELEFONO MEIZU?
Avete visitato PRIMA DI CENTRO DI ASSISTENZA PER FISSARE TUO CELLULARE?

Naphtha said:
On SP flash tool you have another preloader and scatter, try to flash it
Click to expand...
Click to collapse
Nothing to do
Is there a phisical methode to force the download mode? I remember the samsung galaxy s could enter in download mode with the heat from a hair dryer. Perhaps , removing the battery...

ertog said:
WHAT PHONE MODEL YOU HAVE ???
IS THIS MEIZU UBUNTU EDITION ?
WHERE YOU BOUGHT YOUR MEIZU PHONE ?
HAVE YOU VISITED BEFORE SERVICE CENTER TO FIX YOUR PHONE ?
ITALIAN
COSA MODELLO DI TELEFONO HAI ???
E 'QUESTA EDIZIONE MEIZU UBUNTU?
Dove è stato acquistato IL TELEFONO MEIZU?
Avete visitato PRIMA DI CENTRO DI ASSISTENZA PER FISSARE TUO CELLULARE?
Click to expand...
Click to collapse
Normal MX4 32gb returned from customer service.

Naphtha said:
Normal MX4 32gb returned from customer service.
Click to expand...
Click to collapse
it was official meizu costumer service ?

Apply update from sdcard FAILED : Rooted Crosscall Trekker M1 on BOOTLOOP

Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !

Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?

-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can

Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip

-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it

Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)

-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"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"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788

Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?

Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?

-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?

Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers

-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit

After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.

Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset

-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.

Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted

-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.