Hi, i was playing with my yota2 and think i messed up the radio files, now the phone is dead, no vibration no screen light, nothing.
i tried some methods and was able to get the phone recognized as 'Qualcomm HS-USB QDLoader 9008' but dont know what to do. btw i opened up the phone, is there anyway to revive it or should i just order another one?
Thanks alot
Try flashing it with yotaflasher. Post any errors if they occur.
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
yotafree said:
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
Click to expand...
Click to collapse
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
i had a hardbrick yotaphone2 also. only qualcomm 9008 detected. had tried all the way to flash it back due to wrong rom being flashed. please advice....no fastboot, tried power off and volume down, tried kick out from EDL mode...tried qualcomm flasher which support EDL flashing but downloaded rom cannot flash due to only img and bin file, there is no rawprogram xml file.....anybody have dumped rom for this phone?
Thank you but did you forget to add the link which command to run ??
Parmo100 said:
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
Click to expand...
Click to collapse
Thank you but did you forget to add the link which command to run ??
Related
Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s
faraway001 said:
Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s
Click to expand...
Click to collapse
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.
smit.sanghavi said:
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.
Click to expand...
Click to collapse
Hey I am back...
As for your reply ,thanks but what I wanna say is the first,my PC has purely good configured and not any system deformity.
And I haven't found any working adb.exe/fastboot.exe version before I one day surfed a board and droped with a working bundle.
The bunldle included adb and fastboot which had the different md5 from the ones in "15 seconds ADB Installer".
*15 sec
81d188a849c8768e8f3694eb1c0e6086 adb.exe 800k
2782d10e7d3370cfefbadae0e8eaaa35 fastboot.exe 157K
**working version
8ae827f316e4fd4500c8d5b2845bcbe9 adb.exe 2400k
6bbf05d97585c3c515bdb172eb9e7d12 fastboot.exe 969 K
What's the difference between the "15 sec" and the working version. Weren't they coming from the same Google adt-bundle？
Or has somebody compiled the origin fastboot.exe and twisted it in order to make it work straight out there.
hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Mohamed elkholy said:
hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Click to expand...
Click to collapse
It's probably a problem with drivers. It's common in Windows. Search in the forum for these keywords: ADB Windows driver problems
I resolved using a Linux distro (Debian Sid, but Ubuntu is OK and more friendly too), no problems with drivers anymore.
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
mohamedelkholy said:
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
Click to expand...
Click to collapse
Do you run the command prompt as Administrator (right clic on the Command Prompt icon > Run as Administrator)?
Do you run fastboot devices before to check if the phone is recognized by fastboot?
i have run the cmd as an admiristratore but how to reconized it
mohamedelkholy said:
i have run the cmd as an admiristratore but how to reconized it
Click to expand...
Click to collapse
with the command:
Code:
fastboot devices
if the phone is recognized, it should respond with
Code:
random123 fastboot
if nothing happens, you have to check your adb drivers (uninstall and reinstall for example).
Hi guys I tried to root my LeTV 1 Pro but it didn't worked.
My phone keeps rebooting in fastboot ( I see the penguin 10-15sec and it reboot again and again) or it stays alight with the penguin.
Computer doesn't recognize it.
Thanks.
Try and plug it to your computer then keep power and wol down pressed for like 15 sec: now fastboot should stick and device shouldn't reboot, so you can flash a recovery (TWRP?) and start over with a new ROM.
Thank you for your reply,
It still doesn't work, penguin stays on screen but it's not recognized by computer ( before the brick it was)
I'm not very experienced in rooting btw.
Edit : The recovery.bat in the file X1_X800_TWRP_Recovery2.8.7.0 says "Complete! The device is ready to reboot into Recovery." which I do but it keeps reboot with the pinguin on.
I recieved my phone today and it just wont stay in fastboot mode. I can do anything I want but it just keeps rebooting before I can flash anything. Any suggestions on how I should keep the Phone in Fastboot mode?
You need to install drivers. After that it will not reboot anymore. That worked for me atleast.
What kind of drivers do I need? Please link them to me I have tried a lot of drivers. The thing is that the phone also does not stay in Fastboot mode when not plugged into the PC.
It's my topic for my problem so don't ask questions for you on it please u_u
zamul said:
It's my topic for my problem so don't ask questions for you on it please u_u
Click to expand...
Click to collapse
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
DatNoob said:
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
Click to expand...
Click to collapse
Zamul don't be mean. He just asked for help as you did...
I have downloaded drivers (I think) from https://twrp.me/devices/letvle1pro.html where I also get twrp 3.0.2.0
Btw if you are using Windows you can open Device Manager and there you will see your device and what drivers it has installed (you can always use update drivers function, maybe that will help too).
Here is a little guide how I managed to get twrp:
Just download it (drivers and intall them) (and download twrp also). Place twrp file to the folder where you have your adb installed.
In phone settings go to developer menu (first you need to unlock it) and you need to switch on usb debugging.
Connect phone to the pc via usb.
Open command prompt in your adb folder and type Adb devices (if you have drivers installed corectly you will se your devices connected under some code).
Then just write Adb reboot booloader and phone will restart to the recovery.
Type into the comand prompt: fastboot flash recovery name***.img (where the name is the file name of twrp you have downloaded- just a tip: rename it so it is easier to remember for example to twrp. Then the command will look like: fastboot flash recovery twrp.img)
If succesful, write fastboot reboot and that is all.
Btw for me it did not work first time. I had to load twrp for second time and when I wrote fastboot reboot then I immediately pressed volume up so It went directly to twrp recovery.
Hope it helps. Cheers
I have this problem
Hello
I have your problem have you solve this?
Thanks
Hi guys. I have a problem! My letv x800 CN boots to TWRP but doesn't start the system (EUI logo loading all the time) I don't know how to transfer ROM into the phone in order to flash it. I installed all the drivers and PC recognize it. PLEASE HELP!!!
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 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!