Related
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.
JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse
Hard boot the OUYA and laptop, adb via USB seems to work again.
So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
If you can get into recovery, just copy over the latest OTA file onto a usb stick, wipe Data/cache then flash the OTA.
Also for windows, not doing " echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini" " can sometimes make it not be found on its own, was originally required to do it for ADB
In recovery mode, the only way is to flash the OTA via ADB. There is no option like from usb-stick or internal/external sd-card.
and my adb_usb.ini seems to be correct.
But thanks for your suggestions (=
I had the same issues. I'm waiting on a replacement. http://forums.ouya.tv/discussion/comment/13562
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
I haven't messed with root/cwm, since there really isn't much brick protection... you might try 'adb reboot recovery' during bootup... if you can force it to fastboot, you can boot the recovery image, and it should have adb with su access, you should be able to repair you mistakes from there, or just do a data/cache reset to wipe the device.
EDIT: assuming you can get to fastboot somehow, you would just have to 'fastboot boot recovery.img' where recovery.img is the build of cwm.
EDIT 2: try booting with a usb keyboard, during boot, you might be able to spam the kernel with the key combination alt-SysRq-i. This may force it to boot into recovery... Then you should be able to either use regular ADB, maybe push a OTA.zip via ADB, and ultimately install a OTA... Hope some of this is helping, I have no real hands on practice with much of ADB on this specific device... But I'm a LONG time android tinkerer.
EDIT 3: If you're able to get it to crash and boot into recovery via Alt-SysRq-i . It's a recovery based on 4.x as it should be... and you should be able to 'adb sideload OTA.zip'... Sorry for all these edits, I just keep realizing I have more to say.
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
HaYNigloo said:
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Will that require root?
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
HaYNigloo said:
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
Click to expand...
Click to collapse
Yeah that's what sucks. I followed a post on here and thought I had the unit rooted but either I messed it up or the OTA updates wiped it out. Since I no longer have adb access I cannot get root to enable wireless adb access. Snake eating its own tale
Oh! I believe there are wireless adb apps that don't require root. Try looking into the play store to find out which ones.
Edit 1: The Play Store has a wireless ADB app by Sherdle [ADB Wireless (no-root)]which doesn't require root!
Sent from my Galaxy Nexus using xda app-developers app
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
KrelianGS said:
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
Click to expand...
Click to collapse
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
HT123 said:
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
Click to expand...
Click to collapse
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
KrelianGS said:
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
Click to expand...
Click to collapse
I am pretty sure USB debugging needs to be on for ADB to accept connections. make sure it is on
Hello,
I have tried to install cm11 on my ouya with the result that I got only a black screen now.
ADB says that the ouya is offline!
Is there any trick to get in fastboot?
Did you have any type of recovery installed? Might be too late, but remember you need to have Bootmenu installed first, if you did, then it should be fixable. If it doesn't work...pretty sure Target sells OUYA in-store for like $35. Their website says $89, but the last few times I've been there they were $35-40.
brandogg said:
Did you have any type of recovery installed? Might be too late, but remember you need to have Bootmenu installed first, if you did, then it should be fixable. If it doesn't work...pretty sure Target sells OUYA in-store for like $35. Their website says $89, but the last few times I've been there they were $35-40.
Click to expand...
Click to collapse
Hey,
thank you for your answer!
I had cwm installed and was in cwm before! then i did something wrong
Your tip with a new ouye is no help for me, because I am from germany.
Here costs the ouya 99€ that are nearly 135$.
You need to have CWM installed, then OUYA BootMenu, then CM11. When you say ADB tells you the OUYA is offline, I assume you were doing the ADB TCP connection before. Does Windows detect anything when you have your OUYA plugged in to your computer? Does Device Manager show "OUYA (or OUYA 1.1)" with a yellow exclamation point? If not, then you're probably hosed - but, I believe their rooting policy is pretty laxed, you may want to see if it would be worth sending it in for a repair/replacement if you can't get it started.
Anyway, if it does show up in Device Manager, then you need to modify the USB driver (there are several guides, including on this forum), disable driver signing if necessary, and you should be able to get fastboot to work (assuming you're in this situation).
Hi! Never used adb over tcp! Cwm was installed... i was in cwm and tried to install cm11 over adb... since this its bricked! I have bought my ouya on ebay and have no invoice... so there is no warranty!
The ouya is shown up as adp device... tried the other ones in the driver package i have got... it worked before this crash!
Gesendet von meinem XT894 mit Tapatalk
Does it show up as actually connected though? If it does, then the recovery partition should still be there (I can't imagine CM11 includes a recovery partition, otherwise we wouldn't need BootMenu it seems to me). If it does then adb reboot recovery should work, if you can get to recovery then you're golden.
What did you mean with connected though? if it is shown up in device manager? Yes it is!
I only see a blank screen on tv!
So if you type adb devices does it show up as connected? If it does, try adb reboot recovery.
brandogg said:
So if you type adb devices does it show up as connected? If it does, try adb reboot recovery.
Click to expand...
Click to collapse
Hi,
the device is shown up with its device ID as offline!
adb reboot brings: error device offline!
This may help
ibaxx said:
Hello,
I have tried to install cm11 on my ouya with the result that I got only a black screen now.
ADB says that the ouya is offline!
Is there any trick to get in fastboot?
Click to expand...
Click to collapse
Found an unbrick method it works as long as adb is on and clockworkmod is accessible,i saw your post and i uploaded my guide just so take a luck if you have had no joy,it has a tool to get if adb is not working for xp so you could try that if your on xp and only get OUYA? showing in device manager,this was my problem and this is something i figured out alone,i couldn't edit anything in ini files to make it work as adb device,but this tool saved my @ss.It took 48hrs of painstaking scouring the net to fix the device, i had put boot menu on but the console had been destroyed playing after showing red on normal boot,nobody gives the details anywhere i find in laymans to apply the cynogenmod firmware, someone should put one up on xda that has simple laymans step by step points to follow on setting it up,i got it on just would not boot past the logo for cynogenmod firmware?And online nobody has written a laymans tutorial infact only guide i found is the most uninformative and convoluted tutorial i have ever seen before.
Hi I had ADB enabled device and could already get a backup.
What i want is to still use my device with a broken screen - Vysor.
But i need to authorize my pc. I could see thanks to some screenshots, that i get the authorize this pc prompt.
But was not able to click it and don't know how many times and when i should click it.
But now i want to authorize it. I also rebooted into recovery without any luck. Might need to input the Pin but that doesn't work via USB-logitech keyboard dongle.
Help appreciated. Can i just use fastboot and reflash everything?
Can i also than root it and use twrp or would i somehow need the screen for that?
Help appreciated. My best bet would be to get vysor working with adb access.