yashsingh1/xdaforums huggingface dataset:
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
[Theme Chooser] [CM7] Blue Toggles With Transparent Status Bar & JB Header 14/03/14

Status Bar With Blue Toggles JB Header Brightness Slider And Transparent Theme For CM7​

This Mod Is For Any CM7 Only

If You Require The Stock Version Go Here

If You Require The AOSP Version Go Here

My Other CM7 Theme Can Be Found - Here​

Take Note Of The Following

Anyone is free to use and develop this with the following conditions

you do not mirror the download link or add any ads to my download link on blog sites

post the link to this thread if you blog this

credit me

Install Instructions

Step 1 - Flash Status Bar

Go into CWM

Make A Nandroid Backup In Case Your Status Bar Goes Walkies For Some Strange Reason

Mount System Data Cache Sdcard (on bieltv.3 kernel unmount and remount system at least twice)

Install Zip From SD

Select Zip

Restart

Note - If you still cant work out how to flash it on bieltv.3 kernel just flash percys kernel and then flash the zip then flash back to bieltv.3 kernel

Step 2 - Set Blue Toggle Theme

Goto Phone Settings

Select ADWLauncher

System Preferences

Disable (untick) Wallpaper Hack

Press home key

Open dock

Open Theme Chooser app

Select MarcusSmithBlueTheme

Select Apply

Select Apply Anyway

Done - Your status bar now has the blue toggles and is now transparent

Note if you dont want a transparent statusbar just re-enable wallpaper hack in adw launcher settings

Changelog

V1

Initial release

Added/edited smali/xml files to SystemUI.apk

Added brightness slider

Added transparency

V2

Added JB header

Changed some icons

Added some polish to finish it off

V2.1

Resigned SystemUI.apk with a platform key - now fully works with bieltv.3 rom/kernel

For extra toggles

Goto phone settings -> CyanogenMod settings -> Interface -> Notification power widget -> Widget buttons

Select what you want

Downloads

For Galaxy Y GT-S5360 - Blue Toggle Transparent Theme V2.1

Do Not Post Things Like

Will this work on xyz rom - This is for any CM7 Only!

Will this work on stock rom or AOSP - NO!! See link at the top of the thread for stock/AOSP version

To make it clear - this is for any CM7 only!

Credits

UOT Kitchen

evanlocked

Achep

Z25

petrukgrinder
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
AOSP version availablle see first post
[Galaxy Y GT-S5360 Themes and Apps] puli112:
i tried the same but that bricked my phone after flashing the zip and faced status bar FC
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
My theme above will work on any cm7 rom - dont use it on AOSP
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
anyone tried out my theme yet?

if you wanna use any theme chooser theme you find on xda or the play store that has a transparent status bar you will need to patch your systemui.apk first else the theme will work but wont be transparent - you can either flash my zip in the theme above (you can delete the theme from the zip if you wish and just keep the patched systemui.apk) or you can patch your own systemui.apk by following my guide from the link below and follow method 2

http://xdaforums.com/showthread.php?t=2204389
[Galaxy Y GT-S5360 Themes and Apps] Mranggapo:
Can this be used on cm7 by bieltv ?
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
yes should work but I never really finished this theme off

if you give me an hour or so I can make improvements to it and re-release it

you can check out this one I did too which I did finish and Im using it on bieltv cm

http://xdaforums.com/showthread.php?p=49468255
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
just updated this - added some polish to make it look a little better
[Galaxy Y GT-S5360 Themes and Apps] TheFixItMan:
added version 2.1

should all be working fine now with bieltv.3 rom/kernel
[Galaxy Y GT-S5360 Themes and Apps] Puru007:
it worked ... :good:
[HTC One Mini] Zarboz:
Would like to get in touch with a One mini owner who would let me SSH into his machine to see if we can dump a boot.img and get recovery going and developement started for this device
[HTC One Mini] Busted.:
What exactly you want or need to do..?

I own the Mini, and I want to contribute and help to get the M4 rooted.

As long as I dont need to test anything Im ready to help.

Feel free to message me on Skype, Skypename sent vie PM. :)
[HTC One Mini] nelvinchi:
Hi, Flyhalf205 suggested I contact you re getting dev started on the one mini..... Tried to pm you but I have less than ten posts so am blocked sending you pm's....

I have the mini and would be more than happy to assist in any way I can..... Pm me! Thanks!
[HTC One Mini] Zarboz:
unable to PM you due to low post count :P

