Question Possible to get Android 12 via China rom? - Lenovo Legion Phone Duel 2

So my question is that is it possible to flash China rom to global version and get OTA upgrade to android 12 as I heard china devices are getting zui 13?

It's available here. If you attempt to flash it, make a .qcn backup of your nv data first. You can attempt to flash it with these instructions (7th post), only if you have all the drivers necessary for both LMSA/RSA & QPST/QFIL and know how to set it up correctly (firehose config needs to be set to not erase; you will need to set storage type to ufs).

Problem is i cant unlock the bootloader yet cause adb devices command doesnt show up the phone. Tried couple of drivers but didnt work.

You don't need to unlock your bootloader as it will most likely be relocked once you flash it. Do you have these (not just for OnePlus8, for all Qualcomm devices)?

Ok I was able to connect and unlock bootlader. I am downloading China rom now and will try flashing using the instructions. Hopefully it doesn't get bricked.

Make a backup of your nv data (QCN) first. Then do both edit 1 & edit 2 of the instructions posted and make sure to do it carefully, or if you're brave enough do only edit 2.

So I followed the instructions and after flash it went black screen. It doesn't boot or get detected by RSA. Only thing I can do is QFIL detects COM6 port when connected

Force shut it down, hold power until screen flashes on. You forgot to check "Reset after downloading". If that doesn't work you will need to use the other firehose protocol (lite) and that should restore it to a booting state.

&(*) said:
Force shut it down, hold power key for until screen flashes on.
Click to expand...
Click to collapse
I think its in EDL mode cause nothing else happens. Do you use telegram or whatsapp?

Holding power doesn't do anything? It should at least shutdown and reboot and if the screen briefly flashes then yes it is in EDL. You will need to flash it back to Global or whatever was previously on it. Did you unlock the bootloader first or not? That might have been the issue.

Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...

bukeyolacan said:
Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...
Click to expand...
Click to collapse
Okay, try flashing it again with the firehose config option checked "Reset after Downloading". You used EDL to flash it the first time, right? If you still get a black screen you will need to flash the original Global firmware back onto it. You state that RSA doesn't find it? Did you unplug and plug it back in or leave it plugged in?

One other thing you might of forgot to change, storage type to UFS.

I tried firehose flash many times but keep getting sahara fail error or process fail. Storage type was always ufs I never touched it

Use firehose lite and check to see if device manager shows any yellow exclamations now.

Tried lite now, there is android device in device manager with yellow

Is it possible for you to connect remotely via teamviewer or do you know someone that can fix if I pay?

You can fix it. Just try updating the driver automatically and see if it finds it first

&(*) said:
You can fix it. Just try updating the driver automatically and see if it finds it first
Click to expand...
Click to collapse
I think its out of my level now, would need some help with it

The driver package you installed will read the USB ID and should find it within DriverStore. Right click on the android device that has the exclamation and update the driver.

Related

Bricked Redmi note 3, please help.

The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.

Need help with bricked kenzo

I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.

