Database Info

[APP - Nexus, MT3G, Droid, Evo, Hero] Search2Play - Control Music with the Search Key

Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"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"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3

Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release

If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.

Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help

bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble

Droid Support!!!!

Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.

hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.

My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.

hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?

bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?

hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.

Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?

hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine

Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.

hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market

Donate version now just to support me, added support for all devices to free version.
Please donate!

1.3 version uploaded
See changelog.

Any updates on newer phones?

KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.

[How-To](UPDATED 11/1/10)Working Marketplace in 2.2 Emulator (no system.img)(ROOTED)

This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.

Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal​
{
"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"
}
Tweaks:
1: root (done!)
2: busybox (done!)

Wow nice....

Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!

so cool!! Good job man!

Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.

Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.

I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco

I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.

I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco

I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.

Thanks dbzfanatic, that avd worked great.

Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

A lot of apps can not be found in the Market ... I cannot find Lookout....

Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.

Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!

Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.

Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work

Supercharged Dropdown Toggles

Here's a couple alterations to the quickpanel toggles in the dropdown of Supercharged V4 (the 3rd one is the original if you want to revert back).
You need to replace your SystemUI.apk found in /system/app/
cogeary said:
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
-Your phone will reboot and the notification toggles should be installed!
Click to expand...
Click to collapse
Let me know how you all like it and if I should change them. I was going for toggles that were more distinct from their on/off states. Hit the "thanks" if you like 'em and enjoy!
First:
{
"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"
}
Second:
No Bars:
Thanks to lfaber06 for the great ROM we have available to us.

Hey so i was jw... will this be on supercharged v5? Either way. Nice job!

Deliberate said:
Hey so i was jw... will this be on supercharged v5? Either way. Nice job!
Click to expand...
Click to collapse
I have no idea if lfaber06 will include it. I'm perfectly fine with that if he chooses so. Thanks for the compliment!

Is he working on a v5? Jw. I guess I should of asked him. But still to new for the development section. Lol

Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!

loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
I can do that this evening when I get back home. Shouldn't be too hard (just set full transparency to 3 images).
Sent from my MB865 using XDA App

loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
It's up now. There is a way to get rid of the padding under the icons (since the bars are no longer there--well, they're actually there, but invisible), but I'd rather not tackle that right now. It involves xml edits that I've done before (back in my Captivate days ), but I don't remember exactly and would rather not spend the time right now (sorry).
I hope it's what you had in mind.

Awesome. Looks great. Thanks for the quick turnaround!

so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?

Deliberate said:
so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?
Click to expand...
Click to collapse
Do you mean you do the
cp /sdcard/SystemUI.apk /system/app/
but it doesn't actually copy it over? Do you get an error when you try this? If you do this with your phone on, you will get a force close right away and then you need to type "reboot" while still in the adb shell and then your phone will reboot and everything is cool.
Could you explain a little more of what you did? I'll try to help, but I'm not very experienced with adb yet (Jim or lfaber06 among others and tutorials can help better with this).

Ya i put adb shell
Su
Then that code and it said there was no such file. I renamed it though

Do you see the file on your sdcard as "SystemUI.apk" without the quotes? This is what it needs to be (I assumed that's what you mean when you renamed it, but just making sure). If it's not that exact name, it won't overwrite the old one in /system/app/. Also make sure you have permissions set to write to /system/ (I actually would just use rom toolbox or something and use the script in there).
If nothing else, have you tried to reboot both your phone and computer? Sorry I can't be more help. I personally had the files named on my computer to "SystemUI.apk" before putting it on my sdcard (instead of renaming it after it's already on the phone). That might be something else to try, but I doubt that would be the reason. Someone smarter than I could probably figure it out.

Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!

Deliberate said:
Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!
Click to expand...
Click to collapse
I'm in the same boat with you on the adb thing . I'm making guesses on what it might be without truly understanding how to efficiently use adb. I believe you can use it with the phone off, but I haven't tried yet. Ultimately, I hope to get around to making a flashable zip for things like this. However, I need to spend a little less time tinkering for right now (and I brought my phone back to stock in preparation/hope of the pre-release soak). Let me know if you figure anything out (I'd like to learn as well).

I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?

I used this to mount it as write (after "adb shell" and "su"):
mount -o rw,remount /dev/block/stl9 /system
I found this thread useful for adb:
http://forum.xda-developers.com/showthread.php?t=872128

Deliberate said:
I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?
Click to expand...
Click to collapse
I hope I will be...I filled out the survey pretty quick after getting the email [fingers-crossed]. I haven't heard anything since (Sunday).

