Related
Yesterday I had an update for the newest NIGHTLY Cyanogen ROM, which updated my ZUK Z1 to Cm 13 compatible to android 6.0.1
I had installed a NIGHTLY recovery and ROM on my own 3 months ago and everything was working fine. till yesterday after the update
Google Play was not compatible with my newest rom so i had to find a way to install 6.0 version of Gapps cause during the install i
kept getting a message that system partition had not enough space, which was not true.
I used ADB to re-install the latest NIGHTLY recovery and then BOOM... I got that message that bootimage was incomplete or not signed and my ZUK
bricked... It keeps loop booting and I'm not able to enter any recovery or boot in to bootloader.
Any help here would be greatful....
Thanks in advance Nick
TWRP installed on your Z1?
Monget said:
TWRP installed on your Z1?
Click to expand...
Click to collapse
Call me a noob, but I think I never istalled TWRP... Just the NIGHTLY recovery using ADB and then flashed NIGHTLY ROM via the recovery..
Now I can do nothing. I press power button, phone vibrates I see the ZUK logo, then bootloops forever..
Be optimistic your zuk is not dead.
A adb sideload with Cos 12.1 will be a good start. Download the last rom cos (Yogpas3 (of head) and go in recovery cyanogen, I think you did not flash TWRP
Monget said:
Be optimistic your zuk is not dead.
A adb sideload with Cos 12.1 will be a good start. Download the last rom cos (Yogpas3 (of head) and go in recovery cyanogen, I think you did not flash TWRP
Click to expand...
Click to collapse
I cannot enter recovery mode...
My zuk keeps boot looping forever. It just vibrates and I see the ZUK logo for less than a second. Then the same again
Nikosstamatiou said:
I cannot enter recovery mode...
My zuk keeps boot looping forever. It just vibrates and I see the ZUK logo for less than a second. Then the same again
Click to expand...
Click to collapse
i just managed to enter fastboot mode by pressing both volume + and - and then plugging the usb cable into my phone... Any ideas now?
Nikosstamatiou said:
i just managed to enter fastboot mode by pressing both volume + and - and then plugging the usb cable into my phone... Any ideas now?
Click to expand...
Click to collapse
Try to download this : http://loadbalancing.modaco.com/download.php?file=z1.recovery.testkeys.img
Put in a folder, and try an "fastboot i 0x2b4c boot z1.recovery.testkeys.img"
This requires of course that pilot is properly installed on the PC
Sorry for my bad english dude, i do my best (French)
Monget said:
Try to download this : http: // loadbalancing.modaco.com/download.php?file=z1.recovery.testkeys.img
Put in a folder, and try an "fastboot i 0x2b4c boot z1.recovery.testkeys.img"
This requires of course that pilot is properly installed on the PC
Sorry for my bad english dude, i do my best (French)
Click to expand...
Click to collapse
hehe it's ok friend I'm not english or american so we both cant speak very good english...!!!
well I've tried what you told me. I get the message that device is locked, I then try "fastboot -i 0x2b4c oem unlock"
but it won't let me unlock the device... what do I try next...??
Nikosstamatiou said:
hehe it's ok friend I'm not english or american so we both cant speak very good english...!!!
well I've tried what you told me. I get the message that device is locked, I then try "fastboot -i 0x2b4c oem unlock"
but it won't let me unlock the device... what do I try next...??
Click to expand...
Click to collapse
Hum enter "fastboot -i 0x2b4c oem unlock-go"
Any reaction after this command?
Monget said:
Hum enter "fastboot -i 0x2b4c oem unlock-go"
Any reaction after this command?
Click to expand...
Click to collapse
nope... still not letting me unlock. same with flashing unlock and flashing unlock_critical. Only that when I type these commands it seems to be doing something..
i get the "..." message like it is working on something..
SOLVED
problem finally solved, i guess..!!
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a cyanogen recovery and a cyanogen nighlty rom..
What does
fastboot oem device-info
say?
Perhaps it is unlocked, I didn't have a proper UNLOCKED message, but the status shows the Unlocked State.
Otherwise try the original Recoveries / OS from:
https://cyngn.com/support
sirmelkor said:
What does
fastboot oem device-info
say?
Perhaps it is unlocked, I didn't have a proper UNLOCKED message, but the status shows the Unlocked State.
Otherwise try the original Recoveries / OS from:
https://cyngn.com/support
Click to expand...
Click to collapse
I think I solved it..
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a TWRP recovery by breadcrust and a Cyannogen nighlty rom..
Nikosstamatiou said:
I think I solved it..
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a TWRP recovery by breadcrust and a Cyannogen nighlty rom..
Click to expand...
Click to collapse
I have the same problem ..
What the steps ..knowing that I'm not an expert ..
So I hope to simplify the steps in order to get ..
alhoaoy said:
I have the same problem ..
What the steps ..knowing that I'm not an expert ..
So I hope to simplify the steps in order to get ..
Click to expand...
Click to collapse
You'll have to find QPST which is a package of applications, including QFIL. Then you need to find the ZUI ROM and recovery, which will boot again your ZUK. I'll send ypu links ASAP. You can find them for yourself if ypu are in a hurry in xda site. don't worry you'll revive it!!
Nikosstamatiou said:
You'll have to find QPST which is a package of applications, including QFIL. Then you need to find the ZUI ROM and recovery, which will boot again your ZUK. I'll send ypu links ASAP. You can find them for yourself if ypu are in a hurry in xda site. don't worry you'll revive it!!
Click to expand...
Click to collapse
I have got QFIL and ZUI ROM
But when I'm press the buttons sound and Plug the charger does not appear in QFIL
alhoaoy said:
I have got QFIL and ZUI ROM
But when I'm press the buttons sound and Plug the charger does not appear in QFIL
Click to expand...
Click to collapse
try and follow these steps:
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try and follow these steps:
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
Thank you for helping me
Unfortunately it did not succeed to restore device
If you get this rom cm-12.1-YOG4PAS3OH-ham-signed factory With the existence of these files inside
prog_emmc_firehose_8974.mbn
xml file + the other patch
alhoaoy said:
Thank you for helping me
Unfortunately it did not succeed to restore device
If you get this rom cm-12.1-YOG4PAS3OH-ham-signed factory With the existence of these files inside
prog_emmc_firehose_8974.mbn
xml file + the other patch
Click to expand...
Click to collapse
Did you follow the steps as described?
Was your ZUK totally bricked or not?
Mine couldn't even boot into recovery. I had a constant bootloop lasting less than a second. But I saved it.
Do you want to tell me more?
Nikosstamatiou said:
Did you follow the steps as described?
Was your ZUK totally bricked or not?
Mine couldn't even boot into recovery. I had a constant bootloop lasting less than a second. But I saved it.
Do you want to tell me more?
Click to expand...
Click to collapse
The device was on the official rom YOG4PAS3OH
because of a network problem is not solved by format
I was setup Old official rom by the official recovery
then became when running show zuk sign and then resrart and stay that way
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
AmilDK said:
Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
Click to expand...
Click to collapse
Flash universal bootloader and the modem for A2017 from the lineage os thread. Then you should get radio signal again.
I don't know how to do It Can you give me more information please?
AmilDK said:
I don't know how to do It Can you give me more information please?
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Choose an username... said:
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Click to expand...
Click to collapse
Thx for the help, i do not have bootloader unlocked and not have TWRP.
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
AmilDK said:
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
Click to expand...
Click to collapse
What version did you install? 3.1.1-0?
Followed a guide and with minimal fastboot and adb tool put in the phone the 3.0.4-0-ailsa_ii.img successful After that can't go on with steps and if try to open recovery nothing happen
Install Stock ROM from EDL with MiFlash.
WesTD said:
Install Stock ROM from EDL with MiFlash.
Click to expand...
Click to collapse
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
AmilDK said:
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
Click to expand...
Click to collapse
Is your phone on edl mode?
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
AmilDK said:
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
Click to expand...
Click to collapse
Try 'adb reboot recovery' from cmd
I don't know where i miss, i tried with adb and axon 7 tool, adb edl reboot, axon7tool axon7tool -r gpt boot recovery*, then axon7tool -w recovery, with twrp-3.1.1-0-ailsa_ii.img renamed in recovery bin, but from here nothing happen, i can't go in recovery if i try nothing happen black screen if i put the old recovery.bin can reboot in recovery but can't flash modem file or unlock bootloader. Tried with miflash but nothing happen give me error "cannot receave the hello packet"
PS my buil now is ZTE A2017GV1.2.0B04, the original one was ZTE_A2017V1.0.0B15
Choose an username... said:
What version did you install? 3.1.1-0?
Click to expand...
Click to collapse
i found a post with exactly my situation
https://forum.xda-developers.com/axon-7/help/sim-airplane-offbut-turnd-t3698325
perchance have you the file you talk in this post https://forum.xda-developers.com/showpost.php?p=74386034&postcount=24
i don't know how, but i did it.. with axon7toolkit, restored original rom, then updated to V.2.0.0B13, now works good
Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???
Did you enable USB Debugging on your phone?
Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works
Thanks for all Tipps. Finally did it. Running RR Oreo!
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
Flash your stock recovery back! Twrp is not A11 compatible
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
Yes and next time you should better read the threads.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
OMG...how did this slipped through my mind. Damn thank you for this.
Kollachi said:
Yes and next time you should better read the threads.
Click to expand...
Click to collapse
I read many threads dear sir but this point totally slipped my mind about the android. Really appreciate the tip. Thank you.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Shubham1211 said:
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Click to expand...
Click to collapse
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
pyry666 said:
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
Click to expand...
Click to collapse
I just did this. So what I did was since there were fastboot stock roms available but not for android 11, I downloaded one...ran it through payload dumper and copied these files to overwrite the one from 10.5.13. But when I did that and everything went 100% as it should. My phone was not turning on now...no response on button presses and no sound when connected to computer...I thought did I really became the first one to hardbrick a oneplus....then I just checked in device manager and it was showing as 9008 at the end..which meant it is EDL mode...that was exactly what I wanted. I immediately started MSM Tool and there it was then I just started and now my phone is back to normal along woth having OOS 10.5.13 exactly what I wanted so thank you for pointing my foolish mistake.
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Danmanlott said:
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Click to expand...
Click to collapse
Bare in mind that EDL mode doesn't last very long (least it didn't for me)
So make sure you're ready to press start on MSM, once the process has initialized it'll keep it in that mode.
Found it out by trial and error. I too thought I couldn't get into EDL but it's probably the last thing that would fail on the phone, if fast boot is working then EDL almost certainly is too.