Windows Phone 7 has standardized the bootloader requirements for OEMs. No longer will an OEM be allowed to implement it's own design for ROM deployment (such as HTC with the .nbh/RUU system, .dz/LGMDP with LG, etc.)
The image format will be B000FF/.bin, which receives only minor changes from CE5, and so our current tools should work fine with this. The major change is in the way the bootloader handles image deployment. For Samsung and a handful of other manufacturers, this won't change too much, as they already utilize the B000FF system for deployment. The filesystem inside will be IMGFS - no longer will BinFS be used for NK/XIP section (now IMGFS will all partitions on device, NK and OS just being split by package rather than a seperate FS)
The physical flash layout will look as follows:
Reserved Regions, updateable only through a special oem-written driver to allow access to this area (size varies)
Partition Table (1KB)
BLDR (1MB)
DBSP (Device Boot State Partition, 256KB)
DPP (Device Provisioning Partition, 256KB)
USP (Update State Partition, 2MB)
ULDR1 (>=6MB)
ULDR2 (>=6MB)
NK (IMGFS, >=4.5MB) - At least 1MB free space for updates
OS (IMGFS, >=181MB) - At least 20% free space for updates
User Store (TexFAT)
Only the User Store (Which uses new Transaction-Safe ExFAT filesystem) will be user-writeable, all other areas will only be writable during an update operation. The Partition Table, DBSP, DPP, USP, and User Store are all not updateable during an update operation, only during a full-flash scenario. B00FF images are signed and checksummed, and passed through to the bootloader via ethernet over usb. The connection will most likely be encrypted, using the same flashing utility as Zune HD. (This is currently used to deploy images to the DevKits)
.ffu (Full Flash Update) file format (XML) will be used to pass information to the Zune software on which partitions are to be updated, etc. FFUs are signed just as .cabs are signed and only an .ffu which passes validation against the certificates on-device will be allowed to update a device.
Updates can also be done on a per-package basis, using the ImageUpdate process, which I have described in length @ the XDA WinMo Software Development forum. This process is largely unchanged from WinMo 6.x with the addition of a policy xml file containing security policy settings related to the .cab.pkg being deployed.
As such, I would recommend anyone interested in cracking the bootloader and creating a "HardSPL" take a good hard look at the Zune HD.
Similar to CE5/WinMo 6.x, There is a BLDR (Base Boot Loader) which makes the initial determination to boot up to the ULDR or to the WP7 OS. The OEM implements alternate boot parameters to trigger this and/or a button press combination. If ULDR is triggered, it checks the battery and power source to ensure that there is enough life remaining to successfully complete the flash, then awaits the flash download. There are redundant ULDR partitions (ULDR1/ULDR2) to facilitate failsafe recovery in the event of a failed ULDR flash (ULDR provides a basic level of functionality to enable a recovery flash even in the event of power failure during a flash)
MSFT is pushing it's Phone Update service much harder this time - it is intended to be used as the primary method for distributing phone updates. These can be deployed both over-the-air and through a USB connection with the Zune software.
subscribe to this......need to learn before my next device.
Thanks. I didn't see these threads before. Any chance you could share or point to the docs this info came from? It seems tweakers.net acquired it and I wouldn't mind looking through.
saved for future use! Da_G is the master of the roms!
As Usual Da_G you are cool..
Will you make this thread a Sticky for us? Thanks again G.
da_g said:
bump for visibility
Click to expand...
Click to collapse
bump! Bump! Bump!
Da_G you always rock, now we got a huge info.
thanks for your infos
that is some good news eventually have custom ROMs on wp7
thanks!!!!!
So you are saying that we will be able to cook for WM7, but wont be able to get a HSPL to flash it?
Well done Da_G.
Da_G said:
...
.ffu (Full Flash Update) file format (XML) will be used to pass information to the Zune software on which partitions are to be updated, etc. FFUs are signed just as .cabs are signed and only an .ffu which passes validation against the certificates on-device will be allowed to update a device.
Updates can also be done on a per-package basis, using the ImageUpdate process, which I have described in length @ the XDA WinMo Software Development forum. This process is largely unchanged from WinMo 6.x with the addition of a policy xml file containing security policy settings related to the .cab.pkg being deployed. As such, I would recommend anyone interested in cracking the bootloader and creating a "HardSPL" take a good hard look at the Zune HD...
Click to expand...
Click to collapse
Hi Da_G,
How can I get my hands on these files: not wp7 os but the other partition (dpp/bldr/uldr/imgfs/etc) contents? What IS known about wp7-fs? spl?
Do you have ANY dumps - even ZuneHD equiv? maybe the source of your .ffu info and an actual .ffu? Thanks there- pm me if you get the time. Yeah... I am noob here but interested in moving into rom-dev; used to do xbox-1+live and do have jtag, logic analyzers+trace, etc here. How would I begin? Once again: thanks and well done!
Edit/Update:
Perhaps with Cotulla's partition layout over 4 seperate nand areas it would be an option to modify this and his wp7 spl because the activation thing happened AFTER (live activation hack around etc) he had finished leo70 release and then..........
-whilst jtag/usb or eth/debug happening- (obviously you'd though of this b4- im just theorizing- let me know if way off)- to take a HTC HD2 (LEO70) that HAS BEEN ACTIVATED ON LIVE and see where/how/when/with/which partitions, filesys, regkeys, etc, have pvk for live or the ffu and then insert a test cert like ur own xbmod/chevron. or whatever is in sdk for 7 or ce. and then utilize this to diff and comp. I dont see why not. Then .ffu then self signature.
Now THAT'S cool! Thanks, Da_G!
This would mean, that we basically could get custom Rom's on WP7. Can't wait to see the first ones
Interesting info. Subscribing to it now....
Thanks or the info Da_G!!!
eh?
Did you look at the post dates before you all started subscribing? Almost a year now, doubt you'd see anything new ... but this and more 'subscribed' and a possible 'sod off' post.
Is this the only discussion on the topic? I'm sure im not the only one looking forward to having an unlocked bootloader. Any updates?
surrender420 said:
Is this the only discussion on the topic? I'm sure im not the only one looking forward to having an unlocked bootloader. Any updates?
Click to expand...
Click to collapse
See the first thread in this sub-forum.
Related
Here we go!
3 Relevant partitions on the Zune HD:
ZBoot
NK
EXT
(there's actually a 4th partition, but it's a recovery partition for NK to facilitate fail-safe updating)
Enjoy
(a note: some files appear to be damaged, its my first time dumping a CE 7/Zune HD ROM )
(another note: thanks to nd4spd for getting the rom update to me, i don't have a zune hd )
wow I'll take a look.
Anything usable?
These executables are designed for CE 7 and more than likely will not work at all on CE 5 (although things coded for .NET might)
Really, you tell me, though, I haven't actually tried
Awesome! Subscribed...
Wait...so you're telling me it might be possible to create custom roms on the zune hd?!?! i need them to come out with a 128 gb model asap then...
WOW....they were trying to dump a zune rom for years.... so this means the protection on the zune HD is not nearly as strong as the regular zune...this is good news indeed...Mine is on backorder still =x
Another quick Q, did you dump that yourself or find it somewhere?
been trying to find this for a few weeks
looking forward to see what can be done!
are the keyboard files in a format that we can use on windows mobile phones?
votum said:
Another quick Q, did you dump that yourself or find it somewhere?
Click to expand...
Click to collapse
Actually, all I did was reset my Zune HD in recovery mode and plugged it in. When the Zune Software detected it, it downloaded the ROM from MS. When I was defragging my computer a few days earlier, I happened to find the folder where it saved all of the Firmware Updates. So I just looked in that folder and found the FirmwareUpdate.cab that had the .bin files in it.
after messing around with it, looks like nothing can really be recmoded to make dll files. it may need another way to rec mod than in the vk.
So does this mean that the Zune HD will be unlocked shortly?!
Blackwheel said:
So does this mean that the Zune HD will be unlocked shortly?!
Click to expand...
Click to collapse
and does this mean that we will have Zune GUI on winmo devices ?
benko286 said:
and does this mean that we will have Zune GUI on winmo devices ?
Click to expand...
Click to collapse
That could take some time, but once we are able to read the files, i will try to work on a keyboard
setix said:
That could take some time, but once we are able to read the files, i will try to work on a keyboard
Click to expand...
Click to collapse
How about unlocking the Zune HD? Or is that a completely different animal?
Somebody please sticky this thread immediately. This can only lead to great things!
Blackwheel said:
How about unlocking the Zune HD? Or is that a completely different animal?
Somebody please sticky this thread immediately. This can only lead to great things!
Click to expand...
Click to collapse
Err.. forgive my ignorance.. but is Zune HD locked?
In what way?
I think what he means by unlocking is to unlock for ROM modification and development.
ND4SPD said:
When I was defragging my computer a few days earlier, I happened to find the folder where it saved all of the Firmware Updates. So I just looked in that folder and found the FirmwareUpdate.cab that had the .bin files in it.
Click to expand...
Click to collapse
The ROM is saved in a .cab file to %HOMEPATH%\AppData\Local\Microsoft\Zune\Firmware Updates
7-Zip or another unzipping software can extract it out into the 4 .bin files, ext.bin, nk.bin, recovery.bin, and zboot.bin.
I have not yet succeeded to breaking it down into DLLs, it seems like there are multiple DLLs compiled into one .bin file.
Interestingly enough, some of the plaintext I saw in the recovery file was associated with camera/photography code (do a ctrl-f for "autofocus" or "lens" in the recovery.bin file in wordpad). However, I'm guessing it is the remnants of WinCE code, not for the Zune HD (or a successor?). It still begs the question of why it would be included in the recovery code though...
Hope that someone can use this for something...
hairchrm said:
The ROM is saved in a .cab file to %HOMEPATH%\AppData\Local\Microsoft\Zune\Firmware Updates
7-Zip or another unzipping software can extract it out into the 4 .bin files, ext.bin, nk.bin, recovery.bin, and zboot.bin.
I have not yet succeeded to breaking it down into DLLs, it seems like there are multiple DLLs compiled into one .bin file.
Interestingly enough, some of the plaintext I saw in the recovery file was associated with camera/photography code (do a ctrl-f for "autofocus" or "lens" in the recovery.bin file in wordpad). However, I'm guessing it is the remnants of WinCE code, not for the Zune HD (or a successor?). It still begs the question of why it would be included in the recovery code though...
Hope that someone can use this for something...
Click to expand...
Click to collapse
To break it down, you need to use cvrtbin.exe to convert it to the .nb0 format. Once you have that, as Da_G pointed out to me, you can use Xipport.exe's dump xip function to dump whichever converted file. Unfortunately, xipport has an error on the last file, so I'm going to try to fix that this evening.
You can also view the files in Da_G's first post
ND4SPD said:
To break it down, you need to use cvrtbin.exe to convert it to the .nb0 format. Once you have that, as Da_G pointed out to me, you can use Xipport.exe's dump xip function to dump whichever converted file. Unfortunately, xipport has an error on the last file, so I'm going to try to fix that this evening.
You can also view the files in Da_G's first post
Click to expand...
Click to collapse
Ahh... haha, I thought he linked to the raw .bin files and I figured that it would be easier to grab them from your own computer than download them. Whoooops!
I am curious, has anyone disected the Zune HD Hardware? I wonder what extra hardware got left behind that is not currently activated (and possilby not licensed). The core chipset can handle all of the common peripherals that you might find in a WM7 class phone chasis.
At the very least you should be able to see the sort of antenna and amps in there.
the Imageupdate system clearly works, so one approach to updating it (unlocking and or removing security) is to use the imageupdate system (on device or from your desktop, or possibly OTA). Although you would need to know a good bit about the NK and zloader for wm7. WM7 is a more streamlined, efficifient design, but - unfortunatey - there is a lot more in the kernel which makes updating individual bits more difficult without a full link.
It is a little bit more like the X360 design in this sense.
I believe that imageupdate is only known the to the end users as the engine for Windows Phone Update or -previously - FOTA (firmware over the air)
As Da_g mentioned, this is the first commercial device (to my knowledge) to use WCE7/WM7 (in general, WM is just a big OAK on WCE)
What certs are in the full CAB?
Hi all - want to know what the status is on a hspl for wp7 and if can help and wondering how live pvk and id goes to phone in hd2-wp7 situation where no real device provisioning partition exists?!?!?!??! This leads me to think that maybe:
Perhaps with Cotulla's partition layout over 4 seperate nand areas it would be an option to modify this and his wp7 spl because the activation thing happened AFTER (live activation hack around etc) he had finished leo70 release and then..........
-whilst jtag/usb or eth/debug happening- (obviously Da_G etc thought of this b4- im just extrapolating further on this now live done after dft released- let me know if way off)- to take a HTC HD2 (LEO70) that HAS BEEN ACTIVATED ON LIVE and see where/how/when/with/which partitions, filesys, regkeys, etc, have pvk for live or the ffu and then insert a test cert like ur own xbmod/chevron. or whatever is in sdk for 7 or ce. and then utilize this to diff and comp. I dont see why not. Then .ffu then self signature.
If anyone is looking at doing this and needs hardware or I can help let me know thanks. Also:
Anyway to DUMP the newly-activated after-hack after-key after-ms-call hd2 wp7 contents completely? Any news on this unknown filesystem and sd jbod with nand? If a way to extract device provisioning partition etc. Not interested so much in live but more HSPL-for-WP7 creation to allow custom roms. Can not seem to find much on this. Anyone got ideas on own signature or other method using pre-existing leo70 nand parts as workaround maybe?
For the record - I have used a singled live key from Microsoft activation phone call more than 4 times on 2 devices and it works fine over and over: you have to consider fact that if vendor or product id was misflashed at factory onto DPP then every hardreset would not wipe this (unsure)? causing you to call microsoft again and ask for another key? eitherway:
does ne1 know what the key over the phone from microsoft is actual doing? is this key taken with say imei or serial of phone and maybe your @live.com unique GUID and seeded or used with hash or some algorithm to produce a pvk for device provisioning partition? or it simply override and enable live? are there only one type of activation key over phone? seems there could be ones maybe based on your live address+guid and ones that completely allow model and oem identification to be cleanly changed?
I am just theorizing here from what I have been reading. Finally: Is it true that uk/etc MS stopped giving out keys and referring ppl to HTC etc for
live? Any press release or official reaction?
Noticed leaked documents in another thread here marked Microsoft Confidential!
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....
I got useful information From thread posted by ThC23. Credit goes to him
ThC23 said:
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 -
*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.
*ASOP-
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.
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.
*Google Apps-
An add-on for Google's applications (Market, GMail etc.), packaged separately to avoid copyright issues
*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.
*Tethering-
Using a wireless device (e.g. an Android phone) to share it's wireless data connection to another device (e.g. laptop). With an Android device, the wireless data connection can usually be shared via WiFi, Bluetooth or USB connection.
*Wipe-
Usually refers to wiping data and cache partitions of the device.
*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.
Hacking Definitions
*Aftermarket-
Aftermarket generally refers to any product or service applied or requisitioned by end-users to add usability or functionality to the original product. Many aftermarket modifications can void the manufacturer's warranty. From a manufacturer's perspective, the after-market is any goods or services offered by the manufacturer directly to end-users of a given product or service. After-market services include support for warranties, contracts, and parts and accessories sales.
*Brick-
a device that no longer functions, generally caused by a failed firmware or SPL update. Since the device no longer works as intended, it is often referred to as a "brick" or "paper-weight", since that is all it is good for.
*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.
*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-
Obtaining root ("administrator", or "full") access to the device. This means you can mount its internal memory partition as read/write, which lets you do various things: have USB or Wi-Fi tethering, uninstall applications you otherwise can't uninstall (e.g. the Amazon MP3 store), install applications that need root access (such as AdFree), disable the camera shutter sound (simply by deleting the shutter sound file), overclock or underclock the CPU, install and boot Debian, and so on. Installing CyanogenMod roots the device in the process. The "Superuser" app controls what applications may gain root privileges.
*Unlock-
Most GSM devices are locked to only work with the sim cards of a particular carrier. Obtaining root access (e.g. installing CyanogenMod) on the device usually does nothing to the sim-lock. The usual way to unlock the device to all SIM cards is to obtain a subsidy unlock code from a carrier.
Click to expand...
Click to collapse
Good Job
It really helped me
sagarda7 said:
I got useful information From thread posted by ThC23. Credit goes to him
Click to expand...
Click to collapse
Nice post... i like this
Very Nice Information
Very very Nice Information............thanks for it..........
Thanks for the information.. like this!
nice, very informative for newbies like me
thanks for the info
Nice share... but we still don't have multi-odin, right...??
Thanx for the info
Thnx a lot ;-)
Sent from my GT-S5360 using XDA App
Elparaq said:
Nice share... but we still don't have multi-odin, right...??
Click to expand...
Click to collapse
You got that wrong. We don't have single-odin yet.
Sent from my GT-S5360 using XDA App
Nice Info, Thanks!
Nice. It helped me
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