I am trying to unlock the bootloader using ADB and Fastboot, but when I use the command "adb reboot bootloader" the PC suddenly starts recognizing the phone(now in download mode) as a modem, and thus I am not able to update the drivers for Fastboot.
Samsung phones DOES NOT have fastboot, they have a single download mode that can be managed by either Odin or Heimdall.
To unlock the bootloader, simply do it through developer options, set clear that you'll lose all your data in the process.
The problem is that my bootloader can't be unlocked by enabling that one option "Allow OEM unlock", it simply does basically nothing but make some apps stop working. Fastboot doesn't work for reason I mentioned earlier. Is there something I'm missing?
Mohamedkam000 said:
Samsung phones DOES NOT have fastboot, they have a single download mode that can be managed by either Odin or Heimdall.
To unlock the bootloader, simply do it through developer options, set clear that you'll lose all your data in the process.
Click to expand...
Click to collapse
I tried Odin to flash TWRP but it doesn't work. The process fails everytime, for reasons I don't know. I had allowed the phone to be OEM unlocked and I had USB debugging turned on.
WitheRosE said:
I tried Odin to flash TWRP but it doesn't work. The process fails everytime, for reasons I don't know. I had allowed the phone to be OEM unlocked and I had USB debugging turned on.
Click to expand...
Click to collapse
Can you send the Odin log?
Did you install Samsung USB Drivers on your PC? and what recovery version are you trying to flash?
Related
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
ckpv5 said:
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Thank you for reply!
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now. It does not appear under the devices list. If I can just get adb talking with my phone everything else should be easy, I just can't figure out why it's not recognizing it.
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
Click to expand...
Click to collapse
Gitnerd said:
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now.
Click to expand...
Click to collapse
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
Gitnerd said:
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!!
Click to expand...
Click to collapse
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
ckpv5 said:
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Oh.. My..God..
You just saved my life, this whole time I thought fastboot utility in AndroidSDK was just a stripped version of ADB. I'm a moron!
I have TWRP up and running holy crap thank you so so so so much, you are seriously a life saver.
try this
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears again (Should be around 10 seconds), press the volume down key.... Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
4) Once you are in the bootlader, select select fastboot by pressing power key.
5)you can flash either permanent or temporary a TWRP recovery once you are in fastboot.
6)Once you are in recovery mode, you can transfer any custom rom to memory or sd card, then install it from the place you chose.
7) you can flash RUU file at fatboot mode as well.
So I was running a custom ROM for a while and decided to switch back to the stock ROM. After doing that, I flashed the stock recovery so that I could install the OTA update from version 4.28.502.2 to version 6.20.502.5. During installation, the phone got stuck in a bootloop, so I wiped the cache and tried to start it again. After that didn't work, I factory reset it (in the bootloader, and then in recovery after it didn't work), and it still doesn't work. ADB and fastboot doesn't detect my device even though I had USB debugging on before I tried to update it (I'm guessing that the factory reset disabled that?). I can access the bootloader and recovery, and my phone has an unlocked bootloader with S-On. I have the AT&T HTC One M8 if that helps. Can someone help me please?
Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day
BelDev said:
Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day
Click to expand...
Click to collapse
I'm saying that my computer doesn't recognize my phone, and that's why I can't flash a custom recovery like TWRP
Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?
BelDev said:
Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?
Click to expand...
Click to collapse
Yes, I have the right drivers installed. Yes, I have tried a different USB port. Yes, my battery is fully charged.
Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.
BelDev said:
Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.
Click to expand...
Click to collapse
The drivers fail to install everytime, and I've tried on three different PCs
Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?
BelDev said:
Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?
Click to expand...
Click to collapse
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected
Jhaleefi said:
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected
Click to expand...
Click to collapse
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks
Jhaleefi said:
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks
Click to expand...
Click to collapse
Seems like your main issue was not properly using fastboot mode for fastboot, and realizing that adb doesn't work in bootloader mode? That, and having the proper firmware and RUU files.
I can get my Zenfone 2 up to the fastboot screen, but no further.
Under PC device manager is shows "Android-Phone" as the device, but no drivers loaded.
I've tried a few different drivers, but even though they seem to install OK, "Android-Phone" (in device manager) still won't show as having a driver.
Some threads say I have to enable Android Debugging, but how to do that when the ONLY screen I can get on the phone is fastboot??
Help???
Boowho??
You can try this.
1. Uninstall all drivers for phone you installed on PC, then reboot.
2. Disable antivirus on PC then install standard Intel android device usb drivers. You can download them from Asus website. Then reboot again.
3. Connect phone to PC in fastboot mode.
4. In the device manager you should see "Asus android device" under which "Asus android bootloader interface".
5. Check connectivity in minimal adb & fastboot software (you can get it from XDA) by command "fastboot devices" without quotes. It should answer "some number<space>fastboot".
If all is ok then you can flash raw stock firmware in fastboot mode & update it to latest version OR unlock bootloader, flash TWRP & install custom rom.
Thank you Sanesh. I got all the img/bin files successful now. However, the ZF2 has this issue when you select recovery from bootloader screen it gives dead android. You can then (extra step) hold power and VOl + and get into stock recovery. This is a flaw in the original firmware, I think.
BUT, this extra step is causing TWRP not to be entered. Stock recovery is OK, but not TWRP.
I had to recover the phone using the SOC drivers; before that TWRP worked perfectly.
Thanks
Have you unlocked bootloader ? Unlock bootloader first then flash twrp using giovix92 method. Then reboot to recovery.
Thanks. Turned out I was using a twrp image that is only for marshmallow. I still use lollipop. Every thing is now back to where it was before I had to recover the thing using the SOC method.
Lesson learned. un-root before trying to upgrade to MM.
Hi,
I used the XiaoMiTool to flash my Mi Mix 2 from Chinese ROM to global. Around 90% of the flash process, the progress bar on the phone did not changed for 2 hours (!!!). I rebooted the phone and now it is with Mi logo as you can see from the img https://imgur.com/a/O9BZ8
I can enter fastboot and recovery mode, but now my computer does not recognize the device anymore (so I can re-flash it) - I get "unknown USB device" in the device manager. I installed Qualcomm driver, but still the same.
Please help!
please notice that I'm not too technical, therefore would appreciate detailed answers if possible.
Thanks ahead!
try the different computer and different USB TYPE-C cable to check if it helps. as long as you can enter fastboot /recovery mode.
I uninstalled the USB driver, reboot and now the computer recognizes the device, but I have a new problem:
https://imgur.com/a/IetkC
From the command line i got this:
https://imgur.com/a/65Dtn
How to proceed?
moralshixch said:
I uninstalled the USB driver, reboot and now the computer recognizes the device, but I have a new problem:
https://imgur.com/a/IetkC
From the command line i got this:
https://imgur.com/a/65Dtn
How to proceed?
Click to expand...
Click to collapse
Judging from the first picture, the bootloader isn't unlocked. "Erase boot failed" results most likely from a locked bootloader. Go unlock your bootloader, if you haven't done so already. The MiFlash stuff should work after that. Also, with an unlocked bootloader you might as well flash TWRP, boot into it and format data, and use its MTP capability to transfer a custom ROM onto the device and then flash it. Hope that this can help, good luck :good:
GrenadeofTacos said:
Judging from the first picture, the bootloader isn't unlocked. "Erase boot failed" results most likely from a locked bootloader. Go unlock your bootloader, if you haven't done so already. The MiFlash stuff should work after that. Also, with an unlocked bootloader you might as well flash TWRP, boot into it and format data, and use its MTP capability to transfer a custom ROM onto the device and then flash it. Hope that this can help, good luck :good:
Click to expand...
Click to collapse
Miflash will work with locked bootloader no problem.
2nd image shows its the wrong image...