Related
Disclaimer: I make no warranties expressed or implied. This information is provided for research and educational purposes only. By reading this post, you agree not to hold me, my estate, my heirs, or my dog responsible for anything ever and waive all of your rights to legal action against said parties forever in perpetuity. Amen.
Note: this guide covers Android 2.1 (Eclair). Various builds of Android 2.2 (Froyo) are available in the forum. You should NOT use my guide if you are installing a build of Android 2.2 (Froyo). Currently I am running the Jboogie Froyo Rom, Orange DeBlur v4, which is great and (in my opinion) the best Froyo Rom out there for USA T-Mobile. Froyo is not much faster than Eclair in terms of benchmarks, but the apps are better, especially if you need the Android email app for connecting to an exchange server.
Now, on to the guide:
Goal: starting with a fresh-out-of-the-box Defy from T-Mobile USA, root the phone, install a non-US (or other) Rom, and recover your 3G capabilities.
Why: non-US Roms have much less bloatware from T-mo and Motorola, and allow you to install JIT/Deodex if you want
0) Oh noes! You've got to sign up for a Motoblur account just to use your phone! Create a throwaway email address at any of the webmail providers (gmail, yahoo etc.) and then go through the motions on the phone to set it up and get to the main home screen. Editorial note: wtf!!!
1) Get root access to your phone. Following Sorensiim's excellent guide, download the Z4Root app, which allows you to root (and unroot) your Defy. (thanks to Sorensiim for hosting!)
>> n00b notes:
First, go to Settings -> Applications and check "Unknown Sources" so you can run the Z4Root app.
Also go to Settings -> Applications -> Development and check "USB Debugging" so you can connect to your phone from your computer later.
Then open your phone's browser, navigate to this page, and download the app directly to your phone.
Install the app from your "Downloads" folder (accessible inside your Browser)
Run the Z4Root app on your phone, hit the "root" button and wait for it to work its magic.
This is what you will see if you run Z4Root after you reboot from rooting:
{
"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"
}
2) Install recovery so that you can make a backup of your operating system to your SD card before you do anything else - that way you can go back to the stock T-mobile OS if you need to.
Following Sorensiim's excellent guide, and many thanks to tenfar who put it together for us, just go here to download the Recovery App. (thanks to Sorensiim for hosting!)
>> n00b notes:
Just like before, visit this page on your phone's browser. Click the link to download the recover app, and once it's done, install it.
Allow the app to have root access, and check the box to always allow.
Once you are in the System Recovery program, click "Install Recovery System"; it will let you know when it's successfully installed (see image below):
3) Make a backup by opening the System Recovery app, and then press the "Recovery Boot" button. Back it up! Once again, details here, big thanks to tenfar!
>> n00b notes:
Once you have booted into recovery, you'll see the black/green screen shown below.
Use the volume buttons to navigate the menu and the power button to select an option.
Go to "Backup and Restore", and then "Backup".
If you need to restore later, just do the same thing except hit "Restore" and then select the one you want.
4) Flash a different ROM! Now here's where it get's a little more tricky. First, you'll want to follow Higgsy's Debranding Guide closely. I won't repeat his excellent guide, but here are my comments on the steps in the guide:
>> n00b notes:
Technically this step is optional - you can still weed out the bloatware and overclock while keeping your stock USA ROM. However, you will miss out on being able to install JIT/Deodex and having other features of non-USA roms, such as tethering.
Step 1: I used the consumer drivers package - Motorola 4.8.0 Driver with MotoConnect - since I am using 64 bit Windows 7. You can also use the developer drivers that Higgsy links to in his guide (available here).
Step 2: I used the JRDNEM_U3_2.34.1 firmware from central Europe, since you don't have to deal with Motoblur that way. You don't have to use this Rom of course, there are a bunch of different options, but I wanted to stick with a "real" Rom from Motorola as a starting point. Note that a firmware version is not the same as an Android version - i.e. v2.34.1 is NOT android 2.3, it is still anroid 2.1. Confusing, I know. Other Rom options include custom Roms that people put together and list in the XDA Developers forum. If you want to use one of those, you would follow their instructions for installing that particular custom Rom.
Step 3: In case the RSD Lite download link in the guide doesn't work, you can also get it from Megaupload the password for the site and the rar file is 'alabama'.
Step 7: Before booting the phone into the bootloader, you may want to clear out your data manually (aka "wipe your phone"). Go back into the System Recovery app, go to "Recovery Boot", and then when you're back on the black screen, select "Wipe DATA/Factory reset", "Wipe CACHE Partition" and then also go to "Advanced" and then select "Wipe Dalvik Cache". Then hold down the power button to turn off your phone. You won't be able to boot your phone after this, except by holding down the volume up + power on buttons together to get into the bootloader, so I would make 100% sure you have the drivers and RSD Lite installed and working!
Step 8: I would recommend waiting until it says "PASS" on the right side of the RSD Lite window before closing the program (this is after the "PLEASE START PHONE MANUALLY" phase is completed).
You should now have a working phone, with EDGE connectivity (little "E" in your status bar at the top) but no 3G or H icons. What, no 3G? We'll fix that next.
5) Re-root your phone and reinstall System Recovery following steps 1 and 2 above.
6) Install JIT/Deodexed: Optional step if you flashed either the 2.21 or 2.34 ROM. If you want to make your phone a bit faster, this is for you. Higgsy's guide is here if you want to do this!
>> n00b notes:
Update: on my third time flashing the phone, I was able to get JIT/Deodexed working fine. I think my failure the first time may have been due to my old SIM card, which I replaced because I was having problems reading the card and sending text messages (couldn't update the SMSC number).
Originally, I couldn't get the JIT/Deodexed package to work on my USA phone after installing the 2.34.1 firmware (too many 'untoward things happening' like Higgsy warned about), so I just skipped it the second time I flashed the 2.34.1 firmware.
The process of installing the packages is super easy, although you may want to make a backup before you start just in case. You can never have too many backups, because you can always transfer them to your computer if your SD card gets full. They are stored on your SD card under /goapkrev/backup/
The performance improvements are substantial - see graphs below.
Obviously you must get the package that matches the version of the ROM you installed. If you didn't flash a new ROM and still have the stock USA one, you are out of luck.
7) Make another backup! Now you want to backup your freshly-installed (and possibly JIT/Deodexed) Non-US Rom. Your first backup was the USA T-mobile Rom. You'll want to make this backup in case you eff something up in one of the next couple steps and want to go back to a fresh Non-US install and try-again.
Following the instructions in Step 3 above, load the System Recovery app, Recovery Reboot, and make a backup. Then reboot your phone!
8) Install ADB and/or Android SDK on your computer - there is a great guide on the Cyanogen Mod Wiki here. Just go slow, and follow the instructions. Once you can do "adb devices" and see your phone, you're good to proceed onward.
>> n00b notes:
To open a Command Prompt in Windows, go to "start" -> "run" and type "cmd" in the box or just go to "start" -> "all programs" -> "accessories" -> "command prompt").
Note that if you have 64-bit windows, you'll still need to install the regular 32-bit Java Development Kit (JDK), not the 64-bit version.
When you're editing your "path" environment variables in windows, note that you can't have spaces before or after semicolons. This is what my full path looks like (and iTunes works now - it didn't when I accidentally left a space after QTSystem\;
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;[B]%SystemRoot%;C:\Program Files (x86)\Android\android-sdk-windows\platform-tools;C:\Program Files (x86)\Android\android-sdk-windows\tools[/B]
9) Fix 3G
*** NOTE: This step only applies to USA phones. If you're not in the USA, your 3G probably works fine.
Download HandlerExploit's 3G fix from the 2.21 UK ROM or my 3G fix from the 6.19 US ROM. Thanks to HandlerExploit for figuring this out for us.
>> n00b notes:
There's not much difference between the two 3G fixes, except that each one will display different info in the "About Phone" section (either v2.21 or v6.19). For example, if you use my fix, "About Phone" will tell you that you have "Build number: JORDN_U3_6.19.0" installed - this is a side affect of the patch. For HandlerExploit's fix, "About Phone" will report v.2.21 GB
You may want to write down what Rom you actually installed if you think you might forget (for example, my phone actually has "JRDNEM_U3_2.34.1" even though it reports 6.19.0 in "About Phone")
If you downloaded HandlerExploit's 3gFix, you can choose to follow his instructions or the ones below, which are basically the same as what is in his, except you enter the commands line-by-line instead of running them through a script. I prefer line by line because I like to know what I'm doing. Both methods should work fine.
If you are unfamiliar with basic command prompt commands (cd dir ls etc.) please see my reply later in this thread
Once you download the zip file, extract it somewhere, like your desktop.
Alright, time to get some ADB skills. Plug your phone in via USB and open a command prompt. First we connect to the phone by typing this, each command followed by the "Enter" key:
Code:
adb shell
Then you want to run some commands as a super user so type:
Code:
su
Quick! Look at your phone, and tell it to always allow superuser access. You only have to do this once.
You should have a "#" command prompt now (instead of a "$" like before) indicating that you are working as a superuser (#=superuser). Now some more commands to enter. (n00b tip: you can copy and paste each line into the command prompt by copying the line from this guide and right clicking "paste" on the command prompt window)
Code:
mount -o remount,rw -t ext3 /dev/block/mmsblk1p21 /system
chmod 0777 /system/etc/motorola/bp_nvm_default
chmod 0777 /system/etc/motorola
chmod 0777 /system/etc
chmod 0777 /system/app
chmod 0777 /system/lib
chmod 0777 /system/lib/modules
chmod 0777 /system
exit
exit
So now we have set CHMOD Permissions for some folders on your phone, and then quit the adb shell. Now we've got to push some files to the phone:
Navigate to the folder where you extracted the files from the 3g fix you downloaded above, for example, type:
Code:
cd c:\users\administrator\desktop\3gfix\
then enter:
Code:
adb push system /system
This will copy all the files in the subfolder "system" to your phone's "/system" folder, overwriting them (which is why we made a backup earlier). Then enter:
Code:
adb reboot
to reboot your phone. You should have 3G connectivity now - note that it may take up to a minute or so for it to appear the first time, and you may not see the icon at all if you have WiFi enabled (so disable it in your settings to test it out).
If it still doesn't work, try going to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Access Point Names" -> (settings button of four squares) -> "Reset to default". Also make sure the APN name is highlighted with a green dot. You may also have to go to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Operator Selection" -> "Select Automatically"
This is what the 3G icon looks like of course:
10) The phone is yours. You can:
Install some apps: Titanium Backup & Launcher Pro for example.
Weed out the bloatware, overclock, and scale: see Sorensiim's awesome guide here. I highly recommend doing this, just bumping up to 1000mhz overclock makes the phone's performance much more snappy. If you overclock, you should definitely use Sorensiim's scaling method and his scaling files -- it makes a very noticeable improvement in battery life.
Benchmark your phone: with Quadrant Standard Edition, available in the app market
Play Angry Birds all day: :-D
Here is my phone benchmarked, with no overclocking, no bloatware removal, no JIT/Deodex packages, just the stock JRDNEM_U3_2.34.1 firmware (note that the phone with the US Rom straight out of the box benchmarks a little higher at 987. I'm not sure why this is.):
Here it is after overclocking to 1000mhz and my own customized bloat removal (not as much as most people, i use some of the default apps), also still no JIT/Deodex. Obviously you can get it to go faster if you want to overclock more, install JIT/Deodex, and remove more bloat:
Edit: These are the apps I disabled for the second benchmark (renaming them using Sorensiim's guide )
AdService.apk
ArcPhotoworkshop.apk
ArcVideoEditorLite.apk
esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk
FBAndroid-1.3.2.apk
Fota.apk
hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk
Kindle-1.0.2-OEM-SingleSign.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MySpace.apk
Protips.apk
Quickoffice_BasicViewer_2.0.52.apk
revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk
truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk
WeatherWidget.apk
Here is what I got to after JIT/Deodexed was installed on 2.34 - same apps removed, same overclock at 1000mhz. Removing VisualizationWallpapers.apk and YouTube.apk got me to 1308.
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Sent from my MB525 using XDA App
Passa91 said:
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Click to expand...
Click to collapse
Yes, you would do that with Titanium Backup. System Recovery is for making entire images. It's easier to replace things piece-by-piece with Titanium Backup.
Thanks for this...along with handler's tips on SA I got it working.
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
heglen said:
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
Click to expand...
Click to collapse
Sure you can remove Swype, theres still the standard android keyboard installed as well. Check out scandinavian keyboard from the market too
I had a big problem in step #8, installing ADB. No matter what I tried, the command "adb devices" would not work. But I was able to solve it by following this:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
You have to download the ADB files from
http://www.megaupload.com/?d=RTEY0Q97
and put them into your
Android\android-sdk-windows\tools
directory. Word is, they were taken out by Google for whatever reason in the R08 version, and must be restored in order for ADB to work.
After I extracted the files into the Tools folder, and used the 'adb devices' command, it worked like a charm!
Quick noob question.
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo? Currently as I have the stock firmware/ROM it does not let me connect to neither 3G nor Edge. I've tried my SIM with Nokia N900 and 3G works fine, since the T-mo network doesn't recognize it as a smart phone. Please let me know if de-bluring/debranding my Defy will solve this problem for me.
Thanks in advance.
nvvass said:
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo?
Click to expand...
Click to collapse
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
rob-t said:
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
Click to expand...
Click to collapse
I do have a plan. Many friends' Nexuses work fine with the same plan. I know a guy with a Nokia N900 and it works in 3G even with his grandfathered T-zone for $4.99. Why pay more? You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Thanks.
nvvass said:
You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Click to expand...
Click to collapse
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Wifi Calling?
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
rob-t said:
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Click to expand...
Click to collapse
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
bcrawf68 said:
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
Click to expand...
Click to collapse
WiFi calling seems to work fine for me.
nvvass said:
Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan.
Click to expand...
Click to collapse
Ah OK thanks for the explanation. I currently use T-mobile but I don't really know much about their offerings. I would try the 2.21 or 2.34 firmware and then apply the UK 3G fix made by HandlerExploit, instead of the USA 3G fix I made from the US firmware.
Only one way to really find out though...
Excellent!
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
cloogshizer said:
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
Thanks, yes, I updated the guide accordingly. 3G fixing should only be necessary in the USA.
nvvass said:
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
Click to expand...
Click to collapse
cloogshizer said:
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
first of all.. thank's for the great tutorial man..!!
second of all, I got this T-mobile defy from my uncle and I used it in Indonesia.. It's true what nvvass said, that the T-mo firmware constantly tries to connect with the "smart phone" data plan.. which caused me to unable to connect to my local provider data connection.. after I flashed the defy with the central-europe de-blur firmware, Voila..!! I got 3G connection directly..!! without any settings at all..
hope this helps for anyone using US T-mobile defy outsite of US.. cheers mate..
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Jt612 said:
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Click to expand...
Click to collapse
where did you get the phone from? if it from US and still locked with T-mobile, than it would refuse to connect with local provider.. you need unlock code..
i bought it in australia its an australian phone... works fine when i restore my backup of australian software but i would like to use the 2.34.1
Decided to post this for anyone that is curious and wants to know the terminology used in these roms.
I take NO CREDIT for this, just wanted to share my findings. Source below. Let me know if I missed any.
http://wiki.cyanogenmod.com/index.php/Terminology
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
TERMINOLOGY -
*TRWP- Team Win Recovery Project/ It has a touch based recovey interface.. and its more consistent than cwm it seems
*CWR aka ClockworkMod Recovery-
A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
*Superuser-
A progam which gives unlimited access privileges to perform any or all operations on the operating system.
*KIES mini-
Kies Mini is an official application from Samsung that is used to update the software on your phone. It should not be confused with the full Kies application, which has a lot more functionality and is not officially supported in the USA. Therefore, abbreviating "Kies Mini" as just "Kies" can cause confusion.
*ODIN-
Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
*OTA or FOTA-
(F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
*ODEX-
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
*DEODEX-
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
*Busybox-
A set of Unix tools / commands that has been compiled for use on your phone. These are not usually full-featured versions of the Unix commands found on the larger platforms counterparts, but they are pretty close and useful nonetheless.
*3G/4G-
3G/4G is the term generally used to describe 3rd/4rth Generation mobile telecommunications, specifically allowing for greater throughput of data over cellular networks.
*Baseband/Modem-
Baseband refers to the original frequency range of a transmission signal before it is converted, or modulated, to a different frequency range.
*Bloatware-
Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit. For example, the Photobucket app included on the G2 by TMobile.
*CDMA-
Code division multiple access (CDMA) is a channel access method used by various radio communication technologies. It should not be confused with the mobile phone standards called cdmaOne and CDMA2000 (which are often referred to as simply CDMA), which use CDMA as an underlying channel access method.
*Firmware-
Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
*Flash-
Non-volatile computer storage that can be electrically erased and reprogrammed (similar to EPROM). No power is needed to maintain the information stored in the chip. This technology is primarily used in memory cards and USB flash drives for general storage and transfer of data between computers and other digital products. Because of its ease of use, speed, ability to be updated (see flashing), this technology is often used in mobile devices, PDAs, digital media players.
*Kernel-
The central or core software component of most operating systems. Its responsibilities include managing the system's resources (the communication between hardware and software components) and can provide the lowest-level abstraction layer for resources (especially memory, processors, and I/O devices).
*IMEI-
The International Mobile Equipment Identity is a number unique to every GSM, WCDMA, and iDEN mobile device, as well as some satellite devices. The IMEI number is used by the GSM network to identify valid devices and therefore can be used to stop a stolen device from accessing the network. For example, if a mobile device is stolen, the owner can call their network provider and instruct them to "ban" the device using its IMEI number. This renders the device useless, whether or not the device's SIM is changed. The IMEI can be displayed by dialing *#06#.
*IRC-
Internet Relay Chat. Basically a chatroom, or a cross between Instant Messaging and a forum.
*Open-source-
Open-source is software that anyone is allowed to see the 'source' code. In the context of Android, Open-source refers to the approach to the design, development, and distribution of software. This offers accessibility to a software's source code for modification, improvement, bug-fixing, and security-enhancement. CyanogenMod is based on this principle.
*AOSP-
Android Open Source Project
*Radio-
The cellular radio on the device which needs control software called firmware to control it.
*ROM-
Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
*SDK-
Software Development Kit. You can find the Android SDK at http://developer.android.com/sdk.
*Vanilla-
A clean, unmodified version of something. In the context of Android ROMs, vanilla refers to the stock ROM that came pre-installed on the device.
*Widget-
An application that lives (in other words, is always running) on the homescreen instead of being 'run' like a regular app. Common examples are calenders and weather widgets.
*Soft Brick-
Recoverable without professional repair via Odin
*Hard Brick-
Not recoverable, better hope you have a warranty/insurance. Usually happens when flashing wrong rom or modem, like from another device.
*Superwipe-
A tool that will get your device "Rom-flash-ready" by doing the necessary wiping
*Zipalign-
Reduces the amount of RAM consumed when running the application by allowing data to be mmap'd in; which causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries.
*Sleep of death or S.O.D.-
Refers to the the device not being able to be awaken after a long time in "off mode" like while charging while you sleep. If you try to awaken your device, I will not come on. Usually requires a long press on the power button to reset the device or battery pull.
*Hot Reboot-
An option to reload all apps and framework files without rebooing the complete device
*FC-
Foreclose
*WIP-
Work in Progress
*Kanged-
To have one's developer code and work taken, manipulated, rebranded, and re-released by someone else with no credit
*Insecure-
A kernel that will give you root access, installing one of these will allow you to run apps that require root access, and allow you to make proper backups of your handset.
Android Specific Definitions
*ADB-
Android Development Bridge. Command line tool used to communicate with & control the device over a USB link from a computer. The ADB command is found in the Android SDK.
*Android-
Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
*Apps2SD-
Move applications from the internal NAND memory on the device to a removable SD Card.
*CyanogenMod Updater-
An updater written by Cyanogen that allows you to receive OTA (Over-The-Air) updates to CyanogenMod.
*Dalvik-Cache-
The dalvik-cache directory holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
*Fastboot-
Fastboot is protocol used to directly update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled almost all production devices since USB support is disabled in the bootloader.
*GApps-
See Google Apps.
*[CO
Nice job! Thanks for compiling that.
I was just saying on another thread that I wish when I had rooted last week that I knew more about WHAT and WHY I was doing something vs. just following the directions of the dev! Love to see someone maybe elaborate on the actual root process. Such as explaining why we have to use odin vs. say just drag and dropping files, what is and why do we have to have Superuser, explain CWM recovery, etc.
Nice post. I didn't know what odex vs deodex was but now I do!
Swyped from my iPhone eater
-BeastMOD
-Supercharged 1000HP
you deserve a thanks click and a sticky... sorry can only provide one
OP updated with Superuser, ODIN and CWR.
thanx bro..my noob level dropped lol
mightymike889 said:
thanx bro..my noob level dropped lol
Click to expand...
Click to collapse
Lol. If I can help at least one person than my job has been done.
Powered by the SGSII....
Very nice list. But I have one question, what's ota? ;-)
——————————
Deebo took your bike too?
ThC23 said:
OP updated with Superuser, ODIN and CWR.
Click to expand...
Click to collapse
Thanks! Learning more and more!
Superuser...I thought I "installed" Superuser like an app or interface?
AOSP - Android Open Source Project.
I just looked this one up the other day after wondering for a loong time what it meant.
m.
escrowdog said:
Thanks! Learning more and more!
Superuser...I thought I "installed" Superuser like an app or interface?
Click to expand...
Click to collapse
Lol, my bad! It is, it was late last nite and I have no idea where that came from, lol. Superuser fixed. Thanks.
Busybox added.
ThC23 said:
Lol, my bad! It is, it was late last nite and I have no idea where that came from, lol. Superuser fixed. Thanks.
Busybox added.
Click to expand...
Click to collapse
You should've added ota in the op too.
——————————
Deebo took your bike too?
Write what CWR actually stands for. ClockworkMod Recovery
The_Biz said:
You should've added ota in the op too.
——————————
Deebo took your bike too?
Click to expand...
Click to collapse
darkamikaze said:
Write what CWR actually stands for. ClockworkMod Recovery
Click to expand...
Click to collapse
OP updated, thanks.
Thanks OP! You know what I would really like - a listing for the 'just past n00bs' that includes items like:
Baseband version
Kernel version
Mod version
Build number
(Basically all the less than painfully obvious items on the "About Phone" page. )
As an example, Keis wanted to update the firmware to VKID2 last night, but I thought, screw it, I am loading CM7. However, I still see the old baseband version there. Whats the difference? Should I (can I) load the samsung update now that CM7 is loaded. Is there "firmware" and a "rom" or are they the same thing... etc.
anyway, thanks for the glossary. Its good!
I just bought my first Android a week ago. I've been reading a bunch and was confused by many terms. This was very helpful. Thanks!
unlocked ; can also referr to the bootloader too fyi
Sent from my MB860 using Tapatalk
Thanks
Thank you so much for such an informative page. What is Android without Root privileges
Thank you. good Info.
dwayner79 said:
Thanks OP! You know what I would really like - a listing for the 'just past n00bs' that includes items like:
Baseband version
Kernel version
Mod version
Build number
(Basically all the less than painfully obvious items on the "About Phone" page. )
As an example, Keis wanted to update the firmware to VKID2 last night, but I thought, screw it, I am loading CM7. However, I still see the old baseband version there. Whats the difference? Should I (can I) load the samsung update now that CM7 is loaded. Is there "firmware" and a "rom" or are they the same thing... etc.
anyway, thanks for the glossary. Its good!
Click to expand...
Click to collapse
This is what it should look like with the new update. This has the latest baseband and its 2.3.6.
Powered by the SGSII....
If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful than show your appreciation and hit that thnx button.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
How to root ANY US VERSION ON MAC
How To root At&t Samsung Galaxy S III I747 No Tripping Flash Counter
How TO ROOT USING SNAPDRAGON TOOL KIT!
How To Install ClockWorkMod Recovery!
How To upgrade ClowckWorkMod Recovery!
HOW TO UNROOT & FACTORY RESET YOUR SGSIII
How TO Flash ROMS!
How TO Back up Rom on Samsung Galaxy III
How to flash themes
MOD FEEL FREE TO STICKY IT, AS IT WILL BE FILLED UP & THIS THREAD WILL BE NOOB HANG OUT PLACE!
Legit!
Thanks for this thread...this will be my first android phone
I'm switching from iphone 4 to the SGS3, although i'm still eagerly awaiting my phone to arrive at my local BB, i've been reading up on all this stuff as much as i can...
+1 to sticky
send2amrish said:
Thanks for this thread...this will be my first android phone
I'm switching from iphone 4 to the SGS3, although i'm still eagerly awaiting my phone to arrive at my local BB, i've been reading up on all this stuff as much as i can...
+1 to sticky
Click to expand...
Click to collapse
Same here. Nice to have all of this info to read up one while I wait for my phone. Hopefully bb will come through soon. Thanks for the Thread!
heya AppDroid.
i lol every time i see my quote in your guides...
Appreciate the effort here....if only there was a way to make the noobs read all this before being allowed to post on the board
Sup Pirateghost!
Well Your Quote explains why we no get update like GNex! SO its great Explanation to NOOBS! lol
But hope you get this phone/already have it! Looking forward to flashing your stuff!
Pirateghost said:
heya AppDroid.
i lol every time i see my quote in your guides...
Click to expand...
Click to collapse
appdroid said:
Sup Pirateghost!
Well Your Quote explains why we no get update like GNex! SO its great Explanation to NOOBS! lol
But hope you get this phone/already have it! Looking forward to flashing your stuff!
Click to expand...
Click to collapse
Sorry, I don't have it and don't plan on buying another device off contract until the next nexus.
Sent from my HTC One X using Tapatalk 2
Noob here. I plan on switching from a 3gs iPhone (AT&T) I've had for about 2.5 years. Had a few questions.
What's the deal with the micro sim? Will I just need to cut my old one down to size (i've seen the tutorials) or will I need to transfer to the new one they provide?
I don't plan on doing any rooting but I did see a thread about removing unnecessary processes to free up RAM and would like to do this if it is simple. Any advice/recommendations on how to do this without getting too detailed?
Lastly, for those that may have already done the switch or anyone else who would know, what are some of the most important changes I will have to get used to coming from the iPhone? What is the coolest thing I didn't have before? What are some of the first things a noob should do to his phone to make it "better" without getting crazy. I'm not a developer or specialized in computers or code or anything. Just someone looking for a few ideas. Thanks!!
PS thanks for the noob forum
If you're referring to this thread, then you would need to root the device to accomplish what he's detailing there.
http://forum.xda-developers.com/showthread.php?t=1726842
Not sure how I missed that. Guess I'll have to look into rooting.
Spoonman87 said:
Not sure how I missed that. Guess I'll have to look into rooting.
Click to expand...
Click to collapse
If that's your only reason for rooting, then it may interest you to know that in Android 4.0 they introduced the concept of disabling system apps. It'll still take up disk space (which is negligible compared to the 16 or 32 GB availalbe), but it won't be allowed to run (no RAM usage) and it will be removed from the app list. So, it will be as if it's uninstalled.
So that's probably a better option if this was your only reason for rooting.
There are plenty of other reasons to root though, but I'll leave you to discover those for yourself. Personally, I value my 1 year Verizon warranty. So I wait until my second year to root.
demarcmj said:
If that's your only reason for rooting, then it may interest you to know that in Android 4.0 they introduced the concept of disabling system apps. It'll still take up disk space (which is negligible compared to the 16 or 32 GB availalbe), but it won't be allowed to run (no RAM usage) and it will be removed from the app list. So, it will be as if it's uninstalled.
So that's probably a better option if this was your only reason for rooting.
There are plenty of other reasons to root though, but I'll leave you to discover those for yourself. Personally, I value my 1 year Verizon warranty. So I wait until my second year to root.
Click to expand...
Click to collapse
Good to know. Thanks!
Where is the ...
Okay, on a very serious note ...
Where is the post on what to do in case you run out of toilet paper? Well? Well? Come on, this is very important.
Peter
Hopefully this will address a few questions, and help anyone new to the forum. I've assembled a list of terms and acronyms used on the forum below. Terms with links go to sources or threads with additional information. An item in all caps in a definition is one that I've defined elsewhere.
Use CTRL+F to find a specific term.
FORUM RELATED:
SEARCH: The button just above the title of the forum or thread you are in. This should be your first resort when trying to find information.
GENERAL: This is the place for posting anything general. These include tips, ideas, comments, etc.
Q/A: This is the place for posting any questions. If you have a bug to report in a program or ROM (and have the minimum of 10 posts), post it in the appropriate thread in the ANDROID DEVELOPMENT subforum.
ACCESSORIES: This forum is for any items that attach to the physical hardware of the Android device.
ANDROID DEVELOPMENT: This is the place for posting Hacks/Mods/ROMs/Modems/Kernels. Generally reserved for developers, there is a 10-post minimum before a user can post here. This is the place to inform developers of bugs or software issues - ask questions in the Q&A subforum.
ORIGINAL ANDROID DEVELOPMENT: Similar to the ANDROID DEVELOPMENT subforum, this is where Hacks/Mods/ROMs/Modems/Kernels developed from scratch (i.e. not ported from other devices) are located.
THEMES AND APPS: This is the place for posting themes as well as programs. Many applications can be interchangeable with Android Development, so use your best judgement.
FWIW: Short for "For what it's worth"
OP: Short for Original Poster, or the person who originally started the thread.
PM: Short for Private Message. Allows users of XDA to send and receive non-public messages. Accessed from USER CP.
THREAD: An individual issue page on the forum. This thing you're reading is a thread.
THREAD TOOLS: A button that allows users to subscribe and unsubscribe from THREADs. Subscriptions can be accessed from USER CP. See button screenshot below.
USER CP: Short for User Control Panel. This button near the top of the XDA page allows users to update their avatar, personal information, and signature. PMs and subscribed threads can also be checked in this location. See button screenshot below.
YMMW: Short for "Your mileage may vary".
ANDROID DEVICE RELATED:
4G: Short for Fourth Generation. Refers to network connection speed levels that exceed 3G / Third Generation speeds. See also LTE.
ADB: Short for Android Debug Bridge. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
AOKP: Short for Android Open Kang Project. Consists of Android builds compiled from open source, but with special features unique to each build. See also KANG.
AOSP: Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK: An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
BOOTLOADER: There are two of these; the primary and secondary bootloaders. These programs tell the Android device how to start up, and are critical to its functionality.
BML: Short for Block Management Layer. Provides a programming interface simulating the parallel disk model.
BRICK: An Android device that is completely non-responsive, i.e. nothing lights up, the screen does nothing, no combination of button presses cause any reaction. Can only be restored by JTAG or warranty service.
BUILD.PROP: A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations.
BUSYBOX: An application that contains many standard Unix tools. Commonly used with TITANIUM BACKUP.
BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. pushing volume up, home, and the power button for 10 seconds will reboot into the RECOVERY menu). 3-Button Combo is a common example. May also be referred to as a "Chord".
CLOCKWORKMOD RECOVERY MENU: This is a program that allows you to install custom ROMS as well as do many other low-level customizations. Often referred to as the "RECOVERY MENU". See also "ROM MANAGER"
CM: Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
CWM: Short for ClockWorkMod Recovery Menu. See CLOCKWORKMOD RECOVERY MENU.
DALVIK CACHE: The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
DALVIK: The Android operating system's memory management tool. This program handles which other programs are running and assigns memory to them
DEODEXED: Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
DOWNLOAD: The download menu is the lowest-level interface to the Android device. Allows for full access to all flashable items on the device via the ODIN/HEIMDALL tool.
EFS: The directory /efs on the Android device's internal storage. Contains files with the Android device's IMEI, wireless devices MAC addresses, product code, and other information..
EMMC: Short for Embedded MultiMediaCard. A chip architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array package.
EXT4: A journaling file system (e.g. NTFS, FAT32 are file systems) often used by Linux distributions. Can be used with Android.
EXTERNAL SD: A micro SD card that has been inserted in the micro SD slot in the Android device. Can be removed.
FACTORY RESET: This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card.
FC: Short for FORCE CLOSE. See FORCE CLOSE.
FLASHING: The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
FLASH COUNTER: A line of code in several Samsung Galaxy devices' bootloaders that counts the number of times a user uses ODIN to flash code to the device. Commonly used to detect software modification. Can be reset with TRIANGLE AWAY.
FORCE CLOSE: When a program on the Android device becomes unstable, the DALVIK program will force it to terminate to prevent further system instability.
FREEZE: Specific to TITANIUM BACKUP. Using the TITANIUM BACKUP tool, the user changes a program into a non-functional, but still installed, state. Useful for identifying problem and FCs.
GOVERNOR: A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HEIMDALL: An open-source program by Benjamin Dobell that allows the Android device to be flashed back to stock or with custom software. See also ODIN.
HSUPA/HSDPA: Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS: Short for Ice Cream Sandwich, the Android OS version 4.0.x.
IMEI: Short for International Mobile Equipment Identity. A unique number to identify GSM, WCDMA, and iDEN phones. Used by GSM networks to identify valid devices.
INTERNAL SD: The internal storage memory of the Android device. Not a physical SD card that can be removed.
JB: Short for Jelly Bean, the Android OS version 4.1.x.
JIG: A piece of hardware that makes a physical connection between pins of the USB slot to force the Android device into DOWNLOAD mode.
JTAG: A process of connecting directly to the main board of the Android device to rewrite corrupted BOOTLOADERS.
KANG: Originally used to refer to stolen or leaked code. In CyanogenMod builds, a KANG build is one that is an unofficial branch from the main CyanogenMod development. These builds usually contain custom modifications that did not make the official CyanogenMod builds.
KERNEL: The collection of software drivers and more "nuts and bolts" programs that allow the basic functionality of the device.
LAUNCHER: A program that launches programs in Android. Examples are Touchwiz (Samsung), Launcher Pro, ADW Launcher, and Go Launcher.
LTE: Stands for Long Term Evolution. It is based on the GSM/EDGE and UMTS/HSPA network technologies, increasing the capacity and speed using a different radio interface together with core network improvements.
MD5 CHECKSUM: A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
MODEM: The software that interfaces with the phone's radio hardware to connect to cell phone towers.
MTD: Short for Memory Technology Device. A type of device file in the Linux structure that interacts with flash memory. Provides an abstraction layer between applications and hardware-specific device drivers.
MTP: Short for Media Transfer Protocol. Allows file transfers between the Android device and a PC. Safer to use than USB Mass Storage, as it does not seize complete control of blocks on the Android Device; instead, it connects in a transactional (all-or-nothing transfer) method.
NANDROID BACKUP: A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
NO-WIPE PACKAGE: A rom update package that leaves the user's market apps intact while still performing the updates to the system files. Restoring from backup is not necessary. See also WIPE PACKAGE.
NV_DATA.BIN: An encrypted file in the /EFS directory that contains the Android device's IMEI number and product code. See also EFS.
OC: Short for Overclocking. See OVERCLOCKING.
ODEX: A file that is associated with an APK file, containing a list of the dependencies for the program. See also DEODEXED.
ODIN: A Samsung proprietary program that allows the Android device to be flashed back to stock or with custom software. See also HEIMDALL.
OVERCLOCKING: Setting the processor's clock speed to run faster than its default setting, i.e. 1200 MHz (1.2 GHz) vs 1000 MHz (1.0 GHz).
PIT FILE: Short for Partition Information Table file. One of the possible file types used while flashing with ODIN or HEIMDALL.
PRIMARY BOOTLOADER: Also known as First Stage Bootloader. The first bootloader run at boot time, this bootloader finds RAM for the Android device, and hands the boot sequence off to the SECONDARY BOOTLOADER. See also BOOTLOADER, SECONDARY BOOTLOADER.
RAT: Short for Radio Access Technology. This determines how the network decides the QoS (quality of service) on the connection between the Android device and the carrier's data towers.
RECOVERY: The menu that allows a user to do many low-level operations on the Android Device. This menu can either be the stock Samsung menu, or the CLOCKWORKMOD RECOVERY MENU (CWM). See also CWM.
RFS: A Samsung-proprietary file system (e.g. NTFS, FAT32 are file systems) used on some Android devices. Stands for Robust File System.
ROM: The collection of programs, themes, and settings that create the general look-and-feel of your Android device. This is what most users will initially be wanting to change.
ROM MANAGER: The Android OS front end program for the CLOCKWORKMOD RECOVERY MENU (or CWM). Allows use of many of the CWM features from inside the Android OS. See also CWM.
SECONDARY BOOTLOADER: Also known as Second Stage Bootloader. The second bootloader run at boot time, this bootloader handles the processes required to allow the Android device to boot the main kernel, such as file systems, memory, and MODEM. See also BOOTLOADER, PRIMARY BOOTLOADER.
ROOT: Changing the permission level of the Android system to its most powerful level, the root user, allowing full access to the file system.
SILVER HOME BUTTON: One of the most powerful and dangerous modifications to the Android device available. Can cause a variety of results, from improved signal to radioactive cats in boxes. Should not be used by the infirm or those with faulty gluons.
SOFT BRICK: A device that is not functioning correctly, but still shows some signs of operation. See also BRICK.
STOCK: The Android software version that comes installed on new devices, prior to sale to the user. Can also be used to refer to the Android software issued from Samsung or the carrier.
TETHER: Connecting the Android device to a computer via a wired or wireless connection to allow the transfer of data through the Android device's internet connection. Commonly used to provide internet access to a laptop or desktop computer when other methods are not desired or available.
THEME: A collection of images, backgrounds, colors, font types, and other visual items to change the Android device's look and feel. Separate from LAUNCHER, and is usually FLASHed in CWM.
TIBU: Short for Titanium Backup. See TITANIUM BACKUP.
TITANIUM BACKUP: A backup utility available in the Android Market that allows users to back up their applications, the saved data for the applications, and system settings.
TRIANGLE AWAY: An app developed by Recognized Elite Developer Chainfire that resets the FLASH COUNTER to zero, removing evidence of software modification.
UNDERVOLTING: Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
UV: Short for Undervolting. See UNDERVOLTING.
WCDMA: Short for Wideband Code Division Multiple Access. An air interface standard in 3G mobile communications networks that allows higher speeds and more users.
WIPE PACKAGE: A rom package that will format the portions of the Android device where the user's market apps are stored, in addition to any updates to the system folders. After a wipe package is installed, the user will have to restore apps from a backup or redownload them from the Android Market. See also NO-WIPE PACKAGE.
ZIPALIGNED: An archive alignment tool that provides important optimization to APK files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Reduces RAM consumption.
ROMS:
Note: These are only ROM names that use acronyms, not a complete ROM listing
CM: CyanogenMod. See "CM" in Android Device Related section.
MIUI: A Chinese built-from-source ROM. Short for "Mobile Internet User Interface". Also can refer to the MIUI music player, which has been included in other ROMs.
If I've incorrectly identified what something is or does, please let me know so I can update this post with the correct information. If you can think of any other terms or acronyms that should be included, let me know, and I'll put them up here. I've tried to give credit where it's due by direct linking, but if I've copied something and not cited properly, point it out and I'll update it.
Everyone should have to read this before trying to flash a ROM.
Ota?
What does ota stand for?
UnicOrnseeD said:
What does ota stand for?
Click to expand...
Click to collapse
Over the air, as in updates downloaded wirelessly.
Sent from my SGH-I747 using Tapatalk 2
great informative post! it deserves a sticky! this should be the first thing anyone reads before joining the forum :good:
edit:
what are inverted gapps? what's the difference between normal gapps and inverted?
OP great info here, Stuck and Thread cleaned. Thank You.
Thanks for the thread!
Subcribed because awesomeness.
Props friend youbput a lot of commendable time into this.
Fantastic job.
:thumbup:
Sent from my SGH-I747 using
:thumbdown: Crapatalk fail app 2 :thumbdown:
paid app with adds now?? seriously?!?
nlºlm
:banghead:
dd
I have come across the term "dd" a few times. May I inquire as to its meaning?
WavyA70 said:
I have come across the term "dd" a few times. May I inquire as to its meaning?
Click to expand...
Click to collapse
Daily driver. One you feel you will keep a while. The taboo one is deal beaker...ask any dev ..daily driver is a compliment though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what does ''OTG'' means? just saw a post today couldn't find the answer anywhere :/
ravike14 said:
what does ''OTG'' means? just saw a post today couldn't find the answer anywhere :/
Click to expand...
Click to collapse
OTG stands for "On The Go" it refers to the USB standard. Usually people use it to talk about a USB cable that you can plug into your phone and then plug things like hard drives, keyboards, game controllers, and other things into the cable to then the above mentioned devices with your phone.
Sent from my SCH-I535 using xda premium
shimp208 said:
OTG stands for "On The Go" it refers to the USB standard. Usually people use it to talk about a USB cable that you can plug into your phone and then plug things like hard drives, keyboards, game controllers, and other things into the cable to then the above mentioned devices with your phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
thanks also this is not anything related to android but how to post a link with it's name not the whole link which that name redirect to the link?
ravike14 said:
thanks also this is not anything related to android but how to post a link with it's name not the whole link which that name redirect to the link?
Click to expand...
Click to collapse
To do this with a link you can hit the insert link button and input the link you want to link to then highlight the area outside the brackets that looks similar to this and put the word or phrase you want the link to work for, example:
xda-developers
I linked to the xda main page but rather then the full link being displayed it only displays xda-developers for the phrase. To change it you could do:
your text to display here
I would also recommend taking a look at this thread http://forum.xda-developers.com/misc.php?do=bbcode that tells you how to link urls that show only words and all the other things you can do with BB code when posting on XDA.
Sent from my SCH-I535 using xda premium
shimp208 said:
To do this with a link you can hit the insert link button and input the link you want to link to then highlight the area outside the brackets that looks similar to this and put the word or phrase you want the link to work for, example:
xda-developers
I linked to the xda main page but rather then the full link being displayed it only displays xda-developers for the phrase. To change it you could do:
your text to display here
I would also recommend taking a look at this thread http://forum.xda-developers.com/misc.php?do=bbcode that tells you how to link urls that show only words and all the other things you can do with BB code when posting on XDA.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
thanks alot what are Gapps?? also KDH gapps?? sorry if both are the same
BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. pushing volume down, home, and the power button for 10 seconds will reboot into the RECOVERY menu). 3-Button Combo is a common example. May also be referred to as a "Chord".
Click to expand...
Click to collapse
Actually that puts it in download mode
ravike14 said:
thanks alot what are Gapps?? also KDH gapps?? sorry if both are the same
Click to expand...
Click to collapse
Gapps= google apps.. or bad clothing sold by a retailer that employs slave labor.
TeknoGodz said:
Actually that puts it in download mode
Click to expand...
Click to collapse
Op corrected, don't know how those got mixed up
Very useful info
Thank you very much for taking the time to give us this information. It is very helpful.
I've looked several times but what is "d2att"?
Sent from my SGH-I747M using xda app-developers app
I have an AT&T Galaxy S7 Active - US Model - SM-G891A
I haven't seen any credible sources with a root for this device. From what I can tell, it is identical to the Qualcomm version of the Galaxy S7(non-edge) with one exception; The S7 Active has the "Active button".
Since almost every Qualcomm variant of the Galaxy S7 has been rooted, is there a chance that the S7 active is rootable? or is there already a root?
Let me know if you need any other information or if you would like a test dummy.
UPDATE: Successful Root Of the Galaxy S7 Active (Qualcomm)
PLEASE USE THE POLL TO LET US KNOW WHAT VERSION OF FIRMWARE YOU END UP ROOTING. IF YOU FAIL, PLEASE PROVIDE US WITH AS MUCH INFORMATION, ABOUT YOUR EXPERIENCE, THAT YOU CAN. THIS WAY WE CAN DO OUR BEST TO HELP YOU AND CONTINUE IMPROVING THIS ROOT.
ROOT - CLICK BELOW
Original Tutorial Credit(HERE)
Updated for Galaxy S7 Active (by NotSoMiniGun)
Make sure you have downloaded these files:
• SuperSU v2.74 (updated) SuperSU v2.76
• Modified ODIN
• Unlock boot.tar
• Fastboot
• Samsung Official USB Drivers v1.5.40
Make sure you meet these requirements:
• Firmware PG7, PH2, PI2, PK2, PL1(6.x.x only)
• NO NOUGAT SUPPORT YET (1/30/2017)
• >60% Battery charge
Additional suggestions and warnings:
• Make sure you know both your Samsung account info and your Google account info. You will need these, for Factory Reset Protection, if something goes wrong and you need to wipe your phone.
• I, also, recommend rooting a clean/wiped/reset phone. This rules out quite a few things that could cause failures or strange behavior during or after the rooting process.
• You WILL lose some speed and battery life. This is not an optimized root. If you are comfortable with that fact, then go ahead. You’ve been warned. Do not complain about it on this thread.
• Install the Samsung drivers even if your computer already seems to have them. Right click and run the .exe as administrator. REBOOT after install. This rules out another potential point of failure.
• MAKE SURE YOU ONLY HAVE YOUR PHONE PLUGGED IN. Make sure there are as few USB devices, as possible, plugged into your computer during the rooting process.
• DISABLE YOUR ANTI-VIRUS
Step 1:
Read EVERYTHING above. Twice.
Step 2:
Open Settings->About Device and scroll down to “Build Number”. Tap it repeatedly until it says you have activated “Developer Mode”.
Step 3:
Open Settings->Developer Options and turn ON both “USB Debugging” and “OEM Unlock”.
Step 4:
Turn phone OFF. Once off, hold (Volume Down, Center Home, and Power) until you see a blue warning screen.
Step 5:
Press Volume Up and plug your phone into your computer. You should have blue screen that says “Downloading”.
Step 6:
All of the files should be downloaded to your computer and be sitting in your “Downloads” folder. Un-zip the ODIN-modified.zip, right click the ODIN .exe, and run as administrator.
IF YOU DON’T SEE A BLUE BOX AT THE TOP LEFT OF ODIN THEN DO THESE STEPS AGAIN:
1. Run the Samsung USB Drivers .exe again.
2. Reboot your computer.
3. Make sure your data cable isn’t damaged and is plugged in all the way.
Step 7.
Select AP and choose the ENG Boot file ending in .tar. Then click “Start”. The blue box should eventually turn green and say “PASS”.
IF YOU GET STUCK IN A BOOT LOOP:
“If your phone ends up in a bootloop (which most likely will), you will need to do a factory reset. To do this, hold down Volume Down, Center Home, and Power buttons together until your phone resets then quickly switch the Volume Down to Up key while holding the rest of the buttons down until you see “Recovery booting” at the top-left of the screen. If you mess up, don’t worry you can keep trying until you get it right. Once in stock recovery, choose “Wipe data/factory reset” then “yes” to do a factory reset. THIS WILL ERASE EVERYTHING ON YOUR PHONE! Reboot and after 5-10 minutes, you should be welcomed by a welcome screen, go ahead and login.”
Step 8:
Go through the set-up screens until you can repeat Steps 2 & 3.
Step 9:
Unzip fastboot.zip to its own directory. Unzip the contents of SuperSU and copy them to the fastboot folder.
Step 10:
Shift-RightClick in the white space below the files in the fastboot folder. Click “Open Command Window Here”.
Step 11:
Type the following in the Command Prompt:
Code:
adb devices
Code:
root.bat
Watch your phone for any messages and make sure to tap OK. If it freezes, unplug your phone, plug it back in, and restart from Step 10.
Step 12:
Install BusyBox from the app store. Open the app and make sure it installs to “/system/xbin”. DO NOT INSTALL IT ANYWHERE ELSE. THIS WILL CAUSE PROBLEMS AND REQUIRE A FLASH AND RE-ROOT.
Step 13:
You are now successfully rooted. Read the rest of this post carefully to fix the following items:
WiFi password reset
SecurityLogAgent
General Lag and other issues.
TO UNROOT - CLICK BELOW
Link to Instructions Provided By (jembot)
WARNING:
DO NOT uninstall "SecurityLogAgent", DO freeze it using Titanium Backup. Uninstalling it seems to cause instability and random system crashes.
DO NOT attempt to update SuperSU BINARY UPDATE:You can update to v2.76 from v2.74 with the provided file (updating the app is also ok) after root. Other attempts to update will break WiFi, Cellular Data, Access to the Play Store, and will require a reflash in ODIN to regain functionality.
If you do accidentally do this, just reflash to PI2 firmware and check for OTA updates, or use the update packages, to bring your device back to PL1 Firmware. It will lag a lot, so be patient.
FIRMARE AND PACKAGE DOWNLOAD LINKS
PI2 Firmware Download Password: G891AUCS2API2_FULL_FSFD (Cost me $10 lol)
PG7 Firmware Download
PG7 to PH1 Update
PH1 to PI2 Update
PI2 to PK2 Update
PK2 to PL1 Update
PI2 to PL4 Update
PK2 to PL4 Update
PL1 to PL4 Update
SuperSU v2.74
SuperSU v2.76
Modified ODIN
Unlock boot.tar for PL1 or earlier (credit activefan01)
Original boot.tar for PL4 (use if updating to nougat)
imsservice.apk (use to remove VoLTE and RCS icons)
Fastboot (bundle used in the rooting tutorial)
Samsung Official USB Drivers v1.5.40
Other Issues and Solutions:
If you get and MD5 error:
Your download for the tar file was probably incomplete or corrupt. To fix, re-download and make sure it downloads completely before trying again.
If ODIN does not recognize the file or doesn't display it in the browser:
The file should end in a .tar extension, not a .MD5 extension. Use THIS tutorial to show file extensions in windows(if you can't see them), and make sure the file ends in .tar
If you still experience significant lag or battery usage:
1. Try any of the suggested CPU governor apps on this thread.
2. I, personally, noticed the biggest improvement with Device Control [root] from the play store
3. Enable - Power Efficient Workqueue
Enable - LCD power reduce
Core Limits - 1593 MAX - 307 MIN and Lock Frequencies
Governor - Interactive and Lock Governor UPDATE: "PERFORMANCE" seems to work significantly better at removing lag and, surprisingly, saving battery
Enable - Automatic FStrimming
Enable - Core Control and MSM-Thermal
Enable - Reapply on boot with a 15 second delay
4. Under developer options, consider setting all of the animation speeds to 0
5. As always, you are responsible for any damage to your device or data
For those of you who want Xposed:
1. Install Flashfire from the Play Store
2. Put these 2 files on your phone FRAMEWORK and APK
3. Use Flashfire to flash the zip to your phone.
4. Install the APK and Reboot.
5. Enjoy
6. Avoid these modules or risk bricking your phone:
- Gravitybox - Confirmed
- Xblasttools - Confirmed
For those of you who want to Tether/Hotspot:
1. Install XTether in Xposed
2. Activate and Reboot
3. The native hotspot/tether options will now work in settings
4. Enjoy more.
If you have issues with AT&T keeping you from setting up your phone:
1. Make sure you connect to WiFi on first step of the Samsung setup
2. Do the normal setup until you get to the AT&T Setup portion
3. Let the setup "scan" for connections on WiFi
4. Dismiss the warning about limited WiFi and turn the WiFi OFF
5. Proceed with the rest of the setup by hitting NEXT or SKIP when available
6. You should now be able to use your phone and should be able to setup all AT&T related software separately.
To fix WiFi password reset issue:
1. Install BuildProp from the Play Store
2. Change the value of ro.securestorage.support=false
3. Save, reboot, enter WIFI password for the last time!
How to remove the VoLTE and RCS(hurricane looking thing) icons: (tested by FtaWolf)
1. Install a file explorer like FX
2. Set Read/Write access to System Partition, use the 3 dot menu in the top right
3. (be careful not to touch anything else, I soft-bricked my phone twice on accident)
3. Navigate to /system/priv-app/imsservice
4. Rename file imsservice.apk to imsservice.apk.bak, tap and hold to rename
5. Copy THIS file into the same folder
6. Then set permission to 644, again, tap and hold to change permissions
7. Reboot and you should be good to go.
How to add HotSpot and MobileData toggles or remove unwanted toggles (credit slimshouki)
1. Install CSC Feature Expert from the PlayStore
2. Scroll down until you find "Config Def Quick Setting Item" (Do not search for it, you wont find it)
3. Add " ,WiFiHotspot,MobileData"
4. (OPTIONAL) Delete any toggles you don't want. Make you there is a single comma between all values
5. Open Settings->Personal->Backup and Reset->Reset Settings
6. After it reboots you should see the toggles.
COMPATIBILITY STATUS:
Galaxy S7 & S7 Edge Qualcomm Variant Root: Confirmed Successful On: PG7, PH2, PI2, PK2, PL1 || Fails On: PL4, Android 7.0 Update
Poot Debug APK Qualcomm Root: Incompatible
Dirty Cow Exploit: Temp/Partial Root
TO DO:
Determine Root Method/Source (activefan01, perhaps you can weigh in)
Custom Recovery (if possible)
Optimize Current Root Method (currently takes a decent toll on battery life)
7.0.0+ Root (currenty only works on pre-nougat systems)
If no one has any answers on the availability of a functioning root for the Samsung Galaxy S7 Active, can some one tell me why the Active series of phones seem to be actively ignored? Is there an extreme difference in hardware? Is it difficult for devs to get their hands on the device? Is there not enough interest?
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
br0adband said:
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
Click to expand...
Click to collapse
I'm only getting 4hrs of sot..... Hmm
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
I am also searching for root. I got some link in google search, but they are not working. I bought this unlocked device in India. While it works fine with old network, but it does not work with new network which are purely 4g and use voice over LTE for calls.
Sent from my SAMSUNG-SM-G891A using Tapatalk
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
I need to put Indian CSC on this phone.
Sent from my SAMSUNG-SM-G891A using Tapatalk
br0adband said:
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
Click to expand...
Click to collapse
Would you be willing to compile a list of all the packages you disabled? Maybe then I can get better battery life.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Here's the list as XML and it's attached as well for import to Package Disabler Pro:
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.mobeam.barcodeService</string>
<string>com.monotype.android.font.rosemary</string>
<string>com.matchboxmobile.wisp</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.samsung.android.app.galaxyfinder</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.samsung.svoice.sync</string>
<string>com.drivemode</string>
<string>com.sec.android.app.clipvideo</string>
<string>com.sec.android.devicehelp</string>
<string>com.android.wallpapercropper</string>
<string>com.sec.android.app.wfdbroker</string>
<string>com.att.android.digitallocker</string>
<string>com.samsung.android.app.withtv</string>
<string>com.sec.android.app.safetyassurance</string>
<string>org.simalliance.openmobileapi.service</string>
<string>com.samsung.android.easysetup</string>
<string>com.android.externalstorage</string>
<string>com.sec.android.easyonehand</string>
<string>com.sec.factory</string>
<string>com.cequint.ecid</string>
<string>com.directv.dvrscheduler</string>
<string>com.samsung.android.qconnect</string>
<string>com.amazon.mShop.android.install</string>
<string>com.sec.android.app.tourviewer</string>
<string>com.sec.android.Kies</string>
<string>com.samsung.faceservice</string>
<string>com.monotype.android.font.foundation</string>
<string>com.sec.android.widgetapp.easymodecontactswidget</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.firmware.tsp</string>
<string>com.google.android.configupdater</string>
<string>com.sec.android.app.billing</string>
<string>com.sec.android.app.minimode.res</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.samsung.android.slinkcloud</string>
<string>com.dti.att</string>
<string>com.dsi.ant.service.socket</string>
<string>com.sec.android.AutoPreconfig</string>
<string>com.sec.android.app.soundalive</string>
<string>com.samsung.android.securitylogagent</string>
<string>com.android.carrierconfig</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.app.assistantmenu</string>
<string>com.locationlabs.cni.att</string>
<string>com.samsung.SMT</string>
<string>com.samsung.aab</string>
<string>com.samsung.vvm</string>
<string>com.sec.android.ofviewer</string>
<string>com.samsung.hs20provider</string>
<string>net.aetherpal.device</string>
<string>com.sec.att.usagemanager3</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.samsung.android.smartface</string>
<string>com.android.mms</string>
<string>com.android.backupconfirm</string>
<string>com.sec.android.app.SecSetupWizard</string>
<string>com.hancom.office.editor.hidden</string>
<string>com.sec.bcservice</string>
<string>com.android.calendar</string>
<string>com.samsung.android.providers.context</string>
<string>com.sec.android.preloadinstaller</string>
<string>com.sec.android.uibcvirtualsoftkey</string>
<string>com.samsung.android.sdk.professionalaudio.utility.jammonitor</string>
<string>com.android.sharedstoragebackup</string>
<string>com.yellowpages.android.ypmobile</string>
<string>com.samsung.android.app.colorblind</string>
<string>com.android.printspooler</string>
<string>com.android.dreams.basic</string>
<string>com.att.myWireless</string>
<string>com.sec.android.app.dictionary</string>
<string>com.samsung.android.app.talkback</string>
<string>com.samsung.android.game.gametools</string>
<string>com.asurion.android.mobilerecovery.att</string>
<string>com.sec.smartcard.manager</string>
<string>com.sec.allsharecastplayer</string>
<string>com.samsung.app.slowmotion</string>
<string>com.samsung.android.smartcallprovider</string>
<string>com.directv.promo.shade</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.samsung.android.personalpage.service</string>
<string>com.samsung.advp.imssettings</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.sec.android.app.clockpackage</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.sm</string>
<string>com.sec.android.widgetapp.locationwidget</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.samsung.android.controltv</string>
<string>com.samsung.mdl.radio</string>
<string>com.sec.spp.push</string>
<string>com.dsi.ant.server</string>
<string>com.samsung.android.gamepad.service</string>
<string>com.samsung.android.allshare.service.fileshare</string>
<string>com.synchronoss.dcs.att.r2g</string>
<string>com.sec.android.mimage.photoretouching</string>
<string>com.samsung.android.universalswitch</string>
<string>com.samsung.helphub</string>
<string>com.sec.android.app.sns3</string>
<string>flipboard.boxer.app</string>
<string>com.google.android.feedback</string>
<string>com.google.android.apps.photos</string>
<string>com.android.managedprovisioning</string>
<string>com.sec.android.providers.tasks</string>
<string>com.ubercab</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.android.dreams.phototable</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.samsung.app.highlightplayer</string>
<string>com.sec.android.app.vepreload</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.cleanmaster.sdk</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.android.wallpaper.livepicker</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.amazon.mShop.android</string>
<string>com.samsung.android.app.FileShareClient</string>
<string>com.facebook.system</string>
<string>com.sec.android.soagent</string>
<string>com.samsung.android.fmm</string>
<string>com.samsung.android.mdm</string>
<string>com.smlds</string>
<string>com.ws.dm</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.app.newtrim</string>
<string>com.samsung.android.spay</string>
<string>com.sec.hearingadjust</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.sec.android.splitsound</string>
<string>com.wssnps</string>
<string>com.samsung.android.app.watchmanagerstub</string>
<string>com.policydm</string>
<string>com.samsung.android.app.FileShareServer</string>
<string>com.enhance.gameservice</string>
<string>com.americanexpress.plenti</string>
<string>com.sec.svoice.lang.es_US</string>
<string>com.lookout</string>
<string>com.samsung.android.sm.provider</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.android.bluetoothmidiservice</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.voiceserviceplatform</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.android.app.mt</string>
<string>com.sec.knox.switcher</string>
<string>com.qualcomm.atfwd</string>
<string>com.sec.android.app.magnifier</string>
<string>com.samsung.android.video</string>
<string>com.amazon.kindle</string>
</disabledPackages>
</importExportSetting>
Thank you. I'm going to mess around with it later.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Here first run with sot with S7 Active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-G891A using Tapatalk
FtaWolf said:
Here first run with sot with S7 Active.
Click to expand...
Click to collapse
That's awesome, really it is, but what does that have to do with this thread and rooting it?
br0adband said:
That's awesome, really it is, but what does that have to do with this thread and rooting it?
Click to expand...
Click to collapse
Not thing. What did disabled package pro have do with thread. You didn't ? It.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Back On Track
While I agree the S7 Active is a fantastic phone with fairly substantial battery life, those merits should be discussed in another thread such as HERE. The main goals of this thread are:
1. Determine if there is an available Root for the Samsung Galaxy S7 Active
2. Determine if any current exploits, for other models, could be modified to Root the S7 Active
- The Galaxy S7 (snapdragon model) Root
- Dirty Cow
- etc.
3. To offer help or a reward to anyone willing to make progress on this topic.
I personally am wiling to donate $50+ to anyone able to provide a legitimate root (or to a charity of their choice).
Please let me know if there is an official way of presenting a bounty or if there is any other way I can help progress this project.
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
-snip-
Poot
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
NotSoMiniGun said:
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
Click to expand...
Click to collapse
Most likely not as that is an old method. You could try the method mentioned a few posts up.
Sent from my SAMSUNG-SM-G891A using Tapatalk
first of all, I apologize for my "English", I had to use google translator.
I am edu present, I'm from Argentina, and was looking for information on how to root the s7 active, no luck, but I found information that perhaps more experienced people can help them find a solution ....
Qualcomm Quadrooter Exploit
QuadRooter Android sounds like another serious security exploit. Which one can allow a malicious app Apparently to gain root access based on Qualcomm Android phones and tablets, enabling the app to do pretty much what Then it pleases. , According to Check Point, the research group discovered That QuadRooter, up to 900 million Android devices Qualcomm Could be AFFECTED. This exploit targets the drivers Qualcomm Which is why it is specific to this hardware. As of the 1st Augusts security update Google has patched 3 of the 4 will patch vulnerabilities and the last one in the September 1st update. To keep your device safe from bugs it is always in Original bests to stay on top of your security updates. One of the best ways to protect your phone from malicious software is to download apps only from trusted sources or google play.
If you want to check and see if your device can possible be vulnerable to this threat Then you can download and run QuadRooter Scanner by check point. Personally I am hoping That a developer can figure out this exploit and use it to get many android users root access. I am sure someone can create a app gets root then a INJECTS That SuperSU and their binary into the device. If you are hoping for the same I recommend not updating to new security patches and give the developers some time to get root access devices.
I would not be surprise to see this QuadRooter vulnerability Implemented into Kingroot app some time soon, as it would make there app on Android devices unstoppable. What do you think about this bug please comment below and let me know.
This information I found in rootjunky.
I hope you can serve something
---------- Post added at 01:58 AM ---------- Previous post was at 01:45 AM ----------
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
how did it go?
I tried it but not got success.
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
That's awesome! Now, who is familiar with Linux... can dump boot.img and kernel.img from the phone...
I found that it's here:
cd dev/block/platform/soc/624000.usfshc/by-name/
dd if=/dev/block/sda6 of=/sdcard/efs.img
dd if=/dev/block/sdd10 of=/sdcard/aboot.img
dd if=/dev/block/sda13 of=/sdcard/fota.img
dd if=/dev/block/sda16 of=/sdcard/modem.img
dd if=/dev/block/sda17 of=/sdcard/boot.img
dd if=/dev/block/sda18 of=/sdcard/recovery.img
I don't know, will these comands work in linux?