Hi, i can't get my PC to detect my phone under Fastboot with ADB so i can't do anything through there but i wan't to update my ZCX Recovery. In the installation notes it says "You can flash by either Fastboot method or TWRP methods "but what "TWRP methods" means and how to flash it?
TWRP method mean is if your phone already has TWRP recovery before and wanna change or update it..you can flash new TWRP via your current TWRP.
But anyway.. why your phone while in fastboot mode can't detected by pc.and what command you're typing to check in fastboot mode??, i mean are you sure you're already installing all driver that adb and fastboot needed..?, and are you sure you're already typing correct adb and fastboot command..?
Because recently i see someone thread that asking the same problem like this too (more or less) in en.miui.com forum too..he/she is wrong typing command while he/she's phone in fastboot mode, he/she's typing adb command while the phone is already in fastboot mode, of course adb can't recognize it.
I don't know this is you too or another person.
Related
For some reason my phone will not boot into recovery. I have tried booting into recovery from the system and via adb. Takes me straight to bootloader. Strange thing is when in bootloader/fastboot mode my computer will not recognize my device in adb when connected, but when I am booted into the system the phone is recognized in adb. I think I have to reflash my recovery (twrp v2.6.3) but originally I flashed it with goo manager, which seems to be down atm. My question is how do I get my device recognized while in bootloader/fastboot again so I can manually flash twrp, and what were the commands to properly flash the recovery via bootloader/fastboot. I did do a search but did not find specific results that answer my questions. I know I've read about this happening but I cannot remember where. Tia.
Edit: FIXED!!!Needed fastboot in same directory where adb exe was located. Commands were able to be run to flash recovery from fastboot.
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.
AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck
Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
arachniac1 said:
Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Just kill adb.exe with Taskmanager... And try again..
arachniac1 said:
Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Something is not quite right. adb and fastboot have different requirements, and will never work at the same time.
adb = works in OS or TWRP, will not work in fastboot mode. Debugging must also be enabled
fastboot = only works in fastboot mode. Debugging enabled not needed.
So adb working, and fastboot not working is expected, but to me, means you are not in fastboot mode. Or your are changing modes/states between commands (which is really confusing).
Go into fastboot mode and type: fastboot devices
And see if it returns the phone ID.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!