Hello, fellow xda members. I'm teh5abiking and I'm gonna be showing you how to set up the Android SDK AND how to compile CyanogenMod.
Please note that we're gonna be doing a fair amount of work in the command line, and if you're not comfortable with using the command line, setting up the Android SDK and/or compiling CyanogenMod probably isn't for you.
This tutorial covers setting up the Android SDK and compiling CyanogenMod on Debian and Debian-derivatives (specifically Ubuntu and Linux Mint) I have included links for those of you who wish to set up the Android SDK on other operating systems aside from Ubuntu/Debian/Mint. I've also included a link for people who wish to compile CyanogenMod on Mac OS X instead of Linux.
I have tried to include a link for those of you who wish to set up the SDK on other Linux distributions such as Slackware, Fedora, openSUSE, Mandriva, and so on, however all the websites that I've visited that say they'll teach how to install the SDK on Linux systems in general are really for Ubuntu/Mint. Therefore, I'm sad to say that you'll have to make do with the general instructions on the Android Developer's website. If you're looking for distribution-specific tutorials, you'll have to look it up yourself (sorry )
I'm also sorry to say that you can't compile CyanogenMod on anything other than Debian (and Debian-derivatives, specifically Ubuntu and Mint) and Mac OS X
>UPDATE: It IS possible to compile on Fedora. I've only tested on Fedora 15 and Fedora 16, but the process remains largely the same. The only differences there are is in the packages you must install to get things going.
Click me if you want to set up the Android SDK on Windows or Mac OS X, Gentoo Linux, or Arch Linux
Click me if you want to compile CyanogenMod on Mac OS X instead of Ubuntu/Debian/Linux Mint
Click me if you want to set up the SDK on other Linux systems
Prerequisites
-Ubuntu 10.04/10.10/11.04/11.10, Debian 6.0.X/Squeeze (I haven't tested on Lenny, Wheezy, or Sid yet) or Linux Mint installed (Either as VirtualBox, partitioned alongside your main operating system, or written to the entire disk)
-Patience, as the repo sync will take a while.
-A distraction/diversion to help pass the time.
Okay, let's get started shall we?
PART I - SETTING UP THE SDK.
Okay, so first you're gonna need to grab the SDK from the developer's site. If you don't have it, here's the link to the developer's site that contains the SDK: http://developer.android.com/sdk/index.html Download the one for Linux (should be listed as a tgz file.)
Okay, once you've downloaded the SDK, extract it to the home folder, like in the picture that's below (for the tutorial's sake, we're renaming it to androidsdk).
{
"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"
}
NOTE: You are required to have Java installed in order to download the SDK platform tools otherwise users who go on without Java *WILL* get a Parse: XML error notice when downloading the SDK platform tools. This requirement has been noted on the "Installing the SDK" portion of the Android Developers website.
Installing Java can go one of two ways. The first way is to download the actual non-free Sun Java implementation by enabling the Canonical Partners repositories in your Software Sources (for Ubuntu users only. Sun Java 6 should be available in Debian's repositories by default across Squeeze, Wheezy, and Sid. Java 5 is available in Lenny's default repositories. Java 6 I believe is available in the Lenny backports. Linux Mint requires no additional configuration as Java comes preinstalled by default.) and downloading it via "apt-get" or Synaptic. If you install Java this way, you'll have to bear through slow download times as the mirrors aren't localized (unless you live in London or something), accepting an EULA, and having to manually maintain the said packages yourself since it's not software Debian or Canonical can support due to licensing issues.
However, the benefit for this is that installing the official Sun Java implementation on your system is that you can compile Android source, which the second post goes more in-depth about. To do so, go to your Software Sources. On Ubuntu 10.04, it's System -> Administration -> Software Sources. On 10.10 and 11.04, it's System -> Administration -> Update Manager -> Settings.
Once you have your software sources open, go to the "Other Software" tab and check off both Canonical Partners repositories. Once you hit the "Close" button, it will tell you your software listings are outdated. Hit "reload" and wait for the software sources menu to close.
IF YOU ARE USING UBUNTU 11.10: Sun Java is NOT available in the default partner repositories for Oneiric Ocelot. You must add the Lucid partner repository to your /etc/apt/sources.list. Here's how to do it:
Open up a terminal and enter the following:
Code:
$ sudo nano -w /etc/apt/sources.list
In the Nano text editor that's been opened up on your terminal, copy and paste the following at the bottom of the file. Once you're done, Press CTRL+X, Y, and then hit Enter.
Code:
##Java Repository.
deb http://archive.canonical.com/ lucid partner
Now that your repository information has been changed, execute the following to update your repository information, upgrade your system, and then install the Sun Java packages.
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install sun-java6-jre sun-java6-jdk sun-java6-bin
The second way is to download the OpenJDK implementation of Java. This is a bit out of date compared to the official Sun Java, however it should suffice for installing the Android SDK. The benefit for this is that a) It's free software, so that means software updates are supported by Debian and the community (OpenJDK is a part of Ubuntu's 'Universe' repository, meaning that it's community supported software.) b) You don't have to accept an EULA as it's free software. c) Since it's available in the default repositories, downloading it will be as fast as downloading normally. To install the OpenJDK implementation of Java, enter the following command:
Code:
sudo apt-get install openjdk-6-jre openjdk-6-jdk icedtea6-plugin
Now we must download the SDK platform tools as they're not included in the .tgz file you downloaded. To do so, we must start the Android SDK and AVD Manager which is located in the tools folder of the Android SDK. You can do this one of two ways, a) You can start up the file manager and manually navigate to the SDK's tools folder OR you can do it via command line. I find executing the Android SDK and AVD Manager from the command line to be easier so that's what we're going to do.
Code:
$ cd ~/androidsdk/tools
$ ./android
Click on "Available Packages" in the new window that pops up. Now, you have two options:
-Check off the first box and install all the SDK platform tools and nothing more. so we can progress with the tutorial.
-Check off both boxes so you install both the SDK platform tools and the third-party add-ons.
I recommend installing just the SDK platform tools, since it's quicker to do it like that, and the adb protocol is in the first repository, and that's what we're after. But you can do it in any way you chose. After choosing whether or not you want to install the SDK platform-tools along with the third-party add-ons, click on "Install Selected" then "Accept All" in the window that pops up and finally click on "Install." It's quite a bit to download (3.1 GB to be exact) if you download both the SDK platform tools and the third-party add-ons, but that gives us some time to get other stuff done.
UPDATE: The SDK and AVD manager has been updated as of SDK r15. Installation of Packages remains largely the same, sans for how you choose the repositories.
While we're downloading the SDK platform tools we have some work to do. See, we're gonna need to make use of ADB, and we can't set up our CM7 stuff in the platform-tools directory. Time to get nerdier
I find it tedious and messy to put stuff in the platform-tools directory every time I wanna do something like root a phone, so what we're gonna do is edit our PATH variable so that we can execute ADB from ANY location. With the terminal window that I hope you've kept open all this time, let's enter another command:
Code:
$ nano -w .bashrc
OR
Code:
$ gedit .bashrc
It'll open up a text editor, and it's showing us our .bashrc file. At the top of the .bashrc file, copy and paste the following:
Code:
#AndroidDev PATH
export PATH=${PATH}:~/androidsdk/tools
export PATH=${PATH}:~/androidsdk/platform-tools
NOTE: As there is no "~/.bashrc" file included in Linux Mint, you must do the following to make sure it's executable.
Code:
$ chmod a+x ~/.bashrc
After you're finished, it should look like this:
Save your changes. (Nano users, just press CTRL+X, Y, and Enter. Gedit users, just click on File and then click on 'Save')
Now that we've got our SDK ready (for the most part), it's time to set up udev.
udev is the USB 'driver' for Linux, allowing your computer to talk to the device when using adb or fastboot. Just like how you needed drivers for Windows to make ADB work, the same principles apply to Linux, albeit in a different form. So, in that terminal window (That I hope you have kept open all this time) Enter the following, so we can locate and edit the file that our udev rules need.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
.
OR
Code:
$ sudo nano -w /etc/udev/rules.d/51-android.rules
Once you've done that, copy the udev rules that are below and paste them into the rules file, as shown below.
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev
It should be like in the picture below
Save all your changes (Nano: CTRL+X, Y, and hit Enter. Gedit: File, Save As), and then reboot otherwise adb won't be in your path.
NOTE: Debian and Mint users MUST execute the following as root, otherwise udev will fail to recognize your device. If ADB won't recognize your device, execute the following as root:
Code:
$ chmod a+r /etc/udev/rules.d/51-android.rules
Once you do that, let's verify the success of our efforts, so open up a terminal (CTRL + ALT + T or Applications -> Accessories -> Terminal) and enter the following:
Code:
$ adb devices
You should get something like in the picture below.
Congratulations, you've set up the Android SDK! If you just wanted the SDK, you can stop here.
I have adapted this from multiple sources, however the sources that I've used the most in this tutorial are from Ubuntu's wonderful community-contributed documentation.
COMMUNITY UBUNTU DOCUMENTATION FOR INSTALLING THE ANDROID SDK
COMMUNITY UBUNTU DOCUMENTATION ON INSTALLING JAVA
If you want to learn how to compile one of the most popular custom ROMs for Android, read the next post to learn how.
PART 2 - Compiling CyanogenMod.
This half of the tutorial covers the actual compilation of CyanogenMod, one of the most popular custom ROMS that are available to modded Android devices. CyanogenMod supports more devices than ANY custom ROM project that is available for the Android operating system, and let's see
Reasons why you might want to compile your own version of CyanogenMod might be one of the following:
- You might want an updated version of your ROM or an updated portion of your ROM (be that an updated kernel, updated core applications, or an updated version of the Android operating system)
- Certain bugs that you might have experienced in the stable releases of CyanogenMod may have been patched.
- The ROM that you'll compile will contain the most bleeding-edge features that have been committed into the CyanogenMod github.
- You can pick and choose which features that you want and which features you don't want (cherry-picking features won't be covered in this post.)
- You might want to see what goes into making a custom ROM.
- Certain features that you don't care for may have been omitted from the CyanogenMod github or may have been tweaked.
NOTE: Even though 64-bit building environments are supported past Android 2.2, this tutorial will still work on a 32-bit computer.
UPDATE: The Android Open Source Project has been updated to provide 32-bit build environments. However, the AOSP claims that this is experimental. So far, everything is stable. I've incurred no issues as of yet.
FOR 32-bit systems:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown libxml2-utils
For 64-bit systems:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils
If you have a 64-bit system, you must also do the following:
- If you are running Ubuntu 10.04, 10.10, or 11.04, execute the following command in a terminal:
Code:
$ sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
- If you are running Ubuntu 11.10, execute the following command in a terminal:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
NOTE: For 64-bit systems running Ubuntu 11.10, you may not need to install the 'ia32-libs' package, as the 64-bit edition of Ubuntu 11.10 comes with multiarch support, meaning you can run 32-bit programs without the need for additional libraries. However, I've yet to test this feature because I'm running a 32-bit computer. Please post your results if you've tried this tutorial without ia32-libs and instead used Ubuntu 11.10's multiarch support.
Once you do that, you should have something like this (I've already set up my build environment, so it won't be exactly the same as what you should have. Either way, it should go about as a standard package installation procedure)
Okay, now that we have our packages installed, we need to create the build directories. In that terminal window that you should still have open, enter the following commands so that we can create the build directories.
Code:
$ mkdir -p ~/android/system/
$ mkdir -p ~/bin/
NOTE: You can replace "~/android/system/" with any other type of directory. Some people go with "~/cm-build" other people go with "~/cm7" Any time you see "~/android/system/" in a command, just replace that with whatever your build directory is. Just make sure you enter the right location though for such commands.
Now we need to initialize the repo binary and make it executable. If you're wondering what the repo binary is, just look it up at http://source.android.com/source/version-control.html
To make the binary executuable, enter the following commands:
Code:
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
NOTE: You may have to reboot for these changes to work.
Once you've done that, it should look a little something like this:
Okay, now that we've got the repo binary set up, we're now ready to download the source. I warn you though, it does take a long time, so you're gonna want to get a snack, watch a movie, play Quadrapassel, etc. just to pass the time. Trust me.
Okay, let's download the source so that we can continue
Code:
$ cd ~/android/system/
$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
$ repo sync -j16
And now we play the waiting game. You may be wondering what the "-j16" addon is for, well it's essentially an addition to the repo sync command that starts 16 tasks at once. It's a little quicker than doing it withouth the -j16 addon. In total, it should take anywhere between one hour to two hours, depending on your internet connection. Well, I just played Quadrapassel (Ubuntu's version of Tetris) while it was syncing.
Once it's done syncing, you should have something that's in the picture below.
Congratulations! You've withstood the first test. Now let's continue.
This is the part where you're supposed to copy the proprietary files from your G2/DZ. The problem here is that most of the time, it'll give you an error message saying that "MS-HTCEMR-20-BLAHBLAHBLAH.apk is missing" Instead of having to copy the proprietary files straight from the device itself, I just got them from the Koush github.
Here's the link to the Koush github. Just hit the download button that's in the upper right-hand corner and save as .zip file.
https://github.com/koush/proprietary_vendor_htc
Extract it to "~/android/system/vendor/htc/" By doing this, not only do you have the proprietary files for Vision, you also have the proprietary files for ALL HTC devices that CyanogenMod currently supports. That means you can compile a ROM for ANY HTC Android phone you want (Passion/N1, Bravo/Desire, Glacier/MT4G. etc.) Score 1 for doing it unconventionally!
Now it's time to get ROM Manager. You only need to do this every time there's a new release of ROM Manager. So, in that terminal window that I hope you've kept open after all this time, enter the following:
Code:
$ ~/android/system/vendor/cyanogen/get-rommanager
This will get the latest version of ROM Manager that's currently available. We need to see if there have been any updates in the source. That means we're gonna have to repo sync again. Why? Well, we just spent about an hour or two gathering the source, and in that time, something could've changed in the github, so it only makes sense to check again. This time, the repo sync should be faster since we already have all the source.
Code:
$ cd ~/android/system/
$ repo sync
Once that's done, now we're ready to start cooking up the ROM. Enter the following:
Code:
$ make clean
$ make installclean
$ make clobber
$ . build/envsetup.sh && brunch vision
(make clean, make installclean, and make clobber clean out all the directories so that every time you make a ROM, older builds you made yourself won't conflict with the one you're making right now. the brunch is the one that actually sets up the build environment and builds the ROM.)
Compiling the ROM takes anywhere between 20-30 minutes on good hardware to 1 hour - 2 hours on older computers. If you're impatient, read this article from the CyanogenMod Wiki that explains how to speed up compiling, testing, etc.
http://wiki.cyanogenmod.com/wiki/Howto:_Speed_up_building
Congratulations! You've successfully compiled your first build of CyanogenMod! Give yourself a pat on the back. If you're curious as to how this should look, well the photo below should tell you how it should looks. All builds you'll compile have the KANG addition since it's not an official release of CM7.
Remember to hit that Thanks button people
All thanks go to the following people:
cyanogen for sharing his methods.
sykopompos for providing original instructions on how to set up the SDK and compiling CM7
plasmadragon007 for helping me getting the build to compile.
Nice clear guide, thanks. Might give this a try tomorrow. I had tried once before but failed but this seems like a nice simple guide.
Could you provide a guide that details how to cherry pick new features etc?
Thanks
teh5abiking said:
PART 2 - Compiling CyanogenMod.
Here's the link to the Koush github. Just hit the download button that's in the upper right-hand corner and save as .zip file.
Click to expand...
Click to collapse
thanks for the great guide ...btw you missed to give the link for koush github
@cjward23
I can't because I don't know how.
But once I figure it out and try it a few times I'll be more than happy to post a tutorial.
hispeedworm said:
thanks for the great guide ...btw you missed to give the link for koush github
Click to expand...
Click to collapse
Thanks, I missed that one. I had the thing on gedit and I was fixing up some stuff.
Fixed
teh5abiking said:
Thanks, I missed that one. I had the thing on gedit and I was fixing up some stuff.
Fixed
Click to expand...
Click to collapse
sweeeeet
hey i am on the second part figuring out how to compile cyanogen and i do this
$ sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package gcc-4.3-multilib
E: Couldn't find any package by regex 'gcc-4.3-multilib'
E: Unable to locate package g++-4.3-multilib
E: Couldn't find any package by regex 'g++-4.3-multilib'
Could someone tell me what it is i am doing wrong i am running 64bit ubuntu here .... i feel like such a noob....
noob1015 said:
hey i am on the second part figuring out how to compile cyanogen and i do this
$ sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package gcc-4.3-multilib
E: Couldn't find any package by regex 'gcc-4.3-multilib'
E: Unable to locate package g++-4.3-multilib
E: Couldn't find any package by regex 'g++-4.3-multilib'
Could someone tell me what it is i am doing wrong i am running 64bit ubuntu here .... i feel like such a noob....
Click to expand...
Click to collapse
Are you on Ubuntu 11.04?
teh5abiking said:
Are you on Ubuntu 11.04?
Click to expand...
Click to collapse
yes.... oh boy sounds like i missed something....
noob1015 said:
yes.... oh boy sounds like i missed something....
Click to expand...
Click to collapse
Try doing the tutorial from the second post over.
same error the first command went through as yours did showing
[email protected]:~$ sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
[sudo] password for kris:
*all those lines here saying latest version*
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:~$ sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package gcc-4.3-multilib
E: Couldn't find any package by regex 'gcc-4.3-multilib'
E: Unable to locate package g++-4.3-multilib
E: Couldn't find any package by regex 'g++-4.3-multilib'
ps i continued on and got the repo bin file and chmoded it but the repo command doesn't work for later on just a thing to add just in case. Probably becuase of this
Try using the 64-bit command first, I don't own a 32-bit system myself so I can't really diagnose what's wrong.
is that this command ($ sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib)
for 32 bit systems? or 64 bit systems
because mine is 64bit and you say 64 bit systems use that command (i am confused)
perhaps this can clear things up?
http://wiki.cyanogenmod.com/wiki/Compile_CyanogenMod_for_Vision
those missing files are no longer available in 11.04 so that's why they were missing they were supposed to be
ok rebooted my system now it is working no idea what was happening before... sorry about all the issues and thank you for all your help
noob1015 said:
those missing files are no longer available in 11.04 so that's why they were missing they were supposed to be
ok rebooted my system now it is working no idea what was happening before... sorry about all the issues and thank you for all your help
Click to expand...
Click to collapse
Always happy to help
Sometimes, when you're giving the repo binary executable permissions, you might have to reboot. Forgot to include that.
i know im posting in the wrong thread but im compiling on ubuntu 10.04(64bit) for a legacy samsung device im getting this error any helps please
HTML:
host C: emulator <= external/qemu/audio/alsaaudio.c
external/qemu/audio/alsaaudio.c:25:28: error: alsa/asoundlib.h: No such file or directory
In file included from external/qemu/audio/alsaaudio.c:92:
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected declaration specifiers or ‘...’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected declaration specifiers or ‘...’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected declaration specifiers or ‘...’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected declaration specifiers or ‘...’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: error: expected ‘)’ before ‘*’ token
external/qemu/dynlink.h:71: warning: type defaults to ‘int’ in declaration of ‘snd_pcm_hw_params_t’
external/qemu/dynlink.h:71: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
external/qemu/dynlink.h: In function ‘alsa_dynlink_init’:
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_current’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: (Each undeclared identifier is reported only once
external/qemu/dynlink.h:91: error: for each function it appears in.)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_sw_params_set_start_threshold’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_sw_params’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_sw_params_current’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_any’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_access’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_get_format’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_format’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_rate_near’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_channels_near’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_buffer_time_near’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_get_buffer_size’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_prepare’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_get_period_size’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_get_period_size_min’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_period_size’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_get_buffer_size_min’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_buffer_size’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_period_time_near’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_avail_update’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_drop’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_writei’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_readi’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_state’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_open’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_close’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_buffer_size_near’ undeclared (first use in this function)
external/qemu/dynlink.h:91: error: ‘_dynlink_snd_pcm_hw_params_set_period_size_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c: At top level:
external/qemu/audio/alsaaudio.c:106: error: expected specifier-qualifier-list before ‘snd_pcm_t’
external/qemu/audio/alsaaudio.c:111: error: expected specifier-qualifier-list before ‘snd_pcm_t’
external/qemu/audio/alsaaudio.c:140: error: expected specifier-qualifier-list before ‘snd_pcm_format_t’
external/qemu/audio/alsaaudio.c:153: error: expected specifier-qualifier-list before ‘snd_pcm_uframes_t’
external/qemu/audio/alsaaudio.c:185: error: expected ‘)’ before ‘*’ token
external/qemu/audio/alsaaudio.c:199: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘aud_to_alsafmt’
external/qemu/audio/alsaaudio.c:229: error: expected ‘)’ before ‘alsafmt’
external/qemu/audio/alsaaudio.c: In function ‘alsa_dump_info’:
external/qemu/audio/alsaaudio.c:295: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:297: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:301: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:301: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:302: error: ‘struct alsa_params_obt’ has no member named ‘samples’
external/qemu/audio/alsaaudio.c: At top level:
external/qemu/audio/alsaaudio.c:305: error: expected ‘)’ before ‘*’ token
external/qemu/audio/alsaaudio.c:336: error: expected declaration specifiers or ‘...’ before ‘snd_pcm_t’
external/qemu/audio/alsaaudio.c: In function ‘alsa_open’:
external/qemu/audio/alsaaudio.c:338: error: ‘snd_pcm_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:338: error: ‘handle’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:339: error: ‘snd_pcm_hw_params_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:339: error: ‘hw_params’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:344: error: ‘snd_pcm_uframes_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:344: error: expected ‘;’ before ‘obt_buffer_size’
external/qemu/audio/alsaaudio.c:346: error: ‘snd_pcm_format_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:346: error: expected ‘;’ before ‘obtfmt’
external/qemu/audio/alsaaudio.c:349: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:350: error: ‘struct alsa_params_req’ has no member named ‘size_in_usec’
external/qemu/audio/alsaaudio.c:352: error: expected expression before ‘)’ token
external/qemu/audio/alsaaudio.c:354: error: ‘_dynlink_snd_pcm_open’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:357: error: ‘SND_PCM_STREAM_CAPTURE’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:357: error: ‘SND_PCM_STREAM_PLAYBACK’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:358: error: ‘SND_PCM_NONBLOCK’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:365: error: ‘_dynlink_snd_pcm_hw_params_any’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:371: error: ‘_dynlink_snd_pcm_hw_params_set_access’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:374: error: ‘SND_PCM_ACCESS_RW_INTERLEAVED’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:381: error: ‘_dynlink_snd_pcm_hw_params_set_format’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:381: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:383: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:387: error: ‘_dynlink_snd_pcm_hw_params_set_rate_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:393: error: ‘_dynlink_snd_pcm_hw_params_set_channels_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:400: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:411: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:416: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:418: error: ‘_dynlink_snd_pcm_hw_params_set_buffer_time_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:427: error: expected ‘;’ before ‘bsize’
external/qemu/audio/alsaaudio.c:429: error: ‘_dynlink_snd_pcm_hw_params_set_buffer_size_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:432: error: ‘bsize’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:438: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:442: error: ‘struct alsa_params_req’ has no member named ‘override_mask’
external/qemu/audio/alsaaudio.c:442: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:444: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:447: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:452: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:454: error: ‘_dynlink_snd_pcm_hw_params_set_period_time_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:464: error: expected ‘;’ before ‘psize’
external/qemu/audio/alsaaudio.c:466: error: ‘_dynlink_snd_pcm_hw_params_set_period_size_near’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:469: error: ‘psize’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:477: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:481: error: ‘struct alsa_params_req’ has no member named ‘override_mask’
external/qemu/audio/alsaaudio.c:481: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:483: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:486: error: ‘_dynlink_snd_pcm_hw_params’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:492: error: ‘_dynlink_snd_pcm_hw_params_get_buffer_size’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:492: error: ‘obt_buffer_size’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:498: error: ‘_dynlink_snd_pcm_hw_params_get_format’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:498: error: ‘obtfmt’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:505: warning: implicit declaration of function ‘alsa_to_audfmt’
external/qemu/audio/alsaaudio.c:510: error: ‘_dynlink_snd_pcm_prepare’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:517: error: expected ‘;’ before ‘threshold’
external/qemu/audio/alsaaudio.c:538: error: ‘threshold’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:539: warning: implicit declaration of function ‘alsa_set_threshold’
external/qemu/audio/alsaaudio.c:544: error: ‘struct alsa_params_obt’ has no member named ‘samples’
external/qemu/audio/alsaaudio.c:546: error: ‘handlep’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:549: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:550: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:562: warning: implicit declaration of function ‘alsa_anal_close’
external/qemu/audio/alsaaudio.c: At top level:
external/qemu/audio/alsaaudio.c:566: error: expected ‘)’ before ‘*’ token
external/qemu/audio/alsaaudio.c:576: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘alsa_get_avail’
external/qemu/audio/alsaaudio.c: In function ‘alsa_run_out’:
external/qemu/audio/alsaaudio.c:605: error: ‘snd_pcm_sframes_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:605: error: expected ‘;’ before ‘avail’
external/qemu/audio/alsaaudio.c:612: error: ‘avail’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:612: warning: implicit declaration of function ‘alsa_get_avail’
external/qemu/audio/alsaaudio.c:612: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:618: warning: type defaults to ‘int’ in declaration of ‘tb’
external/qemu/audio/alsaaudio.c:624: error: expected ‘;’ before ‘written’
external/qemu/audio/alsaaudio.c:632: error: ‘written’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:632: error: ‘_dynlink_snd_pcm_writei’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:632: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:643: warning: implicit declaration of function ‘alsa_recover’
external/qemu/audio/alsaaudio.c:643: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c: In function ‘alsa_fini_out’:
external/qemu/audio/alsaaudio.c:681: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c: In function ‘alsa_init_out’:
external/qemu/audio/alsaaudio.c:694: error: ‘snd_pcm_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:694: error: ‘handle’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:702: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:702: warning: implicit declaration of function ‘aud_to_alsafmt’
external/qemu/audio/alsaaudio.c:704: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:705: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:706: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:707: error: ‘struct alsa_params_req’ has no member named ‘size_in_usec’
external/qemu/audio/alsaaudio.c:708: error: ‘struct alsa_params_req’ has no member named ‘override_mask’
external/qemu/audio/alsaaudio.c:709: warning: suggest parentheses around operand of ‘!’ or change ‘|’ to ‘||’ or ‘!’ to ‘~’
external/qemu/audio/alsaaudio.c:711: error: too many arguments to function ‘alsa_open’
external/qemu/audio/alsaaudio.c:721: error: ‘struct alsa_params_obt’ has no member named ‘samples’
external/qemu/audio/alsaaudio.c:723: error: ‘struct alsa_params_obt’ has no member named ‘samples’
external/qemu/audio/alsaaudio.c:731: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c: At top level:
external/qemu/audio/alsaaudio.c:741: error: expected ‘)’ before ‘*’ token
external/qemu/audio/alsaaudio.c: In function ‘alsa_ctl_out’:
external/qemu/audio/alsaaudio.c:770: warning: implicit declaration of function ‘alsa_voice_ctl’
external/qemu/audio/alsaaudio.c:770: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:774: error: ‘ALSAVoiceOut’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c: In function ‘alsa_init_in’:
external/qemu/audio/alsaaudio.c:785: error: ‘snd_pcm_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:785: error: ‘handle’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:793: error: ‘struct alsa_params_req’ has no member named ‘fmt’
external/qemu/audio/alsaaudio.c:795: error: ‘struct alsa_params_req’ has no member named ‘nchannels’
external/qemu/audio/alsaaudio.c:796: error: ‘struct alsa_params_req’ has no member named ‘period_size’
external/qemu/audio/alsaaudio.c:797: error: ‘struct alsa_params_req’ has no member named ‘buffer_size’
external/qemu/audio/alsaaudio.c:798: error: ‘struct alsa_params_req’ has no member named ‘size_in_usec’
external/qemu/audio/alsaaudio.c:799: error: ‘struct alsa_params_req’ has no member named ‘override_mask’
external/qemu/audio/alsaaudio.c:800: warning: suggest parentheses around operand of ‘!’ or change ‘|’ to ‘||’ or ‘!’ to ‘~’
external/qemu/audio/alsaaudio.c:802: error: too many arguments to function ‘alsa_open’
external/qemu/audio/alsaaudio.c:812: error: ‘struct alsa_params_obt’ has no member named ‘samples’
external/qemu/audio/alsaaudio.c:814: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c:815: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c:822: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c: In function ‘alsa_fini_in’:
external/qemu/audio/alsaaudio.c:836: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:838: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c:839: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c:840: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c: In function ‘alsa_run_in’:
external/qemu/audio/alsaaudio.c:859: error: ‘snd_pcm_sframes_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:859: error: expected ‘;’ before ‘avail’
external/qemu/audio/alsaaudio.c:860: error: ‘snd_pcm_uframes_t’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:860: error: expected ‘;’ before ‘read_samples’
external/qemu/audio/alsaaudio.c:866: error: ‘avail’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:866: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:872: error: ‘_dynlink_snd_pcm_state’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:872: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:872: error: ‘SND_PCM_STATE_PREPARED’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:876: warning: type defaults to ‘int’ in declaration of ‘tb’
external/qemu/audio/alsaaudio.c:892: error: expected ‘;’ before ‘nread’
external/qemu/audio/alsaaudio.c:893: error: expected ‘;’ before ‘len’
external/qemu/audio/alsaaudio.c:895: error: ‘len’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:897: error: ‘ALSAVoiceIn’ has no member named ‘pcm_buf’
external/qemu/audio/alsaaudio.c:901: error: ‘nread’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:901: error: ‘_dynlink_snd_pcm_readi’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c:901: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:912: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:940: error: ‘read_samples’ undeclared (first use in this function)
external/qemu/audio/alsaaudio.c: In function ‘alsa_ctl_in’:
external/qemu/audio/alsaaudio.c:962: error: ‘ALSAVoiceIn’ has no member named ‘handle’
external/qemu/audio/alsaaudio.c:966: error: ‘ALSAVoiceIn’ has no member named ‘handle’
make: *** [out/host/linux-x86/obj/EXECUTABLES/emulator_intermediates/audio/alsaaudio.o] Error 1
its about 3mins into the make process i'm running 2.7ghz dual core i5 chipset with 1gb ram....some things are undeclared it its getting aborted at alsaaudio.o ..
I've buy used Defy. Seller say me:
Point -1 "I tried to update update it on my pc and I got stuck on bootloader with Code corrupt message".
Point 0 After 3 weeks delivery battery was full discharged, so I plug charger, and see battery's animation.
Point 1 Normal boot of Android. I see all previous users data: SMS, call log, photos, games, etc...
Ok! Reboot to stock recovery -> wipe data/factory reset -> wipe cash -> reboot.
And all exactly as befor a factory reset. Return to Point 1.
Point 2 Of course - RSDLite and stock.sbf - it can quick resolve of all problems, as I've think naively.
Code:
02:05:44, February 11, 2012
Line: 537
ERROR: AP Die ID: 15000109f11468010000dcff0200
02:05:44, February 11, 2012
Line: 544
ERROR: BP Die ID: 0000000000000000000000000000
02:05:45, February 11, 2012
Line: 551
ERROR: AP Public ID: d0e71bd823eaaf9db675d65371b6e26df979ea09
02:05:45, February 11, 2012
Line: 558
ERROR: BP Public ID: 0000000000000000000000000000000000000000
02:08:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:12:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:12:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x8BAC, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:16:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:16:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 34 checksums. File: 0xAB80, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:17:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:17:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 35 checksums. File: 0x100C, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:18:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:18:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0xC7E6, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:19:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:19:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 42 checksums. File: 0x4BB7, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:20:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:20:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0x738D, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:21:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:21:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 47 checksums. File: 0x45F0, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:22:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:22:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 53 checksums. File: 0xFDFF, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:23:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:23:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 61 checksums. File: 0x4A7C, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:24:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:24:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 64 checksums. File: 0x85D0, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1434
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1480
ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 1194
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
02:25:33, February 11, 2012
Line: 610
ERROR: Flash failure: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=32
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
After flashing failed, phone start in bootloader only, and message "Code corrupt" below boot version. Return to Point -1.
Point 3 Short circuit of battery on motherboard was restore phone's normal boot, and now return to Point 1.
I've flash with about 10 different official .sbf, all with same result - Point -1.
I've get root, install 2ndInit - and reboot to Point 1.
I've get root and write CG47 directly to dev/block/mmcblk1p16, then reboot to recovery -> wipe data/factory reset -> wipe cash -> reboot... And return to Point 1 again.
Probably the flash memory is corrupted/damaged from wear and cannot be erased or something...
U can try sbf_flash on Linux...
Sent from my MB525 using xda premium
nogoodusername said:
U can try sbf_flash on Linux...
Click to expand...
Click to collapse
Already tried, same result as RSD Lite.
Good morning.
- You off to see the groundhog?
- I am.
Click to expand...
Click to collapse
TorAll said:
Already tried, same result as RSD Lite.
Click to expand...
Click to collapse
Same, but not at all!
I've tried sbf_flash --groupnane full.sbf step by step.
Succesfully flashed:
CG64 0xB0000000-0xB001FFFF mbr
CG65 0xB0180000-0xB01FFFFF ebr
CG31 0xB0280000-0xB02FFFFF cdt.bin
CG34 0xB0700000-0xB077FFFF lbl
CG61 0xB0B00000-0xB0B7FFFF devtree
CG53 0xB2F00000-0xB32FFFFF kpanic
What this mean, who can answer me?
on what sbf are you now? (in about screen on phone)
Could it be that it was flashed with some sbf that had version 6 or version 7 CG before it got to you? Have you tried flashing some DEFY+ ROM? Or maybe that version 6 Froyo?
But then he wouldn't be able to flash CG31 :s
Think there is really something wrong :/
I would try warranty?
Seems to be not the only one :
http://forum.xda-developers.com/showthread.php?t=1485289
labsin said:
on what sbf are you now? (in about screen on phone)
Click to expand...
Click to collapse
3.4.2-107_jdn-9
labsin said:
I would try warranty?
Seems to be not the only one
http://forum.xda-developers.com/showthread.php?t=1485289
Click to expand...
Click to collapse
Warranty... too sweet for me Motorola fell out of love Russia.
I've searched too, and find couple peaples, who had troubles like me. As far as I know, they dont resolved it.
I have the same problem you have found a solution?