Related
Hey guyz,
I wanna use multirom and I'm getting stuck on flashing kernel in modified TWRP using sideload.
When i start it i can't find my device using command on cmd "adb devices"....it says "adb server didnt ACK" and failed to start daemon.
I'm running windows 8.1 and I installed htc sync for drivers.
If some1 know how to fix this problem i would be appriciate it,
ty
Are you booted into OS, or in bootloader? adb won't work in bootloader.
Do fastboot commands work? You need to be in bootloader-fastboot mode for that.
redpoint73 said:
Are you booted into OS, or in bootloader? adb won't work in bootloader.
Do fastboot commands work? You need to be in bootloader-fastboot mode for that.
Click to expand...
Click to collapse
yeah i know, i fixed it by deleting htc sync manager, anyway ty for your support
I want to root my swift.
I understand that first I need to unlock the bootloader.
downloaded the android studio in order to have adb and fastboot. ??
downloaded both supersu.zip & cm-13.0-20160316-SNAPSHOT
moved them both to sd card
I start the swift pressing power and volume button up i get the fastboot screen.
I connect to my mac.
nothing happens.
Ive seen an earlier post on xda explaining how to unlock the boot loader by inputing code from the computer to the swift but it looks like my mac does not recognize the phone[swift]
any ideas?
cheers
wisdomlight said:
I want to root my swift.
I understand that first I need to unlock the bootloader.
downloaded the android studio in order to have adb and fastboot. ??
downloaded both supersu.zip & cm-13.0-20160316-SNAPSHOT
moved them both to sd card
I start the swift pressing power and volume button up i get the fastboot screen.
I connect to my mac.
nothing happens.
Ive seen an earlier post on xda explaining how to unlock the boot loader by inputing code from the computer to the swift but it looks like my mac does not recognize the phone[swift]
any ideas?
cheers
Click to expand...
Click to collapse
Have you done the other steps as well? Enabling ADB debugging and OEM unlock from settings?
When you are in fastboot mode, what is the output from:
fastboot devices
thanks
Pak0St said:
Have you done the other steps as well? Enabling ADB debugging and OEM unlock from settings?
When you are in fastboot mode, what is the output from:
fastboot devices
Click to expand...
Click to collapse
Thanks for trying to help.
I somehow managed to cobble enough info form the web and by some miracle managed to root my device without bricking it.
I dont think i would be able to repeat the procedure.
cheers
2 points:
1. The 'Install ADB and fastboot on Windows with Minimal ADB and Fastboot' procedure does not allow specifying where adb & fastboot are installed. They actually install to c:/adb folder.
2. 'adb devices' does not show my Wileyfox Swift phone.
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
Hi,
I have OP3 with broken screen but it turns on (there is a LED blinking , and on my computer I see the OP3 CD installation & the device but I cannot access the data)
TWRP is the bootloader , how can I extract the data?
drivers are installed and tried some threads search on the furom but none of them worked for me
on fastboot devices it doesnt see it
Lellouche said:
Hi,
I have OP3 with broken screen but it turns on (there is a LED blinking , and on my computer I see the OP3 CD installation & the device but I cannot access the data)
TWRP is the bootloader , how can I extract the data?
drivers are installed and tried some threads search on the furom but none of them worked for me
on fastboot devices it doesnt see it
Click to expand...
Click to collapse
Insufficient info.
Are you able to boot up? Are you able to boot to bootloader? Do you have TWRP and are you able to boot to it?
Is your bootloader unlocked? Are you rooted? Is USB debugging enabled?
Does "adb devices" / "fastboot devices" command find your phone? What ROM?
tnsmani said:
Insufficient info.
Are you able to boot up? Are you able to boot to bootloader? Do you have TWRP and are you able to boot to it?
Is your bootloader unlocked? Are you rooted? Is USB debugging enabled?
Does "adb devices" / "fastboot devices" command find your phone? What ROM?
Click to expand...
Click to collapse
sorry ,
I think I am able to boot to the bootloader (but I cannot see it since my screen is broken)
my bootloader is unlocked , device is rooted and USB debugging is enabled
while pressing Power+Vol UP I can get into fast boot and see my device on fastboot devices
anything else I need?
To clear things up, TWRP is recovery and not bootloader. Fastboot is bootloader.
So, if you can boot into TWRP, you should be able to use adb commands. Try booting into it, then try "adb devices" and see if it's properly detected (adb reports device's serial number and status "recovery"). You can then use "adb pull" command to get your data.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
To clear things up, TWRP is recovery and not bootloader. Fastboot is bootloader.
So, if you can boot into TWRP, you should be able to use adb commands. Try booting into it, then try "adb devices" and see if it's properly detected (adb reports device's serial number and status "recovery"). You can then use "adb pull" command to get your data.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
my bad , since I dont have a screen , how can I boot into TWRP? is there are "blind commands" you can give me ?
Lellouche said:
my bad , since I dont have a screen , how can I boot into TWRP? is there are "blind commands" you can give me ?
Click to expand...
Click to collapse
Power + volume down should boot directly into recovery.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Power + volume down should boot directly into recovery.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Im pressing both for a long time , nothing happens (I guess , since I dont ear any sound and I dont see the device on adb)
Lellouche said:
Im pressing both for a long time , nothing happens (I guess , since I dont ear any sound and I dont see the device on adb)
Click to expand...
Click to collapse
Ok, an alternative then:
- download latest TWRP .img file to your PC
- open command window in folder with the file (Shift + right click > open command window here)
- boot into fastboot (Power + Vol Down) - you said you managed that before - and connect the device to PC. If it's properly detected in fastboot, you can boot custom recovery with "fastboot boot <recovery-name>.img"
Phone should now restart and boot into previously downloaded recovery. Now you can try and see if adb works.
Easier option would be simply "fastboot reboot recovery", but that command is non-standard and doesn't work on OP3 if I remember correctly. You can try though, nothing to lose.
Explorer23 said:
Ok, an alternative then:
- download latest TWRP .img file to your PC
- open command window in folder with the file (Shift + right click > open command window here)
- boot into fastboot (Power + Vol Down) - you said you managed that before - and connect the device to PC. If it's properly detected in fastboot, you can boot custom recovery with "fastboot boot <recovery-name>.img"
Phone should now restart and boot into previously downloaded recovery. Now you can try and see if adb works.
Easier option would be simply "fastboot reboot recovery", but that command is non-standard and doesn't work on OP3 if I remember correctly. You can try though, nothing to lose.
Click to expand...
Click to collapse
That worked for me , Thanks!!