yashsingh1/xdaforums huggingface dataset:
[Moto X Themes and Apps] tiaoalvino:
BASED ON THE WORKS OF:

[MENTION=2439340]chaoslimits[/MENTION] : http://xdaforums.com/showthread.php?t=2561560 :good:

[MENTION=5103769]kuz142[/MENTION] : http://xdaforums.com/showthread.php?t=2584351 :good:

This mod removes the icons of the mobile network type used by Motorola, which take up too much space in the status bar, to use the default icons used by AOSP, based on the E icon for 2G, H icon for 3G and the LTE icon for 4G. Also, these icons are no longer displayed when connected to a Wi-Fi network.

WHAT WAS MADE:

Pulled out the framework-res.apk file from /system/framework/ folder, and the SystemUI.apk and SystemUI.odex files from /system/priv-app/ folder to my computer.

Decompiled the SystemUI.apk using Android Multitool (thanks to [MENTION=4642185]Flextrick[/MENTION]).

I have made the same changes that [MENTION=2439340]chaoslimits[/MENTION] did, to use the AOSP's mobile network type icons instead of the Motorola's ones.

Changed the res/values/bools.xml line: <bool name="config_show4GForLTE">true</bool>, from true to false, to show the LTE icon instead of 4G.

Replaced the icons of signal strength of the mobile network used by the AOSP with the icons that are used by Motorola at the res/drawable-xhdpi folder. These icons are available at the attached file drawable-xhdpi.zip.

Changed all the lines of the res/values/styles.xml that contains: <item name="android:textAllCaps">false</item>, from false to true, to use capital letters at the quick settings and notifications panels like AOSP did.

Recompiled the SystemUI.apk using Android Multitool instructions.

BEFORE:

AFTER:

REQUIREMENTS:

Android 4.4.2 Brazilian Retail (161.44.26.ghost_row.Brasil.en.BR);

Root;

A custom recovery (CWM or TWRP), if you want to use the flashable zips.

RECOVERY (UN)INSTALLATION:

Flash the SystemUI-AOSP.zip file, if you want to install, or the SystemUI-AOSP-Restore.zip file, if you want to uninstall;

Reboot.

MANUAL (UN)INSTALLATION:

Unzip and find at the /system/priv-app/ folder the SystemUI.apk from the SystemUI-AOSP.zip file, if you want to install, or the SystemUI-AOSP-Restore.zip file, if you want to uninstall;

Copy this SystemUI.apk to the /system folder of your phone, and set its permissions for rw- r-- r-- (equivalent to chmod 644);

Move the file for /system/priv-app folder of your phone, overwriting the existing one;

Reboot.
[Moto X Themes and Apps] themcfly:
really interested in this one, i'm trying to build the closest look to stock as possible on my European XT1052, will this work on it? It has the exactly same icons you have out of the box.

Thanks in advance.
[Moto X Themes and Apps] tiaoalvino:
Hi! I believe that if you use the file attached at the OP, it will not work. :(

But, you can follow the instructions of the WHAT WAS MADE section, and I believe you can obtain the same results with the SystemUI.apk of your device. :)

Sorry for my bad english. :good:
[Moto X Themes and Apps] Kittiesoncrack:
I tried this on my Sprint Moto x using the instructions you have in OP, and My LTE icon is offset. It isnt on top of the Signal bars, its to the right

edit: to the left, not the right

EDIT 2: i am not sure if this applies to other carriers but if you're on sprint, dont replace the drawable xhdi folder, It turns the signal bars blue. and also in bools there is a line called "<bool name="config_enable_carrier_wide_icons">true</bool>" change true to false and the large lte icon will be fixed

Edit 3: spoke too soon, drawable xhdi folder does not turn the icons blue. something else triggers it
[Moto X Themes and Apps] helioalmeida:
"The process com.android.systemui stoped" please help!!!! What can i do to fix?
[General Questions and Answers] Leafs99:
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying:) as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
[General Questions and Answers] turffe:
Sorry for late answer. But, yes you'll need Motorola factory cable to bypass battery check.

1. You'll need to reflash stock JB with RSD.

2. Then reboot your phone (screen turns black) you'll need to press both vol buttons, bootmenu will appear.

3. Then with voldown choose bp tool & select it with volup. You'll boot to android.

4. Then you'll need to root your phone with Razr rooting stuff.

5. Then rooting program reboot your phone (screen turns black) you'll need press both vol buttons & choose with vol down bp tools & select with vol up.

6. Then you'll be rooted install Boot Menu Manager from Play Store. BMM have 2ndinit so you wont need to start phone with BP tool anymore.