One other thought I just had:
When you rename the file, did it show the extension (.apk) or just SystemUI_second (or whichever one you're trying to use)? I'm wondering if by renaming it "SystemUI.apk" that it's actually seeing "SystemUI.apk.apk" or something. Doubtful, but just another thing to check.

No i wonderd that 2 so i tried SystemUI without anything and it still didnt work. Idk. Thanks for all your help though and good luck with the soak!

Oops sorry forgot to turn the page, didn't see the whole next page of replies XD
Anyways... just making sure, when you say you did "Su" did you type in "su" or "Su"?
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
Click to expand...
Click to collapse
-Your phone will reboot and the notification toggles should be installed!

How-To flash your boot.img on Mac OSX

First of all, I think this tutorial is needed since I see this question pop up everywhere and most flashing/rooting tutorials are for Windows. I found myself struggling a lot with flashing on mac since it so much easier on Windows and there are plenty of tutorials on the net for windows but not so much or very poorly for Mac . So I hope this clears out much of your questions on how to flash for a mac.
Download the mac version of the Android SDK from the website.
{
"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"
}
Click to expand...
Click to collapse
Unzip it and place it on your harddrive where you will never delete it. For example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx
Go to the unzipped folder and then navigate to tools. Double click android and let it run. It will open terminal windows and the android sdk itself. Let it load
It will look like this:
Now install the tools, platform tools and I also installed the sdk since 4.0.
Click to expand...
Click to collapse
Download the fastboot files (boot.img and fastboot-mac) here.
Unzip them and place them in the platform-tools in your android-sdk directory for example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx/platform-tools/
Now you download the ROM you want. Here are the most of them located for the HTC One S and you copy it to your phone.
Boot into recovery. If you don't know how to do it, here is a short guide:
Power Off while holding the down volume button
You are into bootloader now if it restarted
Navigate to recovery with your volume buttons
Press the power button to select recovery
Click to expand...
Click to collapse
Then you do the following steps:
Wipe data/factory reset
Wipe cache partition
Install zip from sdcard
choose zip from sdcard
Then you choose the zip you downloaded and where you put it on your phone
Let it install
Click to expand...
Click to collapse
If it is installed:
Turn your phone off while holding the down volume button
Let it boot into bootloader
Connect your phone to your Mac
Select fastboot in bootloader
It will change to fastbootusb
Click to expand...
Click to collapse
Open up Terminal on your mac and type following commands:
cd /Users/your_username/Documents/Android/android-sdk-macosx/platform-tools
chmod +x fastboot-mac
/Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/fastboot-mac flash boot boot.img
You could replace "/Users/your_username/" with "~/" (Option + N). (Thanks to m1schi)
Click to expand...
Click to collapse
let it run and it should show you something like this:
Now reboot and enjoy your flashed ROM!
Note: if this helped you in any means: please leave a thanks.

You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.

m1schi said:
You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.
Click to expand...
Click to collapse
Oh thank you! will put it in there.
Sent from my HTC One S using XDA

Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac

solracarevir said:
Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac
Click to expand...
Click to collapse
Well, if they want to work with adb and such they need to download the sdk. So yeah, I know it was a shorter way but i thought: give it the full on way for people so they are sure.

ive done this 14 times and every single time it says no such file or directory this does not work

chuuw33 said:
ive done this 14 times and every single time it says no such file or directory this does not work
Click to expand...
Click to collapse
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support

You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary

torxx said:
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support
Click to expand...
Click to collapse
thanks i'll give it a go
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
C0mpu13rFr34k said:
You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary
Click to expand...
Click to collapse
thanks i'll try this out

I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?

sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
The op of trickdroid thread. You may need to change boot may need to edit scripts boot.IMG depending on what ROM your running.
Sent from my Nexus 7 using Tapatalk 2

sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
Try this: cd to folder where your fast boot is, then type:
./fastboot-mac flash boot boot.img
Sent from my HTC One S using xda premium

copy file to phone
Hi,
So i unlocked my bootloader yesterday and flashed a custom rom and my phone was working fine. after this though i wanted to use cyanogen mod, so, using rom-manager i downloaded a stable build of cyanogen mod... since then when the phone starts up, it starts up in cyanogen but there are lots of problems...1.it doesnt recognise my sim.2wifi doesnt work.3 my htc one x now isnt being being recognised as a driver on my mac...so this means i can't easily download a new rom and try to flash that, nor can i connect it to a pc and move a new rom file into my phones storage....
i have been told i need to fastboot the phone and flash a new boot.img... so ive downloaded sdk now, and gone through all of the steps up until the instruction *copy rom file to phone*....any ways to work around this, as i cant simply just copy the file to my phone, i think ill need to use terminal or sdk, but im not proficient enough with either of these
thanks for any help u can give

[Zte][warp7]Permroot[kingroot]

Will type up better guide later on gonna include my ota i pulled as well maybe help someone
btw do at ur own risk im not responsable if u mess the phone up
added batch script hope it works to automate the process and guide u. before u can use this guide or batch script make sure to enable developer settings and adb
you can download it this https://forum.xda-developers.com/attachment.php?attachmentid=4181698&stc=1&d=1497456929 extract it go into the folder find root.bat double click file.
or follow the guide below
1.need to get temp root with king root first grab that here https://kingroot.net/ grab file for android not windows version
grab this file https://forum.xda-developers.com/attachment.php?attachmentid=4180414&stc=1&d=1497364232
2.once extracted go inside folder. hold down shift key and right click inside the folder. click open command window 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"
}
unhide for root guide
3. type this "su"
then continue guide
4. type this "getprop ro.product.name"
should show output "ZTE_BEAM"
5. type this "setprop persist.sys.k ZTE_BEAM"
6. type this "getprop persist.sys.k"
output "ZTE_BEAM"
7. type this "cd /dev/block/platform/soc.0/7824900.sdhci/by-name/"
Lets backup recovery
8. type this "dd if=recovery of=/sdcard/recovery.img"
Lets write boot to recovery!
9. type this "dd if=boot of=recovery"
10. type this inside of adb shell "reboot recovery"
if u get black screen just hold power down to reboot
once booted up
make sure your still inside adb command prompt
11. type this "adb shell"
12. type this "su"
13. type this "id"
should show this output
"uid=0(root) gid=0(root) context=u:r:shell:s0"
then to set permissive
14. type this "setenforce 0"
15. type this "getenforce"
output "Permissive"
16. to test if mount system rw while still root type "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
if for some reason u cant write to system u can try
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do once u have perm root do this to restore recovery
type this inside of adb shell dd of=recovery if=/sdcard/recovery.img
hit the thanks button if my post was helpful
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseA...ts/KzgyHLgVhwo
also dont forget to hit the thank you button if this post was helpful
ota file attached may help some that are bricked
to remove annoying lock screen with ads
open king root then touch the 3 dots goto settings
then touch accelerate charging turn switch it off
then that annoying part is gone if purify is installed remove it and everything should be good.

