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".
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
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.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Did you unlock boot loader? After that press volume up and power button,then you can enter fastboot screen. After that use fastboot flash recovery twrp.img
I have same problem plz help
1. boot into fastboot.
2. make sure fastboot can see the device 'fastboot devices'
3. fastboot flash recovery twrp-xxx.img
4. boot into twrp.
Did that work?
chr0 said:
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Click to expand...
Click to collapse
Did you find any solution to this problem?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Yes. Use Powershell instead of the normal cmd
chr0 said:
Yes. Use Powershell instead of the normal cmd
Click to expand...
Click to collapse
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Utsav_vats said:
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Click to expand...
Click to collapse
Nope. Just used Powershell to execute the bat file and then push TWRP.
CMD wasn't working for me.
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.
Try flashint stock on EDL mode.
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.