Develop Bugs

[MOD] CM9 MultiTasking Modifications [ICS Browser Style - Chrome Style - WP7 Style]

I saw these modifications to recent apps which I really liked so I thought I would add it to CM9 on the E4GT. I originally found these modifications in the Nexus forums here and here. There are 3 versions, stock ICS browser style app switching, pictured on the top left[SystemUI.apk from attachments below], Chrome style [SystemUI_Chrome.apk from attachments below] pictured on the top right, and Windows 7 Phone Style below them [found here].
{
"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"
}
These modifications are based off of ICS framework from CM9 Alpha 3. The mod requires 2 modified apks, framework-res.apk and SystemUI.apk which will be attached below.
Install instructions:
If you're using the chrome style, rename to SystemUI.apk before pushing so it overwrites. You will use the same framework for either.
Code:
adb root
adb remount
adb push SystemUI.apk /system/app
adb push framework-res.apk /system/framework
adb reboot
Enjoy
Note: Pushing framework will likely wipe your Google account.

Thank you sir.

Cool. Is it possible to do the chrome style one too?
Sent from my SPH-D710 using Tapatalk 2

satur9ine said:
Cool. Is it possible to do the chrome style one too?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Sure. Gimme a few.

I dont use adb much, do these apks just need to be in the same folder where the adb.exe is located and then run the commands? thanks

rsalinas1 said:
I dont use adb much, do these apks just need to be in the same folder where the adb.exe is located and then run the commands? thanks
Click to expand...
Click to collapse
Yes. Or you can use a file browser with root if you're more comfortable doing that.

I'd rather get comfortable with adb so I added it to my path variables so thats all good. Now I ran the adb push command and it tells me cannot stat 'SystemUI.apk' no such file or directory. Any ideas, both are sitting in the same folder.

rsalinas1 said:
I'd rather get comfortable with adb so I added it to my path variables so thats all good. Now I ran the adb push command and it tells me cannot stat 'SystemUI.apk' no such file or directory. Any ideas, both are sitting in the same folder.
Click to expand...
Click to collapse
I thanked you because it's refreshing hearing that, so thanks.
Are you able to remount? You will need to change directories into the folder where you have the files as well. Adding adb to your path will allow you to execute its functions across the system but won't allow you to push files from within that path from a different location.
Are you on windows or linux?
ALSO:
Chrome style added to OP. Please read directions. Enjoy.

barnacles10 said:
I thanked you because it's refreshing hearing that, so thanks.
Are you able to remount? You will need to change directories into the folder where you have the files as well. Adding adb to your path will allow you to execute its functions across the system but won't allow you to push files from within that path from a different location.
Are you on windows or linux?
ALSO:
Chrome style added to OP. Please read directions. Enjoy.
Click to expand...
Click to collapse
No problem, I want to learn and do this kinda stuff on my own lol. Im on windows, adb remount succeeded. How would I "change directories into the folder where you have the files?" I have both in the same folder as the adb.exe (C:\android-sdk-windows\platform-tools)

rsalinas1 said:
No problem, I want to learn and do this kinda stuff on my own lol. Im on windows, adb remount succeeded. How would I "change directories into the folder where you have the files?"
Click to expand...
Click to collapse
Code:
cd path/to/where/you/have/them
Or, when you load up cmd, it will sit you in your home folder out of box. You could just move the files there as well and not have to worry about changing directories at all. Either way.

barnacles10 said:
Code:
cd path/to/where/you/have/them
Or, when you load up cmd, it will sit you in your home folder out of box. You could just move the files there as well and not have to worry about changing directories at all. Either way.
Click to expand...
Click to collapse
Sorry, still a bit confused and I still cant get it to work. I tried adb push C:\android-sdk-windows\platform-tools\SystemUI.apk /system/app and it still gives me the same error? Sorry to keep bugging you barnacles.

rsalinas1 said:
Sorry, still a bit confused and I still cant get it to work. I tried adb push C:\android-sdk-windows\platform-tools\SystemUI.apk /system/app and it still gives me the same error? Sorry to keep bugging you barnacles.
Click to expand...
Click to collapse
No worries. Open up a new terminal and do this..
Code:
cd C:\android-sdk-windows\platform-tools
Code:
adb push SystemUI.apk /system/app
[SIZE="1"]assuming you have adb mounted[/SIZE]

