Database Users

[Q] ADB sideload & fastboot not working

Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.

Anything?

oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.

taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.

Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?

audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.

oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.

audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.

oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?

audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin

No clue?

Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk

Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app

karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface

No clue?

Unable to Flash Custom Recovery

Hi guys,
Im on the cm12s, and unlocked bootloader but im unable to get into custom recovery, it keeps reverting to Cynogen recovery.
I tried toolkit also, it flashes and then it shows waiting for device, i manually boot into recovery its just a blank screen.
Please help i need root and ROMS

varun.gid said:
Hi guys,
Im on the cm12s, and unlocked bootloader but im unable to get into custom recovery, it keeps reverting to Cynogen recovery.
I tried toolkit also, it flashes and then it shows waiting for device, i manually boot into recovery its just a blank screen.
Please help i need root and ROMS
Click to expand...
Click to collapse
how did you unlock bootloader ?
may be using adb drivers right ?
so if you are using adb drivers then follow this procedure ....
copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:

ashish_zarekar said:
how did you unlock bootloader ?
may be using adb drivers right ?
so if you are using adb drivers then follow this procedure ....
copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:
Click to expand...
Click to collapse
I tried this method.. but it always reverts to stock recovery. and when i boot into recovery directly from fastboot i get a blank screen. Please help.

varun.gid said:
I tried this method.. but it always reverts to stock recovery. and when i boot into recovery directly from fastboot i get a blank screen. Please help.
Click to expand...
Click to collapse
have you tried with this recovery which i provided in link ?
first try using this recovery.
earlier i also face this.
now go to this thread download software from this thread only. there are two thread for this tool but i prefer you to go to this one.
GUIDE
now unlock bootloader.
and go for step 4(which flash twrp recovery)
now flash the recovery which is provided by me using code.
and now go can go into recovery
****************************************************************************************************
i suggest you this guide this method do for me

Disable update CM recovery option in developer options... Then flash custom recovery.... it will work.

once flashing twrp recovery, you will need to use
Code:
fastboot -i 0x1ebf reboot
command.

remove battery after install recovery before restarting phone
then insert battery and start in custom recovery

install Custom Recovery
1) enable developer options
2)enable advance reboot and usb debugging
3)disable Update CM recovery option
4)reboot to bootloader and flash recovery
" fastboot -i 0x1ebf flash recovery recovery_twrpyulolli.img "
5) directly disconnect phone (phone displaying FASTBOOT MODE)
6) remove battery and start phone in recovery mode using volume UP+DOWN and power key
7) And YOUR are IN TWRP RECOVERY ......
THIS method work for me perfectly .....i m also having same problem of flashing custom recovery and again showing CM RECOVERY
:laugh::laugh:
Thank You...!

Which is best for yureka cwm or twrp recovery

I'm facing the same problem but this trick didn't work for me.

Some Help With TWRP and Bootloader Please

Hey guys. I've tried everything, and I'm stuck. Never had so much trouble doing something so basic. No idea where it's going wrong.
Here's the basic timeline:
1. Bought phone
2. Unlocked/rooted/flashed TWRP
3. Tried CM13 for a bit, clean flash +supersu
4. Tried Exodus for a bit, clean flash + supersu
5. Tried community build of 3.0.1, clean flash +supersu
6. Wanted OTA update, so dirty flashed community build to remote root, OTA update ended up replacing TWRP with stock recovery
7. I want to go back to exodus, and can't for the life of me get TWRP back on
Here's what I've tried:
1. Basic steps on any website to download adb drivers etc.
2. Tool box from XDA
3. Factory reset then try all of the above again
Issues:
When I try to fastboot flash recovery [file] I get error: cannot load 'recovery.img' I've tried renaming it to twrp.img as I've seen suggested in some places, no help. I've ensured that the image file is in the same folder as the command prompt. I have used the Grarak TWRP file as well as 3.0.2 and 2.8.7 as suggested on some other sites.
Things I'm noticing:
When I try the fastboot devices command, it only recognizes my device when in fastboot mode, but not when loaded normally. In fastboot mode I can issue commands to reboot, get info, etc. but once loaded it's all gone.
I haven't seen that prompt that comes up to authorize a computer RSA code for USB debugging (yes, USB debugging is enabled in developer options, and yes, I have tried changing the USB settings from charging, to MTP, PTP, even MIDI.)
When I use the device-info prompt I get the following results:
Device Tampered: false
Device Unlocked: true
Device is_verified: false
Charge screen enabled: false
Display panel:
console_locked: 1
exec_console_unconsole: 0
Any and all suggestions would be greatly appreciated!

Hi, Here's what i believe you need to do. If you have the correct twrp recovery img file and all you need is to just flash it to get custom recovery in order to continue enjoying your custom roms, then this will fix your problem.
1. make sure you have all the necessary adb, fastboot drivers installed and that if you run the command 'fastboot devices' fastboot can see your Oneplus device.
2. if fastboot can see your oneplus device, then worry not. use the following command to flash your custom twrp recovery.
3. Rename your recovery file to just recovery nothing else attached.
4. boot your phone into fastboot, open the folder where you have your recovery file and hold down the shift key and rightclick anywhere in the folder and select the option that says 'Open command Window Here'
5. this will load fastboot. after fast boot loads, enter the following commands :
fastboot devices (this will display your device, once your device is showing, then worry not)
6. the next command is to flash your custom recovery image. so u need to enter exactly the following :
fastboot flash recovery recovery.img (this will then flash your custom recovery. make sure you name it just recovery)
7. after flashing your recovery, enter : fastboot boot recovery.img (this will boot you into twrp recovery mode)
let me know if this helps. Cheers!!

Try to flash Hybrid recovery using fastboot. --> http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904

Oneplus 6T hard brick?

Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?

Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/

FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.

ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it

Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode

FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.

When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.

[ROOT] I can boot in fastboot, but it says "waiting for device". I installed a lot of drivers, what to do?

I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?

cocclina said:
I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?
Click to expand...
Click to collapse
Hi There.
change you rcovery image file name to "twrp.img" and move them to c:/ partition.
then enter the command bellow : fastboot flash recovery c:/twrp.img
NOTICE : Of course, I installed twrp custom recovery on my huawei p8 gra-ul00 phone and im very regretted.
And you're doing this at your own risk.
Regards,