get at me on gmail

its my username [MENTION=652814]gmail[/MENTION].com
[HTC One Mini] Flyhalf205:
[MENTION=3903113]nelvinchi[/MENTION] have you gtalked with zarboz yet? If not. Just reply and i'll PM you with some things to try to pull
[HTC One Mini] epolus:
got mine...and just bricket by flashing a kernel :(
[HTC One Mini] iconspiracy:
Really? Soft or hard bricked ?

HTC One Mini

S-OFF
[HTC One Mini] humzaahmed155:
Most likely soft, fast boot flash another kernel
[Samsung Galaxy S Blaze 4G] MrPapito429:
I know that on about every ROM there is, the H logo replaces the 4g logo, is there a way to change the text so that I can get the 4g text back.
[Samsung Galaxy S Blaze 4G] Somcom3X:
but it is not 4g. it is hspa+ or 3.5g

Anyways, go into your apk with root explorer and change the icons name to the 4g ones.
[Samsung Galaxy S Blaze 4G] MrPapito429:
What apk, do I modify
[Samsung Galaxy S Blaze 4G] Somcom3X:
System.ui be sure to backup before and set permissions.
[Samsung Galaxy S Blaze 4G] jparnell8839:
I think I've only hit 4G on the blaze once :P it was when i was in Atlanta. Everywhere else it's HSPA+ except while I'm at work, it's *shudder* edge
[Samsung Galaxy S Blaze 4G] MrPapito429:
And what do I change in the system ui
[Samsung Galaxy S Blaze 4G] MrPapito429:
Can I do all this from my phone
[Samsung Galaxy S Blaze 4G] Somcom3X:
on touchwiz I always have "4g"

screenshots.

You must rename it to systemui.zip and do it from a computer.

Make sure you do it for connected and fully_connected

No
[Samsung Galaxy S Blaze 4G] jparnell8839:
Because touchwiz is cake.

And Samsung is GLaDOS.

And the cake is a lie
[Samsung Galaxy S Blaze 4G] Somcom3X:
I see what you did there :p portal fan ?
[Samsung Galaxy S Blaze 4G] jparnell8839:
I haven't fallen so hard for a game since the original halo
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Can someone create/direct me towards a step by step for this , I would like to do this but I'm paranoid , and I'd feel more comfortable following a step by step :)

---------- Post added at 02:18 AM ---------- Previous post was at 02:07 AM ----------

Original Halo was ... amazing! :)
[Samsung Galaxy S Blaze 4G] Somcom3X:
I will do it for you I just need systemui.apk for ROM.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Just to be sure, that file is under /system/app right?. Can I upload .apk files here?.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
I finally got into the APK, I thought that H+ was 4G but when I saw a 4G icon in systemui,apk I was confused. Then I read your first post :D lol so I'll just leave it like it is.

Another question, if H+ is 3.5G what's "H"?
[Samsung Galaxy S Blaze 4G] Somcom3X:
I believe h is 3g. I think T-Mobile chooses what to show.
[Samsung Galaxy S Blaze 4G] MrPapito429:
How do I upload the apk to here, or what website can I use for free to upload
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
1. Click Post Reply.

2. Scroll down to "Additional Options" and click "Manage Attachments" (See Attachment 1)

3. A window should pop up, as you can see by the highlights you can upload .apk files as long as it is under 8 megabytes (See Attachment 2)

4. Click "Choose File" and select the .apk file

5. Make sure you press upload! (I forget this often! :P)

That's it! Finish off the post as you normally would and the .apk file will be attached :)

I just want to reinforce the fact that you should make sure that you backup systemui.apk, so if something goes wrong you'll have it!

(I accidentally deleted the only copy of mine earlier today :rolleyes: lol )

--edit--

I didn't realize how low quality the screenshots were, sorry about that! Hopefully you can still get an idea :)
[Samsung Galaxy S Blaze 4G] Romman0:
H is hspa, H+ is hspa+ both called 3.5g or 4g by some. As seen in the settings / about phone / signal as hspa:10 and + is 15.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Oh. Thank You! :)
[Samsung Galaxy S Blaze 4G] Somcom3X:
But one is faster than the other.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Cyanogenmod FAQ says H+ is 4G, so whether that's true or not I'll just pretend it's 4G. Lol
[Samsung Galaxy S Blaze 4G] tommyboy8125:
Nope H+ is fake 4G, it's really 3.5G but since it's fast the carriers market it as 4G.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
No! It can be 4G, who are you to tell someone they can't be who hey want to be? Lol ;)
[HTC Droid DNA] DarkBeer:
I use Endomondo to track my bike rides. When I was stock, the GPS was very reliable in that app. Since I've rooted, I've tried ViperDNA and Carbon. In Viper, the elevation is all out of whack. I ride in mostly flat areas, and it shows me going up and down 600 foot elevation changes throughout the ride. Carbon was closer to stock in GPS performance.