Windows Phone 7 Style App Switcher
This mod is based off of ICS framework from CM9 Alpha 3. The mod requires 2 modified apks, framework-res.apk and SystemUI.apk which will be attached below.
Use the install instructions from here if you're not sure how to install.

barnacles10 said:
I thanked you because it's refreshing hearing that, so thanks.
Are you able to remount? You will need to change directories into the folder where you have the files as well. Adding adb to your path will allow you to execute its functions across the system but won't allow you to push files from within that path from a different location.
Are you on windows or linux?
ALSO:
Chrome style added to OP. Please read directions. Enjoy.
Click to expand...
Click to collapse
I've used ADB a few times with my old Nexus One, but it was always a pain having to remember what directory ADB was in, only just learned how to add it to System Path today. It's so nice to just be able to type ADB at any command prompt and it works.

barnacles10 said:
No worries. Open up a new terminal and do this..
Code:
cd C:\android-sdk-windows\platform-tools
Code:
adb push SystemUI.apk /system/app
[SIZE="1"]assuming you have adb mounted[/SIZE]
Click to expand...
Click to collapse
Thank you, finally got it working with your help. If I wanted to get familiar with linux, which version would you suggest to a beginner?

Will this get wiped and reset to original when I update CM9? I'm running darchstar's CM9 BTW.

rsalinas1 said:
Thank you, finally got it working with your help. If I wanted to get familiar with linux, which version would you suggest to a beginner?
Click to expand...
Click to collapse
Ubuntu.
Ubuntu even offers something walled "wubi" or windows ubuntu, which allows you to install Ubuntu onto a windows PC much like an application. It will walk you through an install (up to 30gig of designated storage on it I believe) and set up a boot loader for you to choose on boot. Then, if you ever want to get rid of it, you uninstall it like any other app on windows.
Otherwise you can download the iso and install it that way through partitioning. Whichever you'd feel more comfortable with to start.
garfnodie said:
Will this get wiped and reset to original when I update CM9? I'm running darchstar's CM9 BTW.
Click to expand...
Click to collapse
Yes it will. I will try my best to keep them up to date.

barnacles10 said:
Yes it will. I will try my best to keep them up to date.
Click to expand...
Click to collapse
Would it be possible to take the update zip darch releases and just swap out the files in it with yours and it all work? Will this still wipe the google account and need to be setup again upon booting?

garfnodie said:
Would it be possible to take the update zip darch releases and just swap out the files in it with yours and it all work? Will this still wipe the google account and need to be setup again upon booting?
Click to expand...
Click to collapse
Depending on the changes made between now and then it's unlikely. If there are any changes to framework-res or SystemUI coming from upstream or darch then these mods will need to be updated. [which is very likely]

barnacles10 said:
Ubuntu.
Ubuntu even offers something walled "wubi" or windows ubuntu, which allows you to install Ubuntu onto a windows PC much like an application. It will walk you through an install (up to 30gig of designated storage on it I believe) and set up a boot loader for you to choose on boot. Then, if you ever want to get rid of it, you uninstall it like any other app on windows.
Otherwise you can download the iso and install it that way through partitioning. Whichever you'd feel more comfortable with to start.
Click to expand...
Click to collapse
I will look into 'Wubi' Thanks for everything Barnacles!

[Resolved] ADB No Longer Working on Android 4.2.2? - Update your ADB!

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.

[ROOT, CWM] JXD S18-03-xxxx RK2926 mini pad [Guide]

