Related
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
brosenz said:
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
Click to expand...
Click to collapse
I know nothing about using Macs but have you installed the device drivers? As you are getting no serial number returned when using fastboot devices im guessing not.
Mark.
On a side note please do not post questions in the Development Forums as that is not the place for them.
Thanks.
The device is being detected while running in normal mode, meaning I do have the drivers, the problem is when I go into FASTBOOT MODE, I can no longer see the phone
Craiq said:
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
Click to expand...
Click to collapse
But for the simple command ./fastboot-mac devices should work and it's not
in bootloader mode u need other drivers
but dont know how to install them on mac
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
dhemke17 said:
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
Click to expand...
Click to collapse
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
brosenz said:
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
Click to expand...
Click to collapse
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
dhemke17 said:
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
Click to expand...
Click to collapse
I've done that, going into FASTBOOT MODE manually and the same result. Yes I am rooted.
I just want to go back to stock and re-lock the phone, is there other way to accomplish that ?
NOTE: I've tried Mac and PC (Galaxy Nexus Root Toolkit 1.3), different USB cables, different USB ports, reinstalled all the drivers on the Windows computer, NOTHING, the phone it's not being detected in FASTBOOT MODE.
Is it possible to go back to stock and re-lock from the Recovery Mode ?, I have ClockWorkMode 5.5.0.2 installed and working fine.
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
mskip said:
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
Click to expand...
Click to collapse
I used FASTBOOT to unlock and Root, no problem at all, use the phone for 10 days and them decided to go back to Stock and Re-Lock. If I connect the phone in normal operating mode to the computer it will be recognized and I can see the phone from the computer connected via USB, so the cabe, port on the phone and port on the computer are OK. I've tried different computer (Mac and PC), different OS (Mac OS X and Windows 7), different USB cable, different USB port.
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
dhemke17 said:
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
Click to expand...
Click to collapse
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
brosenz said:
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
Click to expand...
Click to collapse
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol -... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
dhemke17 said:
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol +... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
Click to expand...
Click to collapse
I do not know why but Vol + does not work in my phone
brosenz said:
I do not know why but Vol + does not work in my phone
Click to expand...
Click to collapse
My bad lol...down...volume down
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just used your video to unroot my galaxy nexus 4.0.4 thanks a lot!
hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.
Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app
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!!
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'