Is the difference in GPS performance related to the way the ROM communicates with the GPS, or are there specific files for the GPS that could be modified? Wondering if there is a GPS related file I could take out of one ROM to use in another?
[HTC One S] crakarjax:
UPDATE:

Keeping the top here current for the tldr problem:

- My setup -- T-mo HTC one S with original hboot 2.15.0000 picked from that link, S-On, no SuperCID, and I can unlock the bootloader. I have TWRP 2.3.3.0 installed.

- I can run the T-Mo release_309489 RUU and get a working OS, *except* that my USB port keeps connecting/disconnecting

- Flashing the latest CM10 nightly results in spinning CM logo but no successful boot. It seems as if flashing boot.img did not take, although I got no errors

- I cannot do SuperCID anymore, it seems as though the modified partition is not writable anymore (due to hboot?)

--- Old stuff ---

So I noticed the latest nightly and decided to flash it, and then an error occurred telling me I needed a newer hboot. I installed 2.15.0000 and then the rom and boot.img extracted from rom, but all I got was a bootloop, no CM logo at all. Tried different roms to no avail. Grappled with sdcard unreadable so I have flashed stock recovery to fix that a few times now. I'm kind of at a dead end and feel like I tried everything I could think of. Any help is appreciated!

I can fastboot fine but adb is very spotty, as my computer keeps connecting/disconnecting to my phone, preventing any real use of adb. It seems that when I write to the sdcard, I get immediately disconnected from the phone almost as if the sdcard write is crashing the connection somehow.

I have tried using CWM recovery as well as TWRP 2.6 and 2.4.4.
[HTC One S] khan.orak:
Try TWRP 2.3.3.0
[HTC One S] crakarjax:
Thanks, I will try that. Magical version or something?

I did burn some midnight oil last night and got the latest tmo RUU that I could find to install (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe). By the way, there is an OTA update available, any reason I should take it?

I un-superCID'd, relocked bootloader etc and I am guessing that this one installed because the hboot is 2.15.0000? Anyway, I am wondering what I might have done wrong to cause this in the first place. I still have very odd behavior when USB is hooked up, the connection continuously connects and then drops when in the stock ROM. Could that be an hboot issue?
[HTC One S] khan.orak:
Ok that's great.

-RUU is a one step solution to many problems so that's why it worked.

- the OTA available is for T-Mob only. You may install it if you don't have SuperCID; it contains some sort of battery fix.

- Odd USB behavior could be due to a variety of reasons. For instance:

1. Faulty Cable. Check other cables.

2. Incomplete driver installation. Might try with with HTC Sync Manager.

3. Try enabling USB debugging.

- I can't really seem to establish a relation between HBOOT and USB not working, but then I might be having insufficient knowledge.

Best of luck!

---------- Post added at 03:14 AM ---------- Previous post was at 03:10 AM ----------

And yes, 2.3.3.0 indeed is magical for it has shown wonders where other versions have failed. :p
[HTC One S] crakarjax:
I have tried TWRP 2.3.3.0 but that did not seem to help. My cable is good, I connected my wife's One S to my computer and it had no issues. iirc, I do not have USB issues in TWRP anymore though... so perhaps 2.3.3.0 did help in that regard. The connection works fine with fastboot so I am pretty sure that there is no hardware issue here.

I was going to try to get S-Off but couldn't get SuperCID to stick; it seems that the RUU I installed write protected that partition because I could do SuperCID before I applied the factory RUU.

I am still able to go back to stock with the factory RUU if I apply the factory recovery and relock.

My hboot now says " Tampered / Relocked / Security Warning " if that means anything.

And finally, I am able to flash CM10 (nightly 8-04) but when I did that I got a boot hang at the spinning CM logo. I did fastboot flash the boot.img from that ROM, but it seems to behave as if the boot.img is still incorrect. I suspect that as with SuperCID, something is locking down my ability to write the correct boot.img. Is there any way to pull the boot.img off after flashing to verify that it was correctly written?