Alcatel flash plus 2 doesn't boot after root

Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
EFAYSAL said:
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
Click to expand...
Click to collapse
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
SubwayChamp said:
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
Click to expand...
Click to collapse
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
EFAYSAL said:
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
Click to expand...
Click to collapse
Ok, I guess that your device is actually in bootloop and don´t booting.
Tutorial that you followed has many steps and don´t need to do all this to just root device and it contains some files like lk.bin that you can´t be sure that should be for your device.
Some users use this file (lk.bin) of an unlocked device and think that flashng in other device then get unlock it but no need, your device can be unlock it just follow some commands in fastboot mode.
Now you can do the next;
Try to flash again your rom stock (I guess that you don´t have a backup), if for some reason your official tool doesn´t work then use only some images like boot, system and userdata with the scatter.txt to flash them through SP Flash Tool.
Here a link to TWRP https://youtu.be/6vj_BY6xJdA, you can root it with supersu v2.78 0r v2.82 and here some files that can be usefull too https://drive.google.com/uc?id=0BwJgeCYTpnEHNlg2VUlieHFTYVU&export=download
Update steps that you are following to can assist. What extension has your rom and if it is recogniced for SP Flash Tool. I didn´t ask you if you can enter to fastboot mode and if you can then you can know if your bootloader is unlocked typing fastboot oem info
Most info that you give and some screenie will help to understand better
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
EFAYSAL said:
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
Click to expand...
Click to collapse
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
SubwayChamp said:
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
Click to expand...
Click to collapse
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
EFAYSAL said:
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
Click to expand...
Click to collapse
I´m not sure if you are connecting correctly your device at right time and form to can flash it properly. Every device has more or less a specific way to do it. My last alcatel it was connected just with device power off and after to tap on download, but in other device Blu Dash was connected pressing just vol_up and my last mt6757 Bluboo had to press both vol up and down at time to connect to pc and after to tap on download option. To have sure that is well done increase volume in your pc, you will hear a first sound that is cause pc is recognicing but then you have to hear a second sound that is when SPFlashTool is recognicing device and you will see a red line in down side of the tool window, release button inmediately and let tool to work.
This is a good rom for your device according the author is optimized https://droid1311.blogspot.com/2017/08/alcatel-fl02-aka-flash-plus-2-via.html and this is the link directly if you have troubles with pop-up-adds https://drive.google.com/file/d/0BwAGh1drb91SeDZwV1VXbXpjQWM/view
Also you can try with other versions of SP Flash Tool, most stable maybe should be v5,1628 https://androidmtk.com/smart-phone-flash-tool leth me know how you go
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
SPFlashTool 5.1628:
I try all the way with and without pressing any button but no luck . And when it work finishing with error.
SPFlashTool 5.1628:
I try all the way to get that mode but nothing works. So I try to click download button then conect the phone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
EFAYSAL said:
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
I try all the way to get that mode but nothing works. So I try to click download button then conect the pkone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
Click to expand...
Click to collapse
There is a part that is not variable in the way to use this tool, ever you have to tap on download before to connect device and is recommendable too connect cable usb to pc (not yet to device); from here is when the button that you have to press can vary but like I said you before in my last mt6757 (a very similar to yours) works pressing both vol at same time to connect terminal cable to device and now you will see a red line (could be violet-ish)
Try before just flashing only preloader file to recreate some partitions and then do other flash for the other files.
Of course you have to be sure that all drivers are installed correctly cause this tool needs to put your device in download mode (a special level) and also keep it in this state so find VCOM drivers for Alcatel and adb/fastboot installer and try to uninstalling some older drivers that you don´t use and many times we keep in our pcs and for a short data transmission can helo that all the rom move it in same folder where SPFlashTool is allocated.
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
EFAYSAL said:
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
Click to expand...
Click to collapse
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
- In what android version are you, 6.0?
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
- Did you try to flash just preloader, only this file?
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
SubwayChamp said:
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
Click to expand...
Click to collapse
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
SubwayChamp said:
- In what android version are you, 6.0?
Click to expand...
Click to collapse
Yes, last time it was 6.0 before the root
SubwayChamp said:
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
Click to expand...
Click to collapse
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
SubwayChamp said:
- Did you try to flash just preloader, only this file?
Click to expand...
Click to collapse
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
SubwayChamp said:
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
Click to expand...
Click to collapse
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
EFAYSAL said:
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
Yes, last time it was 6.0 before the root
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
Click to expand...
Click to collapse
You need to try two different ways to flash files and restore your device.
First method: fastboot mode
You need to get device enter to fastboot in order to flash some files like system, boot and userdata, then there are two main methods to do it:
- Pressing pwr + vol down
- And I mentioned that sometimes work pressing both volume button + pwr and a menu have to appear to can select an option to enter to (fastboot mode), in some devices this method is not working but you have to try several times attempting to.
Second method: SPFlashTool
You have to ever press first of all Download box and connect terminal cable to pc and the buttons thhat you need to press at time to connec cable usb to your device may vary, sometimes vol down, sometimes both vol but never pwr button; if pc recognice then you have to release all buttone an let it pc continue the flash process.
If SPFlashTool recognice device first flash only preloader file and select now lk.bin too. Flash only these two files and after do again a new flash with the rest of the files, Why you need to do this? your partitions are corrupted and you need to restore them with these files in order to can flash all another files.
Before all of this charge your battery, if you have a cover removable then extract it some minutes and put it again.
Also I read that for this model it´s used this tool instead of SPFlash Tool https://androidmtk.com/download-sugar-mtk-sp-flash-tool (inside the zip you will find a password to start the tool) but I´m not sure what kind of rom it needs, you have to connect your device to begin the process, you will find in product models section in the tool this variant for your device "FL02"
Try first the other tool and then this and let me know how you go, mtk devices are almost unbrickeable so it´s just to find the appropriate way to return it to the life.
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
EFAYSAL said:
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
Click to expand...
Click to collapse
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
I understand that you tried with Sugar tool with no lucky.
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Is there some custom development, recovery, roms for your device?
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
SubwayChamp said:
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
Click to expand...
Click to collapse
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
SubwayChamp said:
I understand that you tried with Sugar tool with no lucky.
Click to expand...
Click to collapse
Yes. After recognizing it keeps trying to download data but no luck.
SubwayChamp said:
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Click to expand...
Click to collapse
I know it is disappointing!. I try this but no luck.
SubwayChamp said:
Is there some custom development, recovery, roms for your device?
Click to expand...
Click to collapse
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
SubwayChamp said:
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
Click to expand...
Click to collapse
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
EFAYSAL said:
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
Yes. After recognizing it keeps trying to download data but no luck.
I know it is disappointing!. I try this but no luck.
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
Click to expand...
Click to collapse
I´ll tell you some ideas with no any specific order that you can try or see if works.
Really very strange that display stays in black, you told me that flashing files through fastboot is working but doesn´t appear not even bootlogo, connect to pc as it is and see how pc recognices in devices manager and my pc if appears like a determined drive d/e/f so it looks that some bad flashing burn your kernel and this case is similar to when a Samsung device need to use jtag method to revive, if in your country no-one knows about Alcatel devices this could be a similar case to what I´m saying then it could be a clue for a technician. I tell you this cause many time ago when I flashed by error a Samsung s4 and only this method revived my device.
Try this, flash your stock recovery only through SPFlash tool and flash after through Alcatel Download tool your stock rom cause some firmwares need to detect stock recovery first to can flash other partitions.
At this stage don´t you have stock recovery, no? so you can try to format data cause sometimes when bootloader is altered then avoid to boot and formatting data can solve this.
If this recovery twrp is for your device you can try flashing through SPFlash tool, you have to put recovery.img and scatter-txt in a same folder. then if succesfull format data, system, wipe cache and dalvik and maybe later try to port some custom rom would be a way to solve this.
To flash any partition through fastboot this is the syntax, just follow one by one any of the files that are in your rom folder so just follow these, if some of then can´t be flashed don´t worry then it´s not flashable:
fastboot flash boot bot.img
fastboot flash cache cache.img
fastboot flash lk lk.bin
and so on till the end
...But after try this if you didn´t get boot to recovery and obviously you can´t delete data nor system then delete first the next partitions trough fastboot typing:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
Try all this and let us see how it goes
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
EFAYSAL said:
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
View attachment 4518365
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
Click to expand...
Click to collapse
I see that Sugar tool detects your device like rooted and refuses to flash anything, compare imei number which is in the box, I hope that it couldn´t be changed.
Don´t tell me simply no luck, what it says in SPFlash tool when you tried to flash TWRP and I guess that you put scatter-txt and twrp renamed recovery.img simply in the same folder. Just to be clear, to can flash with this tool your device it has to be off not needed fastboot for this. (provide some screenie)
Other combination of keys to enter to fastboot to flash some partitions when something is missing is, try these three ways:
- Pressing only vol down and at same time connecting to charger (connect first one terminal of cable to your device and then to the charger)
- Pressing the three buttons till a menu appears (you must to release inmediately all)
- Pressing vol up + pwr till a menu appears (you must to release pwr button inmediately) then choose fastboot
In the post 4 I provided a link from Google Drive, in this zip there are 8 items;
- From the item 2 use this version of SP Flash tool, put the four files in a folder and flash them
- In the item 3 you will find some scripts for fastboot, maybe they´re working better and also you have here a subfolder with twrp image.
- And if you get sucessfully install twrp in the item 7 there is a backup with some files to restore from this recovery.
Try one by one and update the info, I hope that your motherboard is not damaged.