To try fix CustomerID error completely you should refer to this post - http://xdaforums.com/showthread.php?t=2406867
[General Questions and Answers] Suraido:
Actually, battery IS removable, albeit u'll need a very smalle torx screwdriver (m4 or m5 if my memory is correct). But that still won't do much good since even if it's out, there no easy way to recharge it. Although if you have a scrap battery just to get the connector and have some soldering skills, you can redneck up yourself some AA batteries in a project battery holder and solder the leads to the scrapped battery's connector to at least pass the batt check. As for the softbrick though, i'm used to motorola phones yet, i've mostly fiddled with soft and hard bricked samsungs and my own LG optimus g E971, so i might not be much help on that side YET. But i DO have a razr xt885 here that belonged to a friend of mine which had the great idea of trying to fit his microSIM in there cause he was too eager to get the phone started and didn't wanna wait for me to have time to check everything out and unlock the carrier on the phone so he could use it... So now the SIM holder on the board is dead cause he ripped out the metal contacts trying to pull out his microSIM from there........ Phone still turns on though and software has not been modified in any way and everything works except for the SIM holder, so if you need backups or files from a working model, i can definetly help you there. Only thing i don't have anymore is the stock USB wire cause that one got hacked up later on to be used as a USB jig... but the battery and software are all good and i have plenty of microUSB wires to connect phones here. Plus i also live in the province just east of you :P So it's still a few hours drive but if all else fails and you feel like a roadtrip to Quebec, i'd be happy to help in any way possible :) Just let me know if you need anything :)
[T-Mobile Samsung Galaxy Note II] volcs0:
I've read through all the relevant threads. I suspect I know the answer to this question, but I wanted to ask to make sure.

I picked up a new T-Mo Note 2 yesterday, was on 4.1. (without reading first) I did the OTA to 4.3.

I would like to keep the stock ROM but have root access.

I would like to have the option to install other ROMs, if needed.

I don't care about losing the data on the phone right now (it is new...)

I don't care about the warranty.

I don't need to unlock (right now) - but am going to Europe in a few months and will probably want to then.

I don't know if I need to care about Knox.

Should I go through mrRobinson's process?

http://xdaforums.com/showthread.php?t=1975560

using V2

http://xdaforums.com/showpost.php?p=48414379&postcount=446

Thank you for the information. I know the answers lie in the threads here, and I've tried to sort it out. I just want to be clear.

Thanks.
[T-Mobile Samsung Galaxy Note II] Double0EK:
Yes. I think that's the easiest method to root without tripping the Knox Binary Counter. (But I wouldnt know because I'm still on 4.1.2 Rooted and Rom'd)
[T-Mobile Samsung Galaxy Note II] ciphercodes:
I think rooting via this method trips the counter. Anyone on Mr Robinsons rom please confirm if Knox counter has tripped ?
[T-Mobile Samsung Galaxy Note II] volcs0:
Any thoughts? Should I Just wait a few weeks?
[T-Mobile Samsung Galaxy Note II] ciphercodes:
If you do not care about warranty like you said then you can flash Mr Robinsons v2 rom as its pre-rooted and is Knox-free.
[T-Mobile Samsung Galaxy Note II] Tiberius Jonez:
I used Mr. Robinson's

Pretty sure it trips the counter - I had already tripped it...

First of all, if you don't care about the warranty, then all that really matters is this...

It is a great rom for fixing problems you may encounter after rooting incorrectly and establishing a "fresh root". I use it whenever I go to a new rom now. It has never failed to make things go smoother. Just used it to upgrade to the new ezKAT rom. Now I have Note 3 and S5 features on my Note 2, and it works beautifully. But I had nothing but problems with the installation until I went to my old fail-safe of flashing Mr. Robinson first and then dirty-flashing ezKAT over it. Voila - perfection!:laugh::good:

I now consider Mr. Robinson's rom as basic as a screwdriver in my rooting tool box. And it's especially useful for noobs.
[Networking] drakpzone:
just alpha, but already ROCKING!!! I tried this port on my jasjar with my openvpn installation. It simply rocks and it's imho the definitive kick to ipsec/l2tp weird ass.

http://www.ziggurat29.com/OVPNPPCAlpha/OVPNPPCAlpha.htm

Also as a forum... check it out and contribute... openvpn is great... openvpn on your pocket is amazing!!!

Bye

Drakpz
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] uksrevivor:
Hello all.

I have updated my samsung galaxy ace GT-S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM.

I have had several problems but they all seem to have sorted themselfs out apart from a few glitches as follows

im using cooperfix v6.0.4.5 recovery and i have •Android 4.4.2 CyanogenMod 11 ROM for Galaxy Ace installed on card. I am unable to revert to CM7.2_JellyBreadv1_GT-S5830 using cooperfix v6.0.4.5 recovery as it aborts the instalation with a red triangle in the belly of the android bot and text.all the links i used to do it originly are dead links hotfile and another dead link. The only zip file it will install is the CM11 one.