Since I have not been able to get a custom ROM working since I updated to hboot 2.15.0000, I have to think that the hboot is the culprit. At the same time, I don't see why a version of CM10 would have been released that required 2.15.0000 if it had not been tested. It is possible I suppose that I have installed a bogus hboot, as I grabbed it from someone's post (http://xdaforums.com/showthread.php?p=39216236#post39216236).
[HTC One S] khan.orak:
That's a modded HBOOT. Maybe that is the cause of the problems.

You should flash the original HBOOT and reflash OS etc.
[HTC One S] crakarjax:
The link has both modded and original hboots -- I flashed the original 2.15.0000 version. I'm going to look into downgrading my hboot, but then I won't be able to run the latest kernel so that isn't exactly ideal. It might allow me to run the latest RUU though and get a fresh hboot on there to see if the one I downloaded was borked.
[HTC One S] khan.orak:
That's a fine remedy.
[HTC One S] crakarjax:
Hmm, so I plugged my phone into USB on my work laptop and the connection dropping doesn't happen. The drivers aren't installed though, so I will have to try this out at home with my other computers.
[HTC One S] crakarjax:
I finally got S-Off using moonshine for linux -- Unlocked my bootloader, installed android-tools for Centos 6 (I was using x64 but installed the 32 bit package), and ran moonshine. I guess moonshine installed a modded hboot in the process. Installed TWRP 2.3.3.0 afterwards, and then the latest CM10.

*hopefully* since I am S-Off I won't have any sdcard corruption issues or otherwise after future updates. Thanks for the advice and hopefully if someone runs into this situation, they can jump straight to moonshine on linux as a solution.

HOWEVER, CM10 nightly still gets stuck at the cm spinning logo. I'll try an older version (the one I was using prior to this fiasco) and see if it works.

EDIT: the nightly I was using (20130312) isn't available?!? So I guess I will try another.... ok 3-04 nightly works fine, and the boot.img appears to have been correctly installed.
[HTC One S] crakarjax:
Ok, installed a 3.0 kernel nightly and it does work! So, for some reason the 3.4 kernel versions aren't booting. Not sure where to go from here, as moonshine installed a different hboot in the process and still no love.
[HTC One S] crakarjax:
Installed a different 3.4 kernel ROM (Illusion) and it works! I guess the problem lies with CM10.1.
[Samsung Galaxy Nexus] cuboc:
beats audio hello everyone, I've been already some time looking for a mod beatsaudio or something like that to GNX, but so far have not found anything already tried a lib's and files from htc one google edition 4.3, but not got nothing, I no equalizer, prays without so someone already got something you want to share?
[Samsung Galaxy Nexus] cupfulloflol:
http://xdaforums.com/showthread.php?t=1748803
[Samsung Galaxy Nexus] cuboc:
I already tested this but still not stable that nothing before had megabeatsaudiov3 and always found the simplest and best. but lately with the 4.3 update left you can use. Yesterday we checked out 4.3 for htc one and S3, there is some way to get the beats audio out?
[Samsung Galaxy Nexus] jthrasher47:
Here you go man this should work just make sure you choose what exactly you're build is off of an aroma this works perfectly on all my devices if it hangs at 88 percent in recovery don't worry just reboot your phone like normal and it will be OK can make sure you pick awesome beats in music effects and settings

http://xdaforums.com/showthread.php?t=1728391
[MDA II, XDA II, 2060 General] kulapica:
I got in 1.60WWE but after upgrading to 1.66WWE it disappeared.

Anyone know this?

Thank guys;)
[MDA II, XDA II, 2060 General] bolasz:
Do you mean your today screen layout?
[MDA II, XDA II, 2060 General] kulapica:
yes, I am looking for it.
[MDA II, XDA II, 2060 General] cruisin-thru:
Looks like O2 active front end.
[MDA II, XDA II, 2060 General] Gazzeh:
Correct

Yes this program is

Mobile Solutions SRL O2ActiveUI

not sure where you get it from though, maybe the os website
[Xperia Arc Q&A, Help & Troubleshooting] trinimike100:
I managed to install flashtool drivers on w8 64bit, but my pc does not recognize the arc s in fastboot mode. See attatchments

How to fix?