[GUIDE] EASY Axon 7 UNIVERSAL UNBRICK / FACTORY RESTORE

WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!​
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?

Question ONEPLUS Ace 2 BLACKDEATH AFTER FLASHING 11R OCDT.IMG

Hi everyone into this post thread.
We all know that converting chines ace 2 to oxygen os has some issues. We are trying our best to fix such issues, therefore trying different techniques. I had the same issue too, i read one post that flashing ocdt.img of 11R ll fix the issue, therefore, i took step to do it. After flashing 2487 ocdt.img, i restarted bootloader to normal. Phone booted, but still gets black, flicking and then goes black. I tried to restart it with keys, and phone wont detected by pc, even the bootloader was unlocked and usb debugging was enabled too. I tried enough to start in fastboot mode. But nothing, then i forcely start into EDL mode, and it deteceted. I purchased official authentication key to flash it back to coloros 13. The official tool failed to flash with error that image and product code mismatched and i loss money. Now dont know if i purchase a other authentication or wait for the developers to figure out issue.i have a complete flash tool logs, which is very useful for the developer.
Because in the stock image, they have made tachtis to keep users afftected and pay them to bring the devices back.
Pro opinion and fix is needed for everyone affected by this.
you need to flash china version (Ace2) ocdt.img again in your phone
make sure you have unlocked bootloader ( i know you have black screen). then go to fastboot and flash this file.
download file
power off ...
power on +( vol - )
connect cable
then in cmd write
fastboot flash ocdt ocdt.img
you have not orher way .. only this way can work 100%.
in OFP we have not OCDT image . so do not waste your time and money
I had tried enough to boot into fastboot, but phone dont boot, and dont know even this is booting or not due to black screen, i only know theat attaching cable vibrate the phone but it wont detected. Tried combination keys to boot i to bootloader, but no luck. I keep phone as it is to see if battery get drain and ensure that its power off and will try afternoon.
Thanks forsharing stock ocdt for this model.i would request you to kindly rename the file to this specific model, so people know about it. The flashing way is a same.
you need to keep all 3keys togather...
after 15sec it will go to EDL mode.. connect cable
after that ..
keep power + (vol- ).. after 15 sec it will go to fastboot
I face the same issue, I did wrong that FLASHING 11 (not 11 R) OCDT.IMG, The after-sales staff were unable to restore my phone, so they directly gave me a new one.

Categories

Resources