Awesome, do you know if this will work on the ZTE Warp Elite?

everyone get their phone rooted ok

Well 2 things...
1: can you lost a guide on how you did those steps?
2: if I already did a software update for my phone, would that affect my chances of getting my phone permanently rooted?

those steps are the guide if you dont know what adb is or how to use it or king root then u could look both those up for guides on the 2. after u know how to use both its pretty much gain temp root have adb open then paste commands make sure they say the same as the guide for outputs follow all steps and should be good. unless they released an update that make it android n im sure it will work. once i send in these 2 dead phones to get repaired ill make a video guide of the steps in guide. as i dont know if it will break root to try redo all the steps to show everything i did.i will see if i can automate the process with batch script. aka filename.bat

updated the guide lil for if anyone who is lil new to adb etc

I've used adb when dealing with moto phones. But this has me confused as to what to actually put in cmd prompt. Either way you're a God among us. I'm going to attempt and see if I can get it working. Thank you for your work sir. Hope to see a batch script some day.

added batch script

No errors so far. Just a little sluggish.

Stevenbew said:
No errors so far. Just a little sluggish.
Click to expand...
Click to collapse
um no errors from what and whats sluggish and for anyone who asks i used the lastest kingroot version

Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.

Stevenbew said:
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Click to expand...
Click to collapse
did u use script or manual

madvane20 said:
did u use script or manual
Click to expand...
Click to collapse
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.

Stevenbew said:
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Click to expand...
Click to collapse
ok i only asked cause im already rooted so i couldnt really test the script but it should work and at the end it tells what commands to type in to test. looks like i may need to edit the guide lil bit later and edit my script

I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.

Heartseed said:
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Click to expand...
Click to collapse
use to batch script after u get temp root it will do most of the work for you and guide u through the rest

I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!

Pirela said:
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Click to expand...
Click to collapse
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package

madvane20 said:
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
Click to expand...
Click to collapse
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way

Pirela said:
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Click to expand...
Click to collapse
connect to pc open adb shell run king root while its trying to root keep typing su in adb shell tell it says root. or til it doesnt give u the error saying no su then proceed with guide see if that works