Hey guys I have given up. Been looking at this for two days now and it will not work. Heres the problem.
I have ran X-factor unlock as per instructions and it ran successfully all the way to the point where it asked did I want to see the identifier token. I hit yes and then the it froze. Let it sit there for like 5 minutes and nothing. So I closed X-factor and open cmd and booted the phone into fastboot. Then I plugged my phone into my computer and ran the fastboot command "fastboot oem get_identifier_token" and I does nothing. I also tried running "fastboot devices" and still notthing. I have reinstalled htc sync manager, pdanet for the drivers, have tried all different version of fastboot and adb and nothing is working. What could I possibly be doing wrong? Pdanet recognizes that the phone is plugged into the pc and the phone recognizes it too but fastboot doesn't. Any help is appreciated.
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
abhipati said:
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
ImagioX1 said:
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
Click to expand...
Click to collapse
Did you install HTC sync
First things first, do you get anything when you do adb devices?
APSBiker said:
First things first, do you get anything when you do adb devices?
Click to expand...
Click to collapse
Yaa, when u plug in your device type "adb devices" in command prompt (from android platform tools folder) did u get any response "[serialNumber] [state]"??
Sent from my HTC One XL using xda premium
abhipati said:
Did you install HTC sync
Click to expand...
Click to collapse
I said in my firt post that I did.
I have tried adb devices and for some reason it works some times and other times I get nothing. I suppose X-Factor is using adb though and the adb part( the two backups and the reboot into fastboot) of X-Factors works all the time. Its only when the phone reboots into fastboot that the rest of the commands don't work with X-factor. Only once did it work and it said it was successfull- i go the 111111111 for my CID. But when I hit enter to view the token X-Factor did nothing.
I have another idea that might work. I was wonder what you guys thought. I have vmware running Mac Os and I was wondering if I could download the Mac tools to my vm and try running the commands that way. Since Mac doesn't doesn't need drivers do you think that would work?
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
ImagioX1 said:
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
Click to expand...
Click to collapse
Awesome! Thanks for updating us on how you got it to work. I guess I was one of the lucky ones that it worked the first time for.
That was a tough fix. Windows still will not recognize my device in adb or fastboot. I don't know what the problem is. But the only catch to running Mac Os in vmware is it is against the EULA so I am not telling you to try that. But It will work. I have been looking at this for 2 days now and I had to go install Mac Os in vmware and register with apple and all that good stuff before I could even start running commands. It was tough but I hope its worth it.
USB debugging
I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
You're in the wrong forum, this is the One XL forum. You need to ask in the Desire forum.
Sent from my Evita
Related
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
haltemien said:
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
I'm on skype ATM, so if anyone is gentle enough to try an errorsearch with me, call me on my username snorre.andre.nergaard
Click to expand...
Click to collapse
When I reinstalled my SDK i hadnt noticed that ./adb had been moved to a different directory, and the SDK no longer comes with ./fastboot. If you do a quick google search, or a search on XDA, there are forums out there with links and uploaded copies. Actually I'll just put mine up here in a .zip archive. I moved ./adb and ./fastboot back in to my tools folder since it's what I'm used to.
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
haltemien said:
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
Click to expand...
Click to collapse
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
krohnjw said:
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
Click to expand...
Click to collapse
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's fastboot oem unlock
Sent from my Nexus S using xda premium
krohnjw said:
It's fastboot oem unlock
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It doesn't use ADB at all. That may be what you have your local binary named, but it's fastboot. You need to be in the bootloader (where adb cannot work).
Fastboot is the utility used for unlocking the bootloader, flashing/erasing partitions, booting images (such as a kernel or recovery) without installing to the device.
ADB is the Android Debug Bridge.
This is just for clarity here, there's seemingly a lot of confusion.
Thanks for the clarification bud
Sent from my Nexus S 4G using xda premium
kdepro said:
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
Click to expand...
Click to collapse
Yeah. I was in bootloader mode. So then i guess the fastboot "path". that could be the problem then. Ill check it out when i get back from work. Thanks
I posted this before but it was dead so I'm reposting, sorry. I was in the process of rooting my brothers phone, I turned S-off and flashed updated firmware, however I forgot to flash a recovery. Now the phone is in a bootloop. I tried downloading 4ext recovery file PG58IMG to flash in bootloader. I added his cid number to the file but when I run bootloader it doesn't give me the option to install the file. The other method I was told to try involves using CMD to do it with the flashing tool. But since I can't start the phone, cmd doesn't recognize the device. Can somebody please help me? How can I install recovery on this device?
You could always go into fastboot manually and use the cmd prompt. Fastboot flash recovery **********.IMG I'm almost sure that's the proper command.
Sent from my HTC Sensation 4G using xda app-developers app
Sloopjoshb said:
You could always go into fastboot manually and use the cmd prompt. Fastboot flash recovery **********.IMG I'm almost sure that's the proper command.
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
smockpuv said:
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
Click to expand...
Click to collapse
Hi,
You need to have THESE DRIVERS on your PC.
ADB is explained HERE
Installing recovery is HERE
Took the words right out of my mouth.
Sent from my HTC Sensation 4G using xda app-developers app
smockpuv said:
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
Click to expand...
Click to collapse
this means you havent connected the phone properly to pc
the phone should show "fastboot usb" if connected to pc properly ..if it shows hboot and there is an option fastboot in the list . browse to fastboot using volume download ..then select fastboot using power ...then connect the device to pc ( at the end phone should show fastboot usb)
then try the command
fastboot flash recovery recovery.img
(if you got PG58IMG.zip open it and copy the recovery.img to the folder where you got adb/fastboot )
Hi,
Take a look at this thread, it may be able to help you out, plus the tool is simple to use to install the recovery as well. Just follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1668276
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
an_xda said:
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
Click to expand...
Click to collapse
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
thinhletien said:
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
Click to expand...
Click to collapse
Yes, I have the drivers (ADB/Fastboot) in a folder on C:\ and have pointed to that folder in cmd prompt (I should mention I have successfully leveraged the commands in the past).
However, I do not have HTC Sync installed so let me give that a shot...
Edit - after installing HTC Sync and connecting the phone (after unlocking the PIN, of course) - it could not connect to my device. Any advice/suggestions? This is probably going to tie into the same reason why I cannot connect via fastboot to my device.
Side note is that I am running CleanROM 6.5 if it makes any difference (stock kernel or whatever the roms come with).
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Venomtester said:
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is enabled in developer options.
Still having no luck.
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Willz said:
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Click to expand...
Click to collapse
I can help you out.
Download and install Android File Transfer, which will install the necessary drivers for your phone to connect to your computer. http://www.android.com/filetransfer/
Enable developer options on your phone by going to Settings > about phone and tapping the build number 7 or so times. Then go to the developer settings and enable USB debugging.
Once this is done, in your folder entitled your "username" in your Mac (the same folder that has Desktop, Documents, Downloads, etc.), create a folder titled Android.
Inside that Android folder, put these two files: http://cl.ly/SMwW and http://cl.ly/SMiC These are adb and fastboot.
Once that's done, open Terminal, type:
Code:
cd /Users/yourusername/Android
and hit enter.
Then type:
Code:
./adb devices
hit enter, and you should see your phone's serial number so long as you enabled USB debugging as described above.
Then type:
Code:
./adb reboot bootloader
hit enter, your phone will reboot to the bootloader
Download this file and place it inside the Android folder we created earlier: http://cl.ly/SMw9 This is the latest TWRP for our phones.
Into the same Terminal window, type:
Code:
./fastboot oem unlock
hit enter, WARNING: your phone will be returned to stock and your storage erased, once that's done, type
Code:
./fastboot reboot-bootloader
and hit enter to reboot back into the bootloader that is now unlocked.
Then to install TWRP, type:
Code:
./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
and then reboot the bootloader again. I would then suggest hitting your down arrow a couple of times and booting into recovery, where TWRP will prompt you to root your device with SuperSU. Alternatively, here is the SuperSU zip that you can put onto your phone's storage and flash in TWRP. http://cl.ly/SMlk
Not sure if you missed it, but alternatively there's a Mac toolkit that's recently been posted.
http://forum.xda-developers.com/showthread.php?t=2515640
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
stelv said:
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
Click to expand...
Click to collapse
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
0dBu said:
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
stelv said:
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
Click to expand...
Click to collapse
When you're in bootloader and you type: fastboot devices what does it return?
0dBu said:
When you're in bootloader and you type: fastboot devices what does it return?
Click to expand...
Click to collapse
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
stelv said:
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
Click to expand...
Click to collapse
If adb devices shows your device you're in recovery, not bootloader
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
stelv said:
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Use fastboot devices if you're in bootloader
Anyhow, the link I posted is a good tutorial, it should get you sorted. Although, even though I have ADB and Fastboot in my Path (ADB works fine), I still have to cd into the platform-tools directory to get fastboot to work. If anyone has some insight into that's I'd be all ears, but I still make it work.
Sent from my Nexus 5 using Tapatalk
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
stelv said:
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
Click to expand...
Click to collapse
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
0dBu said:
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks. I saw a fix in the twrp thread as follows, so i did this. Twrp is working as normal now and no bootloops. I have the factory image downloaded too just in case. Thanks again! Everything seems to be working now.
Dees_Troy said:
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Click to expand...
Click to collapse