In this guide i will show you how to root a JXD S18 03-xxxx device.
This method was tested on the following device:
OS: Android 4.1.1
Kernel: 3.0.36+ Feb 2
Soc: Rk2926
Model: S18-03-201304-4GB-00727
Root:
0. Download files.zip(from here) extract it and open it in explorer.
1. Connect your device to your computer (micro-usb)
2. Unmount all storage devices (TF/SD card, onboard TF/SD, etc..)
3. Enable USB Debugging (Under settings > Options for developers > Enable USB Debugging)
4. Open ''AdbDriverInstaller.exe'' and install the universal ADB driver
5. Automated process for rooting the device ''ROOT ME.bat'' Press any key and just wait and let the tablet reboot.
6. Manual root:
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
And now you have root.
{
"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"
}
Make sure to update su(super user) after rooting. Because it is outdated.
You can either use adb push for this or you can use the Google Play store to download the latest bin.
CWM-recovery
Download: http://files.androtab.info/rockchip/rk2928/20130425/S18-03_CWM.zip
From adb root shell
1. extract flash_image and recovery.img from CWM.zip
2. put flash_image and recovery.img into device, e.g.
adb push flash_image /dev/
adb push recovery.img /dev/
3. enter root shell (adb shell)
4. flash recovery.img into recovery partition with flash_image, e.g.
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Read this when you have any issues
CWM installation problems, please try another method if this doesn't work for you.
Link: http://androtab.info/clockworkmod/rockchip/install/
If you have any issues while rooting please try:
adb kill-server
adb devices
And see if the devices is listed after killing the server.
If it is not than u may have another soc (older version does have other rockchip and the adb driver wont work properly).
This guide is for the latest version as if 1st May 2013: S18-03-XXXX (4.9.2013)
If you still have no output from adb devices you can try one more thing!
By editing android_winusb.inf in C:\Windows\System23\Drivestore\Filerepository\android_winusb.inf_amd64_neutral_<random_chars>
You will see two of those folders.
Open it with a text editor like notepad++ or notepad make sure you have nt authority rights
android_winusb.inf:
Code:
;------------------------------------NTx86------------------------------------
[Google.NTx86];
For loopback testing
And add this after the first space of declaring hardware ids;
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Tested and working on the following devices:
Audiosonic T-17B 7" tablet (Kmart webshop version) ✓
S18-03-XXXX (4.9.2013) ✓
S18-03-201302 (4gb-00905) ✓
S18-02-XXXX (x.x.2012) ?
Credits: me, icood70pro, fun_ for modding CWM for rockchip, all credit goes to original CWM author koush and all its contributors.

How about S18-02-xxxx ?
I got myself a S18-02-xxxx, The ADB drivers behave oddly for this gadget. The driver installs, but SuperOneClick can't locate the device.
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Think you can setup something?

macrat said:
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Click to expand...
Click to collapse
Can you get access to adb shell and what os are you running? Modified adb doesn't seem to work properly on windows 8 you need to change this in order to make it work for windows 8 i think (at least you can try).
Start -> Run -> Type: "gpedit.msc" (Without quotes) -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> Turn off Application Compatibility Engine <- Disable this
It might be the S18-02-xxxx. Model 02 has another soc i think, can you download a app in the play store for me? Type in: "Cpu info", download and install -> "CPU / RAM / DEVICE Identifier". And tell me what soc you have in it. Because the older versions may have a a9 amlogic 8726-m3l soc in it.
Please try that and verify if that worked for you or if you get adb shell access. Thanks,
and sorry for the late reply.

Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?

switchblade88 said:
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
Click to expand...
Click to collapse
Yes i can and sorry for that mistake. Thanks for confirming that it did work for you on another device with the same soc.

Resquest download password
NiTrOwow said:
0. Download files.zip(from) extract it and open it in explorer.
Click to expand...
Click to collapse
I not success download the zip file because ask me for a password. It's possible obtain this password please?

Stef20 said:
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Click to expand...
Click to collapse
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
And my content does not even include <br /> == space/enter ...
FYI. PROBLEM IS SENT TO FORUM ADMIN.

Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!

Stef20 said:
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Click to expand...
Click to collapse
Alright man good luck and let me know if it works for you and let me know the model number

I will for sure. I wait a new tablet S18 from China just I'm not sure if I will have a s03 or s02 model. I suppose is a S03.

NiTrOwow said:
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Click to expand...
Click to collapse
Thanks. This problem is now fixed. it will not ask for a password now.
Mike

Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
MikeChannon said:
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Click to expand...
Click to collapse
Thanks Mike that was fast :')
Sent from my HTC Sensation using xda app-developers app

NiTrOwow said:
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
Click to expand...
Click to collapse
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.