Factory reset takes me back to cyanagemod boot screen and then the set up screen so its defaulting to CM11 and then in set up screen its imposible to set up gmail account and google play e.t.c. All the cooperfix files on here for older versions are dead links because of some federal law?

Wifi is perfect and connected straight away and the browser app works perfect connecting to the internet everytime.

so how can i get google play back again and working so i can install app and use it and if not possible to resync to google play how could i revert back to an older version. I really do prefer these custom roms but im struggling. Any help will always be appreciated and will always involve a thank you from me.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] -BRK-:
install cwm5 to install roms prior to cm11.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] uksrevivor:
Nice one thank you I have reverted back to gingerbread 2.3.6 via flashing cooper v1 and the md5 file in ODIN and its worked fine im running original stock rom with no problems. I have rerooted the phoneand installed CWM 5 recovery and looking into more stable custom roms as 11 is still in early stages.

Some of the problems i had were no camera/ no google play store / no connection / random bootloops/ alarm didnt switch off, and this really random one that the phone would ring but there was no way of answering it lol:eek: An exellent rom with brilliant potential and one i will use again but for now im experimenting with earlier versions that are more stable.:)

many thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] devilsdouble:
I think everyone is familiar with the tick tick sound when you increase or decrease your phone's volume by using the volume keys. Suddenly from yesterday there's no volume while I'm changing volume! I've checked Wanam Xposed sound option, and that option (disable volume control sound) is unchecked, still!

What could be the reason? I'm on Adam latest, with stock MK9 ROM. Any help will be appreciated.

Thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] devilsdouble:
Anyone?
[T-Mobile Samsung Galaxy S 4] xgreenlanternox:
Hello!

Hope all is well. First I wanted to say i'm sorry if this is a duplicate - I searched and saw similar questions, but not exactly the same as mine :).

I own a T-Mobile Samsung Galaxy S4 M919 and I had rooted it and installed a custom rom. Im having hardware problems and need to return it for repairs, so I reflashed the stock system and recovery, used triangle away to remove the binary counter, and hard reset the phone. In my download mode, my phones reads "Current Binary: Samsung Official" and "System Status: Official", as well as reads official on the device status in android so all went well.

My question is this - I got notification of a push update that is going to install Android 4.3, and apparently this "KNOX" software that I do no seem to currently have. My concern with this is that i'm reading that there is a flag with this KNOX software that is easily tripped, and once done, the download mode reads "KNOX WARRANTY VOID 0x1", which therefore voids warranties. Since I was able to get everything back to completely normal, I dont want to run any more risks since my phone really needs repairs very badly. Should I bypass this update? Though my phone is 100% official now, if I do the update, will the KNOX software catch that I had rooted/custom rom'd the phone in the past and trigger the flag automatically, or do you first have to have the update installed BEFORE you try to root it for the flag to trip? Everything is 100% stock now so when I download the update, I don't think there is anything present that would trigger anything, but I don't even have this "KNOX WARRANTY VOID" line in my download mode yet so I am wondering if I am just better off being safe than sorry?

Thanks!
[T-Mobile Samsung Galaxy S 4] serio22:
It won't be tripped until you trip it so you will be OK if you update it to 4.3, But I highly advice against doing so.. Just leave it as is, and return it like that
[T-Mobile Samsung Galaxy S 4] Misterjunky:
If you are having hardware issues and are returning the phone and

your phone is 100% stock without KNOX right now then why in

the world would you want to take chances with OTA updates or

any other updates.

If it was me I would have already taken/shipped the phone back for

repair or exchange instead of worrying about OTA updates.

Good luck!
[T-Mobile Samsung Galaxy S 4] xgreenlanternox:
Thanks for the advice! Download mode would be the only location of that "KNOX WARRANTY VOID" flag right? If it's not there, then as long as it states both Samsung Official and Official in download mode I should be good ya think?

Thanks!
[T-Mobile Samsung Galaxy S 4] serio22:
Yes.. It will also show a message at boot
[T-Mobile Samsung Galaxy S 4] xgreenlanternox:
Awesome yep - no boot message I see either - boots just like it did the day I bought it. So I am pretty sure I have the firmware before KNOX came out - It has been rooted since the summer so I probably luckily bypassed the official update with KNOX :)

Thanks to all for your information! Im gonna stay away from the new firmware just to be safe until i get the phone back from warranty!
[T-Mobile Samsung Galaxy S 4] xgreenlanternox:
Hmm - things got even more interesting. So it seems when i reset everything back to stock as mentioned above, the screen flickering issues have now gone away and I am not seeming to replicate them in any way at all. Does this sound familiar to anyone? I was using a version of Wanamlite ROM before i reset everything. I am wondering if it was just the ROM causing the screen flicker and not a hardware defect.
[T-Mobile Samsung Galaxy S 4] serio22:
It could have been
[Xperia Z Q&A, Help & Troubleshooting] pepeace:
Hi,

