Related
[*] shutdown the phone
[*]hold down volume up + power
[*]Now you are in the standard recovery mode
[*]assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows
or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB
[*]assuming you device is seen via fastboot devices, now type "fastboot oem unlock"
[*]accept...and new bootloader is unlocked...
[*]now we need a custom recovery from clockworkmod or amon_ra, and we'll be good to go
Credit goes to gandalf44
Seems like a lot of people are having issues with the amd64 driver from the 2.3 SDK. Here's a workaround:
Go to the PdaNet homepage and download the Windows 7 x64 version of the PC software Download PdaNet
Make sure your phone is not connected to the computer. Install the app from PdaNet. Ignore the warning about HTC sync if you get it, that doesn't matter for what we're doing.
At the end of the PdaNet install, you'll be prompted to connect your phone. Make sure USB debugging is on, and connect to a high speed (as in not through a hub) USB port.
Follow the prompts and accept the unverified driver warning. Let it finish, then reboot your phone into fastboot mode -- power off, then hold volume UP and power.
Open the device manager in Windows (right click My Computer, properties, choose Device Manager from the list on the left.
Find the Android 1.0 entry, with the yellow exclamation mark beside it. Right click and choose to update the driver.
Select to search your computer for the driver manually, and point it at C:\Program Files (x86)\PdaNet for Android\. You will see a warning about an unknown/unsigned driver for sure this time, accept it.
When it finishes, at the command prompt (in the sdk\tools\ directory) type
Code:
fastboot devices
you should now see your Nexus S listed.
Credit to Gbhil
Thank you for this information
So easy??? Lol!!! The only reason i asume somebody could take that phone is this...
The really OPEN SOURCE ....
That was easy and fast.
We can't flash files through the stock recovery?
I dont understand..I did everything you stated but I dont get the option to type anything.
just a fyi. fastboot oem lock will relock the bootloader!!
pimpkogan69 said:
I dont understand..I did everything you stated but I dont get the option to type anything.
Click to expand...
Click to collapse
You need to type it into the command prompt on the computer, not on your phone.
Any way to root without doing this?
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Jr33 said:
just a fyi. fastboot oem lock will relock the bootloader!!
Click to expand...
Click to collapse
Can anyone confirm this? This would be freakin awesome!
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Technically, it's not rooted, but in essence, we all know that once the bootloader is unlocked, we can fastboot flash a custom recovery. And from there, we can flash custom roms or just the su and superuser.apk into the stock rom from recovery. So yea, it is kind of rooted.
DOHCtor said:
Can anyone confirm this? This would be freakin awesome!
Click to expand...
Click to collapse
I can confirm that fastboot oem lock does re-lock it.
crazifyngers said:
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Click to expand...
Click to collapse
yea just found it thanks
Seems I can't update my Android 1.0 device driver.... I've updated everything in my SDK 2.3 but keep getting this ... Hmmmm
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
had same problem use this link
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
Yes you need to force the driver install
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Well once a custom recovery is available then the puzzle is complete.
Okay so I flashed a rom and im stuck in a bootloop, but I cant get into recovery to restore a nandroid. My power button receded so as soon as I put in a battery it immediately turns on. But if i go into bootloader, not the power button nor the volume keys will work. So I cant get into recovery that way. Is there any other way like with adb in bootloader? Or am i screwed lol.
Thanks in advance for help, I could really use it.
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
estallings15 said:
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
perhac89 said:
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
Click to expand...
Click to collapse
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
saranhai said:
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
Click to expand...
Click to collapse
Then only thing Im getting is Hboot Usb Plug, not Fastboot Usb
Edit: Okay now I have Fastboot USB showing, but cmd doesnt recognize fastboot, nor will it connect to my device
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Jack_R1 said:
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Click to expand...
Click to collapse
All Im getting when I do this is error device not found
Bump.
I can't get it back into fastboot usb either, I think the power button fixed for a second before and selected fastboot.
Do you have a warranty on this phone?
If not, you may want to open it where you can access the power button more easily.
Before you do that though, get it caught in a bootloop and try adb reboot recovery. Reboot and try again at a different point. It should work eventually. Persistence might pay off.
Sent from my HTC Glacier using XDA App
perhac89 said:
All Im getting when I do this is error device not found
Click to expand...
Click to collapse
Since you're in the bootloop, your device is connecting and disconnecting. See when it connects (easily recognized Windows "USB device connected" sound), then execute "adb reboot recovery" until the command catches or the phone reboots. Attempt several times.
If it won't work - open the phone and fix the button.
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
enochthegreat said:
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
Click to expand...
Click to collapse
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
I used the hiensberg guide https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
What do you think is the best option from here?
Are you trying to get into fastboot with it connected to computer?
Iceburn1 said:
Are you trying to get into fastboot with it connected to computer?
Click to expand...
Click to collapse
No im already in fastboot mode. Im just trying to restore my devioe so that it works. When i power on my phone it displays the unlocked bootloader warning then goes into fastboot mode. The screen reads-
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
On top of this my device will not connect to my computer through usb and all my data is deleted included twrp. I really dont know what to do
acejavelin said:
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
Click to expand...
Click to collapse
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
enochthegreat said:
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
Click to expand...
Click to collapse
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
acejavelin said:
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
Click to expand...
Click to collapse
The response is no devices attached. I am android 6.0
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
Have you tried rsd lite it might recognize your device?
acejavelin said:
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
Click to expand...
Click to collapse
My pc operating system is windows vista and my device used to show up on device manager. I used to be able to plug the usb and be able to look at my phone saying device connected
enochthegreat said:
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
Click to expand...
Click to collapse
Do you have this when you boot into bootloader/fastboot mode?
Power off, vol - & power?
I think you can't repair it in home.
It looks like you flashed something wrong or something in wrong place.
F.e.: twrp into boot partition.
jonomods said:
Have you tried rsd lite it might recognize your device?
Click to expand...
Click to collapse
Hmm i just tried that and no device showed up. I think after this im just gonna buy a fresh usb cord and if that does work i am scarping this phone. I overall had a very bad experience with this phone anyways. Ill get back to you once i try.
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
acejavelin said:
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
Click to expand...
Click to collapse
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
enochthegreat said:
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
Click to expand...
Click to collapse
Hmm... Sounds like bad luck, hopefully a new, quality cable will take care of it for you
Looks like it was all bad luck. A day after I bricked my phone my charger port broke
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Having the same exact issue here, hope someone has a way to fix it.
sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.
I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.
Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.
After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.