4.2.2 now enforces RSA authentication via ADB. This is only supported in later versions of ADB.
On Windows, you can see your local user profile folder's .android folder and see if there's a file called 'adbkey'.
Or use 'adb version' to see if you have the latest version. ADB version 1.0.31 is working.
Google just added this in the ADB protocol last November, so you need the NEWEST ADB:
https://github.com/android/platform_system_core/commit/d5fcafaf41f8ec90986c813f75ec78402096af2d
The keys for your hosts are stored at /data/misc/adb/adb_keys, I believe.
If your ADB works correctly, you will see this when you plug in for the first time. You may still have to reseat your cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Pic credit to rickbosch)
* * *
This will not affect all of you.
But on the stock Android 4.2.2 kernel from Google, I cannot get adb to work (always shows 'adb offline') on the stock kernel. This is with my laptop (a Lenovo Thinkpad), and I never had issues with this before with the same setup.
My current workaround is to use a custom kernel for 4.2.2 (thanks to renaud for delivering)
A custom Fugumod kernel that works with 4.2.2 and does not have this issue with ADB:
http://forum.xda-developers.com/showpost.php?p=37892325&postcount=2167
Stable builds (future?):
http://fugumod.org/galaxy_nexus/stable-4.2.2/
Please report back with the PC/Mac and possibly the cable you are using, thanks.
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
manumanfred said:
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
Click to expand...
Click to collapse
That's default.
I resolved my issue swapping my kernel, not the ramdisk (that's where default.prop is in anyway). Hm...
rickbosch said:
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
Click to expand...
Click to collapse
This never came up for me . Didn't wipe though.
How do you manage devices?
I'm using 4.2.2 and I didn't got that popup!
I extracted boot.img and made it to insecure and changed adb secure line from 1 to 0 and now I can use ADB!
neither did I. Just flashed via TWRP over stock Takju 4.2.1
edit: And about managing devices, I have no idea.
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
xaueious said:
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Screenshot was taken on my phone, and about RSA key and ADB on Windows, I'm afraid I can't answer those for you.
xaueious said:
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Why not!
It lets to use ADB then, now I can use ADB without any issues, before editing default.prop I wasn't able to use ADB!
This is probably a new feature of some sort. Linux works fine, Windows doesn't. Mac probably works too.
Windows works fine for me. Maybe you changed something somewhere. I had 0 problems.
Never changed anything on the phone. Fixed the issue though. I was using an older version of ADB: 1.0.31
Older versions don't support key RSA authentication.
I also had this problem.
Then I deleted some spare copy of adb.exe and its dlls that where installed under \windows\ by some "do-it-all" tool and updated the adb tools with SDK-Manager.
After connecting to the PC, my GNexus asked for confirmation before allowing USB debugging and since then everything is fine :victory:
I updated android sdk tools on my mac today (before that I couldn't launch abd sideload update.zip) and haven't noticed any issues with adb/fastboot commands.
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
For me with stock kernel adb and fastboot ok.
I'm using bigxie rom deodex.
rickbosch said:
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
Click to expand...
Click to collapse
Done
It may seem obvious for some, but wasn't for me.
I flashed the upgrade, with the cable always connected then couldn't get adb to work. Just need to re-plug the cable for the prompt to show up
Is this new version in the latest Android SDK? If not, where can you get it from?
EddyOS said:
Is this new version in the latest Android SDK? If not, where can you get it from?
Click to expand...
Click to collapse
Yes, it is in the new SDK.
On a side note, OP, the image you used and credited in the first post was mine, not manumanfred's.
Related
Hi,
I don't know how but my RSA key is missing from Winmax RSA key checker. no wonder I couldn't connect to my 4G network. I did make a backup using RA a while ago just to backup the Winmax key and nothing else. I located the folder on my SD and could view it from my RA recovery. But when I try to restore it...it says opps something went wrong and check your log file.
I don't know where is my log file and I don't know how to restore this key..any help would be greatly appreciate.
Thank you
place the wimax.img file on the root of your sdcard, open terminal, type
su
then type
flash_image wimax /sdcard/wimax.img
reboot, check for keys
Hi,
I did place the image file on my root under the sdcard and type "flash_image /sdcard/wimax.img"
but it says not found
i also created another folder called wimax and copy and paste my wimax.img in there as well and tried "flash_image /sdcard/wimax/wimax.img"
its also not found
i'm using terminal emulator if that helps
thank you
the file is named wimax.img? it is caps specific so if its named Wimax.img it will error
either change the name or type its exact name with caps etc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using Tapatalk
your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?
It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Clarification: the "not found" error you're getting is in reference to flash_image. Notice that you got the same "Not found" message when you typed "dir", since there is no dir command in that shell.
NewZJ said:
your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?
Click to expand...
Click to collapse
YES and still not found
jesuspgt said:
It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Click to expand...
Click to collapse
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks
hmm. used to have flash_image included. when did it change?
TommyNgo215 said:
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks
Click to expand...
Click to collapse
You really should follow the instructions on that link, they tell you exactly how you need to do this.
NewZJ said:
hmm. used to have flash_image included. when did it change?
Click to expand...
Click to collapse
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.
jesuspgt said:
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.
Click to expand...
Click to collapse
oh i don't have busybox i'm using Terminal Emulator. may that's why?
FIXED
download android terminal emulator, jack palevich author
it works in that one
Edit: not fixed
NewZJ said:
FIXED
download android terminal emulator, jack palevich author
it works in that one
Click to expand...
Click to collapse
Yea thats why i have...i downloaded that one Android Terminal Emulator by Jack Palevich but it doesn't work for me for some reason ((
TommyNgo215 said:
oh i don't have busybox i'm using Terminal Emulator. may that's why?
Click to expand...
Click to collapse
busybox isn't a terminal, it's the name given to the collection of command applications (for lack of a better term), that are used in a linux shell (terminal). Here's a wiki about it: http://en.wikipedia.org/wiki/BusyBox
If you don't want to use ADB, you can try just unzipping http://cyanogen-files.carneeki.net/flash_image.zip
It should just be flash_image in there. Stick flash_image into the root of the sdcard. after that, you should (hopefully) be able to begin using that command.
Edit: that zip file is not one that is flashed via recovery. It's just a plain old zip file. You just need to extract the file inside of it to the root of your sd card
its not that I don't want to use ADB but my knowledge is very limited. I got so confused from reading it and more confused from reading it again. SDK i don't have SDK i don't know what it is and then ADB i'm stupid. its crazy that i have an image here but i can't flash it using RA recovery.
ok i extracted..and still not found..it didn't install that to the phone. oh my what have i done
ADB is really not as complicated as it seems at first.
To get the SDK, go here: http://developer.android.com/sdk/index.html and install whichever flavor applies to you.
Assuming you're in Windows, just load up command prompt and navigate to the folder that the SDK installed to.
Plug your phone in, make sure that debugging is enabled in the USB settings on the phone, and then just follow the instructions step-by-step from that link. Those instructions focus at the end towards flashing a recovery image, but you will just need to substitute wimax in instead.
The right edge of my touchscreen has gone dead, not sure what the problem is, maybe the ribbon cable? I'm not sure, but I contacted htc and they said it's still under warranty and will be repaired (just so long as there's no physical/water damage, ect.) well my phones in pretty good shape, so I'm hoping I wont get charged.
However, I figured I should probably get back to stock and S-On
an quick tutorials on how?
This is why we have a Wiki, and a search function.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
If you have any particular questions, search first, if you can't fix them at that point, then post back to the thread for specific help with a problem.
I can't even figure out the first step :/
how do I check Gfree verify? I type that into terminal emulator, nothing heppens
Edit:
I'm not a n00b and the rest of the instructions look do-able, but how do I do gfree_verify?
bumpity bump bump
It's on the wiki page. You can find it if you search the page for 'gfree_verify'. I've linked the section for you below. Scroll down till you see '5. Verify the success of gfree'.
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
Thank you both very much
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
I go down to the next step, (and honestly, I don't know what my main version is) but when I use "# /data/local/tmp/misc_version -s 1.19.531.1" It says "permission denied"
Bump (sorry)
swee08315 said:
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
Click to expand...
Click to collapse
You are positive the you have gfree.
Your device is positive you haven't got gfree_verify.
Guess who's right?
Follow Bharakrama's link, read, follow, success.
I too was sure I had adb and gfree but it wasn't working. I updated my android sdk and path variable and it worked again.
I'm also trying to return to stock. My gfree is working. How do I know if my main version is higher than 1.19.531.1? I'm using Cyanogen. Do you know how I find, or what the CID for Bell Mobility is?
I'm pretty sure I have Gfree, when I rooted it, it got unlocked and I'm now using it on at&t, that means I have gfree, doesn't it?
I'm thinking that I probably have footclans problem with the adb because I had ubuntu on thiis machine before and I just installed windows recently. I haven't had to use adb since then.
Try reinstalling ADB or updating the android sdk.
thanks, everything works now except this:
Disconnect the phone from USB and shutdown the phone.
Boot into hboot by holding <Vol-Down> while powering on.
hboot should load the PC10IMG.zip automatically and the ask you if you want to update. Press <Vol Up> to start the update.
After updating the radio hboot will start again (screen will get dark for some seconds)
If you had the fake S-OFF engineering hboot installed it will be replaced by this process
Click to expand...
Click to collapse
The text is too fast to read, but I think it says wrong image or something?
edit: theres a bunch of lines, and I think most of them say "no image"
bump bump.
my screen is really becoming very annoying to use now. I really have to get this factory reset soon so I can send it in.
I really need to get this figured out.
Sorry, but if I can get this resolved by the weekend, it would be wonderful.
anyone know why the factory image wouldn't be writing?
I'll try again tomorrow and record what is displayed across the screen if that will help.
Did you name the file right and check the md5 sum? Also make sure PC10IMG.zip is not is labeled exactly that! not.zip.zip unhide file extensions if your on windows. Also it must be on the root of the sd not in a folder of any kind.
Here's a screenshot of the zip on my sdcard
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and here's what happen when I boot with the volume down key pressed:
I also tried to use the following in adb shell, but I get permission denied
# /data/local/tmp/gfree -s on -c T-MOB010
Click to expand...
Click to collapse
Does that last screenshot help at all?
I'm busy with classes, and really need this done before the 1 year warranty is up.
Sent from my HTC Desire Z using XDA App
So I was messing around with different one clicks since I got ADB going on my kindle fire and I was able to Successfully use SuperOneClick 2.2 to root my kindle fire!
Sorry for the mess. Its late, and I wanted to type this up so I could crash...
To get adb going you must download the android sdk (google it).
*Run SDKManager.exe and download the google-usb_drivers package from "3rd party tools"
* Download platform-tools as well
Open a command prompt and run adb update usb to get the .android folder to appear.
goto: %USERPROFILE%\.android and edit the adb_usb.ini and add this to the end of the file and save:
Code:
0x1949
then go into where you have the sdk at and open the google-usb_driver folder and edit android_winusb.inf and add this to the [Google.NTx86] section and [Google.NTamd64] section:
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
save and close
If you have already plugged your kindle into the usb you may have to open device manager and find "Kindle" under other devices and choose the android_winusb.inf file.
Turn on Installation of apps from unknown sources: tap the top bar>choose more...(+)>device
open a command prompt and run adb kill-server then try adb devices..
you should see a device listed.
go here: http://forum.xda-developers.com/showthread.php?t=803682a
download and run SuperOneClick and choose the "root" option. let it go!
Enjoy!
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome!
Why do I have a mac
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
^^ now THAT is funny ^^
Magnesus said:
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
Click to expand...
Click to collapse
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
aimbdd said:
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
Click to expand...
Click to collapse
I almost suspect from their coy comments (yes, it will be rooted, no we don't care, type of thing) That they're just after market share, period. Now let's bring on CM ICS! (impatient optimist in me, sorry!)
My question is can anyone get TTS to work?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
I lawl'd
* * *
Amazon said they wouldn't get in the way of root.
wow, this was quick! i hope we get custom gingerbread and later on ICS roms quick
Rooted Fire
Death2All - Rooting instructions worked like a champ!
Thanks for posting.
Donation to Shortfuse OTW.
Kind regards
Worked Beautifully!
Success!
My Kindle Fire is rooted and happily working with ADB.
Now lets get some dev-action love going on here . Thanks.
Good work
hey so can we now get the Amazon VOD app on our android phones with this root? If So...How do we do it?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
You could do it manually using the zergRush exploit, SuperOneClick just makes it easier for Windows people.
zergRush exploit: http://forum.xda-developers.com/showthread.php?t=1296916
(Usage instructions are there, it's fairly simple - push the binary to device with adb, chmod binary and then execute binary. this gives temp root, push su and busybox binaries for perm root and install superuser.apk)
[This replaces the SuperOneClick part of the original post, you still need to do everything leading up to that (editing adb_usb.ini etc.) - some parts may be changed slightly for mac/linux e.g. I would assume you need to edit a different file than "android_winusb.inf"]
EDIT: Guide for getting ADB working on Mac: http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html (probably applicable to Linux too). Do this, then you can manually root via ADB and zergRush.
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
death2all110 said:
<snip> To get adb going you must already have the sdk on your machine and used it. <snip>
Click to expand...
Click to collapse
Never used it, but I have it installed. I don't even know where to begin
mipakr said:
Never used it, but I have it installed. I don't even know where to begin
Click to expand...
Click to collapse
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
abremel said:
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
Click to expand...
Click to collapse
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
smtom said:
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Actually an easy fix - the unroot button on superoneclick unroots it, and a reboot restores video playback - the instant video app must have some sort of check in place to see if the device is rooted.
abremel said:
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
Click to expand...
Click to collapse
You also need to install the Google USB driver via the SDK Manager I think to generate the other files that need editing.
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..
Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.
Re-Mi has helped me solved my issue! Thank you so much!
Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!
I have read, I have searched thread after thread. I have the Google Pixel XL on Verizon. I have followed the directions to the letter for unlocking bootloader using dePixel. The issue I have is with the Developer Options. I am unable to enable the OEM Unlocking because it is grayed out. I have reset the device like 10 times. I have automatic updates disable in developer options. I need to be point in the right direction or have someone that can relate, to chime in. I am not looking for root....I just want the bootloader unlocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?
You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk
DualSportDad said:
You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I followed to the letter and I get nothing
Mike02z said:
That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?
Click to expand...
Click to collapse
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line
Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?
mikeutsey said:
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line
Click to expand...
Click to collapse
Set the phone from charging to file transfer. After hitting enter for the last command line op pen the chrome browser app. I don't know why but that's what worked for me.
Sent from my Pixel XL using Tapatalk
Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.
jaxenroth said:
Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.
Click to expand...
Click to collapse
The dePixel8 Program has yet to work for me. Still have not successfully unlocked bootloader
Marghost said:
Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?
Click to expand...
Click to collapse
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Was able to get it to reboot with cmd line but still not working. Thanks for all of your help with this
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse
OK I see try close your phone and boot to the bootloader screen with power and vol down pressed at boot. After run the command
fastboot oem unlock
And tell me what you see!
That did it.....thanks guys....never would have even considered physically turning off device and and manually fastboot :highfive:
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse
Np bro glad I helped. If you want give me some thumbs up hehe
Great day
Sent from my Pixel XL using XDA Labs
Is ADB working for you? I'm not sure where your are in the process, so forgive me if you've done these steps:
- enable debugging in developer options (must first tap on build number 10x or whatever
- if you do adb devices from command prompt, do you get the device id? You need to allow the computer to talk to the phone (security authorization on the phone the first time you attempt adb), as well as have drivers properly installed on computer
- assuming adb is writing properly, people seem to have best success with depixel8 if they set screen timeout to 5 min or longer, and after starting depixel8 commands on the computer, is screen blanks out, truth screen back on and try and run an app ...
Hope this helps