I have serious troubles with my xperia Z phone and i would be very happy if someone could help me. So this is my story:

After i bought my new xperia Z and had it for several months i wanted more of it so i rooted it. then i found an backup app for rooted phones (Titanium Backup). So i backed up my whole phones files with Titanium Backup and exerything worked properly. After a time the new software was out and i was asked to update the existing software. Whithout thinking about it a lot i did so and at first nothing happend. After a while i rebooted it once and the phone and contact icon disappeared. So i opened Titanium Backup and restored my loses. Unfortunately i had to do this each and every time i rebooted my phone and tried uninstalling and reinstalling Titanium Backup a few times but nothing changed so i thought it would stop with time. Then Jelly Bean 4.2.2 came out and it asked me again if i wanted to update my software and so i did. After updating the icons disappeared again and when i tried to restore these again (from Titanium Backup) it just loaded forever and never restored them and i also cant restore anything else from my backup. So i thought that maybe this ****y app just kept updating my backed up files without asking me and that the newer firmwares doesnt support the backuped files from another firmware so it stucked. What can i do now? Should i downgrade me phone two updates down then restore everything, update and make a new backup or something like this?

Thank you and i hope somebody can follow my problem and have an idea how to fix the hole problemm....:crying:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ianjojo:
Hello, I can't seem to find the perfect answer in another thread.. I'm on a google experience 4.4.2 rom, with the MK6 modem and i'd really like to unlock my phone for use on a different carrier. i tried flashing an older modem but no luck.. is there a way i can do this myself without going into a shop and paying $40?
[T-Mobile, Samsung Galaxy SIII] Kamau54:
I am running my S3 on TMO, with 4.3 booloader & latest modem. I was also running a 4.3.2 TW rom.

This morning, I decided to wipe the rom, then restore it, as it was the one I had in backup. I was having stuttering problems, and thought that because I had added & deleted so much stuff in the past few days, restoring my clean backup would clear it up.

I have the latest TWRP recovery, and wiped the cache & dalvik, then went to restore the rom. But when it finished, and I rebooted, got stuck at the ktoonez (my kernel) logo. I did a battery pull, and went back into recovery, did a full wipe, then tried to restore the rom. This time, 3/4 of the way through, it rebooted on its own, and started to bootloop. When I tried to get back into recovery, it would only boot to the Samsung logo, so I knew that now my recovery was gone. I used Odin on my PC to restore it, but it does the same thing. I do a complete wipe, restore the backup, but it again reboots by itself out of recovery about 3/4 of the way through, then it gets stuck at the kernel logo.

I don't have anything other than the backup stored on the phone. Is there a way that I can load a rom from my PC through recovery so that I can just start over? Or will I probably have to Odin everything back to stock, and start from there (which I've never done from the PC. I have used mobile odin though)?
[T-Mobile, Samsung Galaxy SIII] Kamau54:
Update:

I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
[T-Mobile, Samsung Galaxy SIII] Kamau54:
anyone?
[T-Mobile, Samsung Galaxy SIII] serio22:
Did you go into recovery and do a factory reset?
[T-Mobile, Samsung Galaxy SIII] Kamau54:
Yes, a couple times.

I have also tried taking the card out the phone and putting it into the pc to manually place the rom on it, then flash it, but my pc wont see the card. It makes the sound that something has been inserted to a usb port, but shows nothing on the computer.
[T-Mobile, Samsung Galaxy SIII] serio22:
What if you flash a recovery and then a ROM?
[T-Mobile, Samsung Galaxy SIII] VolcanicSkunk:
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:

adb sideload location/of/ROM.zip

This should transfer the ROM to your internal sd card.

You should make sure that your computer detects the phone before the transfer with the command:

adb devices

It should should return:

List of devices attached
phone id recovery

If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.

I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.

I hope you're able to get your phone booting again!
[T-Mobile, Samsung Galaxy SIII] Kamau54:
The phone doesn't have a rom to start with I don't think. This is what I Odin:

http://www.androidfilehost.com/?fid=23212708291682181

It's the right one, as I have the TMO S3, and I already had it on my phone to begin with. I thought it came with the stock rom included, but when I rebooted, it just gets caught in a bootloop after it says optimizing apps. I can get the recovery back, but I don't know how to get a rom on the card to flash. I even tried to use a old card, but again, my pc won't see it, so I can't put a rom on it to flash.
[T-Mobile, Samsung Galaxy SIII] Kamau54:
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.

But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .

Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.