Stef20 said:
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Click to expand...
Click to collapse
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:

NiTrOwow said:
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
Click to expand...
Click to collapse
It's fun view the inside without open it I view have a little more space for a bigger battery

Stef20 said:
It's fun view the inside without open it I view have a little more space for a bigger battery
Click to expand...
Click to collapse
Forgot to say that this battery for the S18-03 has a pcb on the battery (fail safe, anti-overvolt). It did surprise me because most cheap china products don't have that and it is a risk if you want to use it a lot because it may someday explode if you don't have this haha .. Battery looks like a BL-5B/BLC-2 from nokia without the plastic housing.

Finaly I received my S18 today and it's a S03, just a big trouble... after only few hours of use, the power button refuse work now... It's a cra* product I received...

I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.

Stef20 said:
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Click to expand...
Click to collapse
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.

NiTrOwow said:
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
Click to expand...
Click to collapse
I wait a new S18, just it's very long to receive it with the cheap post chipping.
I want root it because I hate not have the control

[Q] Can't figure out how to flash CWM via Mac OS X

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!!!

Helo. Can't perform any commands via shell on bueller-5.2.1.0-rooted_r1, 1st gen box

Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title

seems like there some SU related issue.
is that how its supposed to look in the application manager?
{
"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"
}

mrwp said:
Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title
Click to expand...
Click to collapse
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
mrwp said:
seems like there some SU related issue.
is that how its supposed to look in the application manager?
Click to expand...
Click to collapse
Thats how it looks on everyone's. With rbox roms you cant open supersu app.

KLit75 said:
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
Thats how it looks on everyone's. With rbox roms you cant open supersu app.
Click to expand...
Click to collapse
yeah I did type 'su' quiet a few times untill su popup appeared and Im not sure what was wrong untill then, but it worked on the next day itself kinda. at least I dont recall doing anythng specific for it to work.
still not able to start the full unlock procedure tho, gives me the same error even with root prompt

screenshot

mrwp said:
screenshot
Click to expand...
Click to collapse
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.

ImCoKeMaN said:
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.
Click to expand...
Click to collapse
I am running adb push from my machine, from adb shell

mrwp said:
I am running adb push from my machine, from adb shell
Click to expand...
Click to collapse
If you don't understand the difference between your pc's command prompt and firetv shell you aren't ready. the command adb push can't be run from adb shell as you are seeing.

I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...

mrwp said:
I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...
Click to expand...
Click to collapse
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.

rbox said:
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.
Click to expand...
Click to collapse
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.

mrwp said:
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.
Click to expand...
Click to collapse
Well you can't downgrade... so it doesn't matter.

ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now

mrwp said:
ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now
Click to expand...
Click to collapse
If you were on 51.1.1.0, then you already unlocked...?

rbox said:
If you were on 51.1.1.0, then you already unlocked...?
Click to expand...
Click to collapse
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall

mrwp said:
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall
Click to expand...
Click to collapse
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.

rbox said:
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.
Click to expand...
Click to collapse
cool, then I'm all set. still lots of things to grasp though.
thanks a lot!

Did you find a fix?
Hey, just curious to see if you found a fix for this. I had a similar issue. I upgraded my friends AFTV to os5 from 3. Everything was unlocked and rooted but something went wrong when installing Xposed. Basically I didn't realize I had a boot issue at first and it didn't take. Now the AFTV skips TWRP and just goes into the normal AFTV OS. The OS still seems rooted just doesn't bring up the recovery. But I also cannot ADB into it either. Keep getting permissions errors.
Any idea to fix this? Or any idea on how to even connect into it again?
Also here is what I posted on AFTVnews when it happened:
"Wat happens if you sideload xposed before installing the installer it in TWRP? Because I did not read (and did just that (Step 3 before step 2) though I did not launch it) and side loaded it. Now I my AFTV 1 skips TWRP and just goes into the Amazon Home Screen. I also keep getting permission errors in ADB. Also says [email protected], instead of [email protected] Is there anyway to reverse this? It had TWRP running and newest RBOX FireOS5. I’m not bricked, just lost boot to SPMC and recovery access."
AND
"Correction, it’s “127|[email protected]”"