I installed drivers using this http://xdaforums.com/showthread.php?t=2044804
[Xperia Arc Q&A, Help & Troubleshooting] Kepta Duona:
Did You selected to install fastboot, flashmode and Xperia Arc drivers in "Flashtool Drivers Setup"? (C:\Flashtool\drivers\Flashtool-drivers.exe)
[Xperia Arc Q&A, Help & Troubleshooting] kzizo:
Maybe bad USB cable?

Maybe bad USB cable?
[Xperia Arc Q&A, Help & Troubleshooting] Claxc Designs:
Yes, you have to install the driver first as [MENTION=1835024]duon[/MENTION]a said :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] joedajoester:
Hi all, sorry if this is in the wrong thread, please move it if is. I tried rooting my SCH-1935, but i couldnt find a thread for that model. When i was rooting it as it had the android logo and the loading screen right after the rooting process was almost done it bought be to stock recovery before it was finished and had some red text and now my phone is basically boot looping. Can anyone shed some light on this?

EDIT* This worked for me, it took a while to boot, just don't pull the battery lol. :D
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] JJEgan:
Wrong thread its in the wrong forum
[RAZR HD Q&A, Help & Troubleshooting] FLAcco:
Hello everyone, I was reading this post http://xdaforums.com/showthread.php?t=2154264

I would like to know if anyone knows what would be the corresponding values ​​for our razr HD.

i try with the same values ​​and only obtained a bootloop
[Android Q&A, Help & Troubleshooting] aknor:
Greetings XDA Forum,

This is a general question that should be in everyone's mind who might want to root a phone or tablet or any Android or other mobile OS device:

Is this root exploit or bootloader going to be spyware and collect any and all data of mine (login credentials, keylog my every character, account/bank numbers, identity information, use your evil imagination)?

So, I searched this forum for key words like "trust root" "secure root" "security" and found nothing related to this topic.

So, how am I to trust ANY of the root exploits or bootloaders created and posted to this forum for ANY device?

Have any of the developers developed an audit process using firewall rules to ensure that a posted root exploit or bootloader does not attempt to keylog, report captured information to some obscure IP address (thief/hacker's machine of course)?

Do any of these root exploits or bootloaders or custom unofficial builds of entire android (like Cyanogenmod and the 3rd party variants) get Security Audited?

How am I to believe that the whole lot of you making the root exploits and bootloaders are not a big community of identity thieves and financial fraudsters?

Am I just supposed to trust you?

Answer me that, folks ;)

Aknor
[Android Q&A, Help & Troubleshooting] demkantor:
I've never seen any root exploit that did as you say, if your concerned pick apart the code and look for this, I've never seen anything of the like

As for bootloaders, there are very few devs that actually make or tweak bootloaders as a misstep will nearly for certain result in a brick. Almost every bootloader you will find is made by the OEM, if its not, again feel free to pull apart the code and look for an issue, but I doubt it as this is far more advanced than most will ever become

As for custom ROMs, well this is the most possible out of all your worries, but again most ROM chefs here are not capable of inserting malicious code, and if its an official build of a major team (cm, aokp, slim, etc) you are damn near 100% certain there is no issue, as for random ports made in the former USSR by KGB spies, well just don't flash their ROM and you'll be fine

But of course no one is forcing you to root your phone, flash their bootloader, or download their ROM, so if youre the paranoid type just get an iPhone, at least they're upfront about most of their evil ways
[Android Q&A, Help & Troubleshooting] aknor:
Okay, I can see that on the boot loaders, but more than just a few make the root exploits and custom builds of cyanogen or android for many, many devices. So, how am I to pick apart the code of these projects when they do not provide the source code for the builds? How would I even trust those builds after they are built? They could slip some malicious code in that they intentionally do not show in the public repository for the code and no one would ever know.

Sure this sounds very paranoid, but no one has really answered how or if at all any of these builds of unofficial android or cyanogenmod or the root exploits or the bootloaders can/would be tested for malicious code.

Think of it, something as small and innocuous as a keylogger with a simple, non threatening name, and all the while, it logs your every username and password, credit card number, 3-digit security code, bank account numbers, anything. How bad would that be, eh?

Any you're not concerned these builds/exploits are not somehow security audited and we're all just supposed to trust them like blind sheep?

As more and more of these get built, it's only a matter of time before someone slips something like this into their build to take advantage of all those people who want to root their phone/tablet, or put an unofficial build of android on their device. Shame on that person who does it, of course, but to think somehow we could have audited the software and found out as a matter of course?

-- Aknor