I was searching for international Nougat roms for my Leeco cool 1 dual. I found 3-4 roms mosltly by Cuoco. But all have major issues whith this C103 device. No WiFi, not enough brightnes, no video capture, no mic.
I decided to turn to original MM rom then. But first i wanted to replace the JUI TWRP (One of the roms has installed it) with 3.2.1.0 TWRP. I make the flash without any errors. But after the restart of the device, JUI twrp logo appears again. But phone not go in the recovery. Just stays in Nougat twrp logo.
I tried to go in bootloader mode. Fails.
I tried to shut the device off. Fails. Its turn on by itself and stays at JUI recovery logo screen
I tried to go in recovery mode again. Fails.
I tried to put it in EDL mode. Fails
Then i decide to let the battery drain, and after that i put it in Bootloader mode. Then....
I tried different versions of Coolpad download assistant (latest v 1.59) in order to flash a new rom. Procedure allways fails with an error at the end. (is in Chinese)
I tried QFIL but app can see the device only at EDL mode.
I tried to put another TWRP via Fastboot but with the order fastboot device says ...searching for devices. It cant see the phone when in bootloader mode. (yes a have installed all drivers including qualcom usb drivers, google drivers, generic android drivers etc.)
I tried some versions of YGDP tool (latest v.5.00) but fails with this error..
21:28:17 CELL0: V4.0.3.0
21:28:17 CELL0: Cell 0 USB address is: 6&396408C&0&4
21:29:17 CELL0: Download Started...
21:29:17 CELL0: Downloading CPB:
21:29:17 CELL0: Init DownQueue...
21:29:17 CELL0: Device connected, start to download ...
21:29:17 CELL0: Get bootloader information ...
21:29:17 CELL0: Bootloader is new !
21:29:17 CELL0: Bootloader will not use CRC while system img!
21:29:17 CELL0: Bootloader does not support querying CID !
21:29:17 CELL0: Bootloader does not support querying Secure !
21:29:17 CELL0: Check device ...
21:29:17 CELL0: Jump eMMC check. User setting.
21:29:17 CELL0: Check phone name fail, The phone name 'C106' not contained in 'C1'
21:29:17 CELL0: Check phone name fail, Please check the 'ProductName' in the PhoneInfo.yl
21:29:17 CELL0: Check phone name fail !, msg:C106_P4
21:29:17 CELL0: Download failed,please try again!!
21:29:17 CELL0: Total download time elapsed: 0 min : 0 sec
21:29:17 CELL0: Downloading all files: Failed!
Please!! Any help will be acceptable!!!
Managed to solve ? I have the same problem . If so, can you explain to me how?
AgeuLevi16 said:
Managed to solve ? I have the same problem . If so, can you explain to me how?
Click to expand...
Click to collapse
No i didnt. I am still struggling to solve it.
nikose said:
No i didnt. I am still struggling to solve it.
Click to expand...
Click to collapse
Follow the tutorial that works. https://www.youtube.com/watch?v=oPB1izX4Plo
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
If you can not tell me, I managed to solve mine today like this.
AgeuLevi16 said:
Follow the tutorial that works. https://www.youtube.com/watch?v=oPB1izX4Plo
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
If you can not tell me, I managed to solve mine today like this.
Click to expand...
Click to collapse
No. It stays here...
{
"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"
}
What drivers did you put in your windows, and how your device seems in device manager when is in fastboot mode before you install thw new rom?? Do you remember?? I have unistalled all drivers from my windows. i installed only Qualcomm_USB_Driver_V1.0 and Coolpad-150819-Setup from russian site that had the rom. But the only thing i see in device manager is..... Other devices/unknown device
https://phoneusbdrivers.com/coolpad-cool-1-usb-driver/
My detected it as coolpad bootloader ... The rest I forgot. Install this drive with this tutorial,
i am trying to install those drivers as android adb interface. But windows says they are not compatible and didnt install them. Or you install them as android device instead of Android adb interface??
nikose said:
i am trying to install those drivers as android adb interface. But windows says they are not compatible and didnt install them. Or you install them as android device instead of Android adb interface??
Click to expand...
Click to collapse
Install the same on the video as on the link
Nah......... Nothing seems to work. Time for the recycle bin i thing. The only app that sees the phone in fastboot mode is the YGDP Tool. But it says new bootloader error and stops the flashing procedure.
nikose said:
Nah......... Nothing seems to work. Time for the recycle bin i thing. The only app that sees the phone in fastboot mode is the YGDP Tool. But it says new bootloader error and stops the flashing procedure.
Click to expand...
Click to collapse
It's complicated to help you, I use google translate, and it does not translate right and it gets complicated to understand.
nikose said:
Nah......... Nothing seems to work. Time for the recycle bin i thing. The only app that sees the phone in fastboot mode is the YGDP Tool. But it says new bootloader error and stops the flashing procedure.
Click to expand...
Click to collapse
Trying to downgrade your firmware, bootloader refuses to boot, in some new version you can´t downgrade by the usual way.
Try to install first only recovery and bootloader partitions, then if sucessful you can use fastboot again to flash boot, system and userdata cause maybe the other partitions are ready yet or also you will able to flash all the other partitions through YGDP.
How i can install only recovery and bootloader partitions?? With Qfil?? It generates an error and stop right away.
Case closed. Recycle bin gave the solution.
Sad
nikose said:
Case closed. Recycle bin gave the solution.
Click to expand...
Click to collapse
Same problem here. Same end.
=(
nikose said:
How i can install only recovery and bootloader partitions?? With Qfil?? It generates an error and stop right away.
Click to expand...
Click to collapse
Sorry unfortunately I never received any feedback maybe cause you didn´t quoted me till today with a new post from other member.
YGDP tool has a way to flash only the partitions selected by moving all the other files that you´ll want to flash and only leaving the needed files, you have to go to the directory where the tool unpack the rom before in order to flash it.
It´s possible that now the bootloader is messed so first of all in this case it´s needed flash only bootloader so it can allow to flash the other partitions.
Also there are other possible ways to recover device but it´s needed to know the exact situation that it is right now like which modes are working or not.
This is also for other members to try to find a solution, better you describe better to know the issue.
This is sad, my phone is exactly in same status right now
Hello guys,
I had the same issue, but resolved after 10 hours of tries lol.
Really difficult to know how i did it but you can try to flash a recovery from fastboot then you can have an access to the recovery.
It's possible to recover using Qfil .In my case i flashed twrp for eui , on top of jui rom, and got bricked.
Open qfil program.
Hold all 3 buttons down , vol up vol down and power , and connect to pc .
Qfil will detect Qualcomm Hs-Usb Diag port.
Keep holding down all 3 buttons , about 1 minute ,
phone switches to edl mode.
Then just reflash twrp or stock Jui recovery from Qfil.
This worked for me , i hope it works for you.
Related
If you connect your phone to the pc and see something like this
{
"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"
}
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Thanks for the tip ramm...
Dr. Ramm said:
If you connect your phone to the pc and see something like this
View attachment 3590142View attachment 3590143
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
View attachment 3590159
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Click to expand...
Click to collapse
Thanks man u are truly
Savior of mine MI4
Thanks a lot
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Nice share bro. Thanks
mad-extrem said:
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Click to expand...
Click to collapse
There is no difference between stock or extended partition, in flashing fastboot rom using MiFlash! It will recreate whole partition table!
Just follow steps in OP
Inviato dal mio D6633 utilizzando Tapatalk
mad-extrem said:
Tell me how to flash fastboot rom on extended partition.
Click to expand...
Click to collapse
U mean MM merged partition? IDK, which error show MiFlash?
If error: 0x80004005: FAILED (remote partition table doesn't exist).
then use this tutorial
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
It worked, thanks allot
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
vaski123 said:
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
Click to expand...
Click to collapse
What do you not understand?
You have to flash a fastboot rom, with MiFlash, that will re-build partition table
Inviato dal mio D6633 utilizzando Tapatalk
That will erase internal stoarge (sd card too). I lost everything on stored on it.. ?
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
marlo125 said:
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
Click to expand...
Click to collapse
Check post #7, if you read all (just less than 2 pages) you could find the solution by yourself.
Inviato dal mio D6633 utilizzando Tapatalk
Thank you for you sharing your knowledge I am very grateful I ran into this post and was able to repair my mi3. :good:
thanks sir, you saved ma life,thanks once again
You are my saviour
thanks for tutorial
a.broken.star said:
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
Click to expand...
Click to collapse
hey could you or anyone else help me with this...i bricked my phone and not able to boot into recovery and fastboot mode..its just completly dead...i am downloading miflash and fastboot room for my device[mi3]...plz help
Sir I Have followed your instructions because my problem is having having a Partition does not exist error in mi flash. i was already in the MiFlash step when suddenly the there was an error Access Denied and i keep receiving an error saying USB not recognized. Please help me any workaround Sir my mi3 no longer turns on and it no longer detected to a computer
Device: LG-D325
I tried rooting, unlocking bootloader, and installing custom rom (this link).
I successfully gained root & unlocked bootloader. Than it all went down.
I flashed recovery and booted into it, using "fastboot boot recovery.img" command.
I flashed cm12.1 and after that I got the "purple screen" error.
When phone is off and I try to normally turn it on:
1st screen:
Code:
Secure booting error!
Cause: boot certification verify
2nd screen:
Code:
DemiGod Crash Handler : DBI Err Fatal!
Board Rev.: 1.0
Ram dump mode.
Option : SD card ram dump mode.
Push below files to sd card before test.
rdcookie.txt, rtcookie.txt
Please do following action.
1) Ram dump Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
3) If sdcard ram dump enabled just wait for reboot.
4) Collect ramdump files from your pc or sdcard.
5) Send e-mail to [email protected]
The same happens when I plug in the USB cable when phone shut off.
Also, I cannot enter the fastboot menu (previously I could - before flashing CM12.1 via recovery) using volume UP + power buttons. Therefore, I cannot enter recovery.
Any info on this situation?
You need to short the test point of your phone and force the phone to qhsusb dload mode after that boot repair
it will repair your phone's download mode
And flash the phone
Br
Shahzaib Jahangir
Is there any way to fix this problem bro with out jtak
Thanks.
The test point method is not the JTAG method
razeen said:
Is there any way to fix this problem bro with out jtak
Thanks.
Click to expand...
Click to collapse
Use the test point method. It works very well and it's quite easy. But first I recommend you try "LG Flash Tool 2014" . If that works, no need to open up the phone for test point method. If you are already seeing pink screen demigod error DBI fatal error, no need to go for JTAG I think.
Feel free to ask if you need assistance for testpoint method. I have already published the method for few other people here on XDA. A little search will bring you there
my Lg325 also violet and dump mode cant flash i go to celpon repair but they cant fix my pon pls help me tnx
gilliane.08 said:
my Lg325 also violet and dump mode cant flash i go to celpon repair but they cant fix my pon pls help me tnx
Click to expand...
Click to collapse
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
honeybun.1986 said:
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
Click to expand...
Click to collapse
same problem here
can you help, please?
LG D325f L70
UPDATE
Now i have QDLoader 9008 (i've installed driver manually without signature). I don't know why my computer did not recognise automatically installed drivers
Else i trieb Board diag
I,ve tried QFIL QPST and recieved
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
Before that
BoardDiag 3.99c I have an error
AP CHECK START
FAILED during loading flash programmer
There were already messages about this trouble,but there are no solution, so i am asking for it.
LGE AndroidNet USB
qhsusb_bulk
Previously i had Pink screen and Lg Pc Suite could recognize my phone
I,ve tried Format to Fat32 my inner phone emmc(i did not insert in my phone microSD card) DiskImageRev2.zip and LoaderD325.img. After format to fat32 it was 4gb.When i,ve installed loader.img it became 64mb with 2 folders in it. Device monitor showed the phone as qhsusb_bulk (i already had istalled Qualcomm drivers) After installation of LGMobileDriver_WHQL_Ver_4.0.4.exe ( 12,39 МБ )
It was recognised as LGE AndroidNet USB. (com port 3) After that i tried LgFlash tool (tot and kdz firmware,it showed error on 50%) 2014 and BoardDiag also showed error .
I can not convert it to Qualcomm HS-USB QDLoader 9008 (I saw many articles where people with qhsusb_bulk converted it to Qualcomm 9006 after installation of qualcomm drivers,but it did not works for me. Please help
Any ideas? I heared about SRK tool 2.1 Does it works for my Lg L70 D325? Or maybe QPST, or ADP
honeybun.1986 said:
May be I can help you. But first you need a PC, a good internet connection and patience.. If you're interested, reply me.. I will guide you how to unbrick or come out from that pink screen/demi-god screen
Click to expand...
Click to collapse
Please help me
My lG D325 cant on recovery and download mode. Fatal error. Who can help me
Gayan360 said:
My lG D325 cant on recovery and download mode. Fatal error. Who can help me
Click to expand...
Click to collapse
I think you are referring to the famous "purple screen" mode. Relax, that is not hard to get pass.
Follow the steps below.
But, be warned, I am not responsible for any damage caused by following these methods.
Your phone's battery has to be charged at least 50%.
You'll need a USB "data" cable.The one came with your phone is the best. Some third party cables have only power lines connected in and they will not work. So, make sure you have the "data" cable.
1. First, we have to install the necessary drivers(I am assuming that you're using a Windows PC) .
Here are the drivers. Download, install and give your PC a restart.
2. Download LG flash tool 2014 from here and extract it to your root directory(For example, drive "C " in your PC )
3. Download the firmware file for your specific phone model. In your case, as you have mentioned, it is LG D325. This is a link to a matching firmware for LG L70 D325. This file is big and its around 920MB. After download, extract the zip file to the folder where you copied the LG Flash tool 2014.
4. I hope the above mentioned steps were followed correctly and you're ready now. Remove your battery, press the power button for 5-10 seconds and then re insert the battery. press the volume up button and plug the USB cable(The other end has to be plugged in first to PC. Refer to this video if you are unclear.
5. Now launch "LG Flash tool 2014.3.exe" (right click on it and select "run as administrator" for best results).
6. Once the program is open, and click on 1 and select your kdz file which you got from the step 3. Then click either "Normal Flash(2)" of "CSE Flash".
{
"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"
}
7. Now another window will appear and click "Start" as in this picture.
wait until the program finishes and once done, you'll get the initial setup screen on your phone with a greeting message.
If you're still unclear, please pass a comment. Happy communicating..
there are too many people have bricked their device. so here is the guide on how to debrick your device.
1. download the factory firmware ,uncompresss to your local disk. links : http://pan.baidu.com/s/1bC1tJw ; direct link from my server: https://tenfar.com/usr/uploads/nexus6p_fix_bricked.zip .use baidu disk .if you can. bandwidth limited.
2. download the EDL mode drivers ,and install to your pc. links: https://pan.baidu.com/s/1bpHPXE3
3. download miflash http://api.bbs.miui.com/url/MiFlash and install in your pc
4. run the miflash program and select the firmware ,plug in your phone to usb cable. in pc's device manager it will show the 9008 com port.
5.in miflash will show the com port,click flash,wait for it to finished
{
"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"
}
Edited:
How to enter EDL mode:
1 your device is bricked ,stuck in edl mode.try reset your device before flashing with miflash
2 flash a customize boot from cyanogemod or lineage.
Code:
adb reboot edl
3 unlocked phone with fastboot commands ,try this https://forum.xda-developers.com/ne...l-bootloader-extra-commands-nexus-6p-t3564086
4 unlocked phone using fastboot commands to erase sbl1
Code:
fastboot erase sbl1
not recommended
5 erase your sbl1 with dd commoand not recommended
Code:
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/sbl1 bs=16384
can you upload to androidfilehost links, not able to download from there.
also is that a normal firmware or special one?
Same here, first link is not working. Is it the standarg Google Factory Image or is it something different?
The Bootloader must be unloked?
I see the following under Device Manager when I connect my Nexus 6P to a Windows 10 Desktop via USB C:
Qualcomm HS-USB QDLoader 9008 (COM3)
I have installed the Mi Flash Tool as above along with USB drivers and Qualcomm drivers. I am not able to flash any factory firmware, however. I receive an error stating that the "hello packet" could not be received followed my an object reference error. I have tried many versions of the Mi Flash Tool to no avail.
Any other suggestions are much appreciated.
Thanks.
catalase said:
I see the following under Device Manager when I connect my Nexus 6P to a Windows 10 Desktop via USB C:
Qualcomm HS-USB QDLoader 9008 (COM3)
I have installed the Mi Flash Tool as above along with USB drivers and Qualcomm drivers. I am not able to flash any factory firmware, however. I receive an error stating that the "hello packet" could not be received followed my an object reference error. I have tried many versions of the Mi Flash Tool to no avail.
Any other suggestions are much appreciated.
Thanks.
Click to expand...
Click to collapse
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
@tenfar Can u update to the another host so we can easily download? That's will be great.
@tjchuot287 you can download "nexus6p_fix_bricked" firmware using "Advanced Download Manager" ADM on PlayStore using its built-in browser with "desktop mode" enabled...
Worked for me...
Hope that helps...
@5.1 I mean that i cannot download "USBdriver_8916.zip", but i think i will find it on google and download it instead. Hope it works.
@tjchuot287
I used advanced download manager and both downloaded fine... Since then far already shared the firmware from his server, It's likely he'll provide an alternative link for the driver as well... :good:
@5.1 does it unbricked your phone? Im kind of desperate
Well, I didn't use it... Since my phone is working. :angel:
I guess tenfar wouldn't have posted it if it didn't work. :good:
anyway, how to enter to EDL mode?
tenfar said:
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
Click to expand...
Click to collapse
I press the power key for 30 seconds with the USB C cable attached to the computer and the computer does emit a tone as if the phone has been disconnected and the device manager continues to show the Qualcomm HS-USB QDLoader 9008 (COM3). However, I still receive read packet error.
Do you have any other suggestions on how to get it into the correct EDL mode or the correct firehose state?
UPDATE:
[0.00 COM3]:[COM3]:start flash.
[0.00 COM3]:received hello packet
[0.00 COM3]:can not found programmer file.
Hello packet is recevied. However "can not found programmer file" is returned. Programmer file prog_emmc_firehose.mbn is in the extracted contents nexus6p_fix_bricked.zip, however the Mi Flash Tool does not recognize.
tjchuot287 said:
anyway, how to enter to EDL mode?
Click to expand...
Click to collapse
A few posts above yours...:
tenfar said:
power off your device with pressed the power key for 30 seconds. if the EDL mode is not in the right state .it will said send hello packet errors.
this firmware is flashed with qcom's firehose protocol. it needs the device in the right firehose state.
Click to expand...
Click to collapse
@5.1 thank you, I really appreciate your helps, but i think my phone is dead now. I didnt unlock bootloader before so now i cant do anything. Poor me
I'm having the same "cannot receive hello packet" error. I tried to old down the power until the device is re detected in device manager, but it still does the same.
catalase said:
I press the power key for 30 seconds with the USB C cable attached to the computer and the computer does emit a tone as if the phone has been disconnected and the device manager continues to show the Qualcomm HS-USB QDLoader 9008 (COM3). However, I still receive read packet error.
Do you have any other suggestions on how to get it into the correct EDL mode or the correct firehose state?
UPDATE:
[0.00 COM3]:[COM3]:start flash.
[0.00 COM3]:received hello packet
[0.00 COM3]:can not found programmer file.
Hello packet is recevied. However "can not found programmer file" is returned. Programmer file prog_emmc_firehose.mbn is in the extracted contents nexus6p_fix_bricked.zip, however the Mi Flash Tool does not recognize.
Click to expand...
Click to collapse
select the file in advance settings in miflash
从我的 iPhone 发送，使用 Tapatalk
tjchuot287 said:
@5.1 thank you, I really appreciate your helps, but i think my phone is dead now. I didnt unlock bootloader before so now i cant do anything. Poor me
Click to expand...
Click to collapse
I'm not sure this procedure require an unlocked bootloader. However @tenfar may certainly shed some light on this matter...
Hoping you get it sorted though...
Still getting "cannot receive hello packet" error. @tenfar a couple of questions:
- If the phone is detected in Device Manager as "Qualcomm HS-USB QDLoader 9008 (COMx)" do I still need to install the drivers from step 2?
- Do I need a particular combination of power, vol +/- in order to put the phone in the right EDL mode?
When I hold the power button for few seconds, the PC it is connected to makes the standard tone when a USB device is plugged/unplugged, but device manager still show the same device and Miflash still gives me the error when I flash.
Thanks for all the help BTW
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
Hello everyone, problem.
after unbrick procedure
I am with miui 10 android 8.1.0.011019
boot in twrp format data wipe , yes
error failed to mont '/data' ( invalid argument )
install Magisk-v15.3 last line
failed to mont '/data' ( invalid argument)
... done
install MagiskManager-v5.5.5.apk
i don't get root permissions .
where am i wrong? thank you
patrizi said:
Hello everyone, problem.
after unbrick procedure
Click to expand...
Click to collapse
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
A thousand thanks . in order to perform the procedure I had to try 4 versions of MiFlash, to find the complete one .
i went back to miui 9.6 android 8.1.0 English / Chinese language .
now everything should be fine.
Thanks again, good evening everyone
same exact problem
failed to mont '/data' ( invalid argument)
... done
possible ?
NOSS8 said:
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
Click to expand...
Click to collapse
Drive with fastboot, I'm working on it
do I find on the forum? thank you
patrizi said:
Drive with fastboot, I'm working on it
do I find on the forum? thank you
Click to expand...
Click to collapse
What's the problem now?
NOSS8 said:
What's the problem now?
Click to expand...
Click to collapse
Good morning .
turned on this morning I find:
android system
there's an internal problem with your device. contact your manufacturer for details, ok. with audio notification
pressed ok everything seems to be OK / working
current firmware: miui 9.6 stable 9.6.3.0 (ocbcnfd). android version 8.1.0. android security patch level 2018-05-05
installed with MiFlash20210226 where I selected clean all in automatic configuration.
writes with 70 - 100 seconds the green line does not fill completely, shows reboot alert with pc notification sound, the phone is in fastboot
does not reboot, has not completed writing, the count does not stop I have waited up to 780 seconds does not reboot, does not
complete writing, stopped at that point, I unplugged the cable and restarted manually. as before failed to mont '/ data' (invalid argument)
TWRP always cactus Italian, previously I have tried others without Italian does not format DATA.
still write problem for protection? that zone (date) has not been overwritten.
you can do a deep format (eliminate protection problems) with fastboot or how?
thank you
patrizi said:
Good morning .
turned on this morning I find:
android system
Click to expand...
Click to collapse
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
NOSS8 said:
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
Click to expand...
Click to collapse
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
fixed format error , I install Magisk-v15.3 reboot does not install app MagiskManager-v5.5.5.apk goes into error starts in recovery
I try to delete everything again without errors ,
reboot, delete everything again
install lineageos without errors restart ,
vibrates does not turn on, I also tried detach / attach battery it's bricked now,
procedure for recovery
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
searched for info by mistake
everything is correct, i made no mistakes, i have to try with latest version of flasch tool
I can not understand . thank you
patrizi said:
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
Click to expand...
Click to collapse
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
NOSS8 said:
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
Click to expand...
Click to collapse
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
patrizi said:
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
Click to expand...
Click to collapse
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
NOSS8 said:
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
Click to expand...
Click to collapse
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
patrizi said:
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
Click to expand...
Click to collapse
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
NOSS8 said:
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
Click to expand...
Click to collapse
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
error : status_sec_img_too_large (0xc0020005)
hint
Verified boot in enabled .
Please download signed image(cust-verified.img) or disable verified boot .
I can't find info to disable verification.
the file is safe and I tried like this:
disconnect phone, uncheck write files before the error
connect phone, write, answer: writing completed disconnect phone
invert selection of file writing boxes (check for no selection errors)
connect phone write
writing completed disconnect phone
turn on phone in fastboot mode
turns on and enters fastboot
SP_Flash_Tool does not connect to the phone (first attempt)
test connection with Mi Flash, here it is ok
select file to write,
ok start writing never ends.
fastboot always ok
I'll try again tomorrow.
i can't understand these writing problems
patrizi said:
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
Click to expand...
Click to collapse
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
I have edited, not complete writing, I insert log
thank you
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\Miflash\cactus11
if you manage to unlock it use this method post#11
NOSS8 said:
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\cactus11
if you manage to unlock it use this method post#11
Click to expand...
Click to collapse
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
patrizi said:
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
Click to expand...
Click to collapse
You have selected:
[12:37:55 bf4b07ea7d2a]:script :E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global\flash_all_lock.bat
result
[12:37:56 bf4b07ea7d2a]:err:FAILED (remote: not allowed in locked state)
You've made this mistake before.
Right path; E:\Miflash\cactus11
{
"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"
}