Database Develop

[GUIDE] Flash SBF to Atrix (Mac OS X or Linux) *simple*

//Version 1.0
Flash any SBF file to your device *without* RSDLite (Mac or Linux)
*using sbf_flash created by [mbm]
**UPDATE: THIS DOES NOT WORK WITH RADIO SBFS. YOU CAN USE CWM TO FLASH RADIO IMGS.
**IF YOU ARE UNLOCKED WITH CWM, YOU REALLY SHOULD HAVE NO NEED TO FLASH FULL SBF FILES. SEE SAMCRIPP'S FRUIT CAKE THREAD
This guide is for Mac OS or Linux users only!! I didn't see any dedicated guide for flashing SBF files for Mac users so i thought I would contribute something to this wonderful community.
Pre-Guide Information (SKIP BELOW FOR ACTUAL INSTRUCTIONS)
The standard prerequisite for flashing SBF files to our devices is RSD Lite, and as we all know, the only platform made available for RSD Lite is Windows. Mac or Linux users have always been required to either run Windows using a virtual machine or find a Windows computer to use. In my opinion, all of these methods are time consuming and can sometimes be very frustrating. Now we can VERY easily flash any SBF file using a simple utility called "sbf_flash" (created by [mbm]). The creator of this wonderful little utility deserves a lot of credit because he was able to make the executable work on both Mac and Linux platforms which is no small feat considering Mac OS X uses the mach-o executable file format while Linux uses ELF. It is very interesting how he was able to accomplish this so if you are interested to find out how or interested in learning more about this nifty little utility, visit his blog.
[mbm]'s Optical Delusion Blog: http://blog.opticaldelusion.org/
DISCLAIMER: The following procedures require you to be somewhat comfortable using terminal and some basic commands. All the standard warnings apply as well. I am not responsible if anything happens to your device. It is your responsibility to ensure you are flashing an SBF that is compatible with your device. Check and then double check for good measure. I also recommend checking the md5sum of the file you choose. Check both the compression md5sum and the actual SBF file md5sum. Follow the instructions carefully and heed the warnings about downgrading.
** DO NOT TRY TO DOWNGRADE TO 1.8.3 IF YOU HAVE FLASHED AN OTA UPDATE OF 4.5.91 **
---------------------------------------------------------------------------------------------------------------------------------------------------
INSTRUCTIONS
SBF_FLASH GUIDE FOR MAC OS X (linux users too)
Required Files to Download:
- sbf_flash utility ---> DIRECT DOWNLOAD
- sbf file of your choice **make 100% sure the SBF file you choose is compatible with your device**
** no drivers needed, thats the beauty of this method. so clean **
**There are 2 sets of Instructions, choose one. Novice and Expert (Scroll below for Expert).**
Detailed Instructions (Novice):
GET READY: As always when flashing SBF files, remove your SIM and microSD cards and power the device on by holding the Vol+ and Power.
Step 1: Download sbf_flash and place it in an easily accessible directory (e.g. /Users/username/Documents)
*You have to rename the file "sbf_flash" to "sbf_flash.sh" (thank you n1ckr0th)
Step 2: Place the SBF file you have chosen in the SAME directory you put sbf_flash (e.g. /Users/username/Documents/).
Step 3: Open up a terminal shell.
Step 4: In terminal, change to the directory where you have placed both files:
* SKIP TO STEP 5 IF YOU KNOW HOW TO USE TERMINAL *
// how to change directories in terminal
* in the following instructions, ignore the brackets when typing in the commands
- the command [cd] is what you use to change the directory. so if the files are in /Users/username/Documents, you would type [cd Documents]
- the command [ls] lists all the files and folders in the current directory. type [ls] and make sure you see both files before proceeding.
Step 5: We first need to make sbf_flash executable (thank you ionstorm3) by doing the following steps:
* once again, ignore the brackets when typing these commands
- type [sudo chmod +x sbf_flash.sh]
- it will now prompt you for your password. enter it *note: [sudo] is a command which gives temporary admin privileges for the preceding command.
- sbf_flash is now executable. continue
Step 6: Flash the image onto your phone:
- type [sudo ./sbf_flash.sh nameofyourSBFfile] (example: if your SBF file is called "atrix.sbf", you would type [sudo ./sbf_flash.sh atrix.sbf]
- once again, it will prompt you for your password. enter it again.
- you are now done.
If you followed the above steps correctly, the SBF file will now begin flashing onto your device. Sit back, grab a brew, and relax.
*TIPS: when you are typing in the names of files or folders in terminal, you can hit the [tab] key after you have typed in the first few letters of the file or folder and terminal will autocomplete the rest. This is especially useful if your SBF file has a long name (e.g. OLYFR_U4_1.8.3_SIGNED_1g_1FF.sbf) in this case, if you just type OLYF then hit the [tab] key, terminal will autocomplete the rest of the filename for you. Very useful!
---------------------------------------------------------------------------------------------
EXPERT INSTRUCTIONS:
1. Download sbf_flash utility and place in easily accessible directory
2. Download SBF file of your choice and place in same directory
3. Open up a terminal shell and [cd] into that directory
4. Execute following command [sudo chmod +x sbf_flash.sh] - this makes sbf_flash exectuable (thanks ionstorm3)
5. Execute following command [sudo ./sbf_flash.sh nameofyourSBFfile] - this flashes your SBF file to your device.
6. Done son.
Well folks, that is it. In my opinion, this is the fastest and easiest way for Mac and Linux users to flash SBF files. Now we can finally do all our rooting/flashing/etc. on one machine. If you have any questions/concerns/problems, please feel free to PM me. Also, if you have any suggestions on improving this guide, let me know. Now it is time for me to give credit to those that deserve it.
CREDITS:
[mbm] for creating sbf_flash and making it work perfectly on both Mac and Linux platforms.
ionstorm3 - thank you very much for not only essentially providing me with the cream of this guide, but promptly responding to my initial concerns.
XDA Community: thank you for well……everything. this is such a great community with many helpful members.

This doesn't work for radio SBFs I believe?
Sent from my MB860 using XDA App

working with Ubuntu
I had no luck using sbf-fash until I updated the udev rules. it would just hang and not flash anything, after updating udev it works perfectly. I do not know if user on Linux other then Ubuntu will have this problem but if they are they may want to check out http://forum.xda-developers.com/showthread.php?t=921169 and look at step 5. This is a walk-through of getting adb setup and working under Ubuntu and is a very helpful post.
neer2005 said:
This doesn't work for radio SBFs I believe?
Click to expand...
Click to collapse
Not sure about that, I will have to test that out tonight.

neer2005 said:
This doesn't work for radio SBFs I believe?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
this is actually a very good question that I do not know the answer to. but i will do my best to find out

arvindrao86 said:
this is actually a very good question that I do not know the answer to. but i will do my best to find out
Click to expand...
Click to collapse
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
also, you might want to change the op to say that you need to either rename the sbf_flash file to .sh after you download it and change the third step to include the .sh extension (sudo ./sbf_flash.sh nameofradio) or remove it from the first step because it didnt work until i added the .sh and included it in all the commands.

n1ckr0th said:
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
also, you might want to change the op to say that you need to either rename the sbf_flash file to .sh after you download it and change the third step to include the .sh extension (sudo ./sbf_flash.sh nameofradio) or remove it from the first step because it didnt work until i added the .sh and included it in all the commands.
Click to expand...
Click to collapse
thank you for the confirmation of radio flashing and for the obvious flaw in my instructions.

Stop flashing with sbf... You guys have more safer methods using cwm.
Sent from my MB860 using Tapatalk

CWM for radios?

n1ckr0th said:
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
Click to expand...
Click to collapse
Didn't seem to work for me w/Debian Squeeze, I'm afraid.
Code:
debian:/# ./sbf_flash.sh 4591Radio.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== 4591Radio.sbf ===
00: RDL03 0x00000000-0x002FFFFF 9FC5 AP
01: RDL01 0x00800000-0x008407FF 36FF BP
02: CG05 0x00000000-0x013E3BF7 E0E7 BP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> rebooting

AnalogXDA said:
Didn't seem to work for me w/Debian Squeeze, I'm afraid.
Code:
debian:/# ./sbf_flash.sh 4591Radio.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== 4591Radio.sbf ===
00: RDL03 0x00000000-0x002FFFFF 9FC5 AP
01: RDL01 0x00800000-0x008407FF 36FF BP
02: CG05 0x00000000-0x013E3BF7 E0E7 BP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> rebooting
Click to expand...
Click to collapse
I assume that you can flash other sbf files??
Also for me running Ubuntu 11.04 I have no need to rename it to a .sh but I guess if it works it works, that is the important thing.. Just for myself what shell are you using, I use bash.

Worked for me in Mac OSX (at least the radio flash). Also, no need to add the .sh extension in OSX.
Thanks for posting this, I've been trying to figure out how to use the new sbf_flash. I wasn't aware of the need to mark it as executable.

Tao_Man said:
I assume that you can flash other sbf files??
Also for me running Ubuntu 11.04 I have no need to rename it to a .sh but I guess if it works it works, that is the important thing.. Just for myself what shell are you using, I use bash.
Click to expand...
Click to collapse
Yep, I used sbf_flash to unlock the bootloader. I'm using bash, via Xfce terminal emulator.

getabetterpic said:
Worked for me in Mac OSX (at least the radio flash). Also, no need to add the .sh extension in OSX.
Thanks for posting this, I've been trying to figure out how to use the new sbf_flash. I wasn't aware of the need to mark it as executable.
Click to expand...
Click to collapse
the .sh was only added for consistency throughout the instructions.

The author is [mbm], not "Optical Delusions" ... that's just the name of his blog. And no, it does not flash your radio.
16:03 < [mbm]> anyway, sbf_flash can't reflash baseband
19:21 < [mbm]> right, sbf_flash has never touched the bp
19:21 < [mbm]> it just skips over those sections of the sbf
It's a great tool, but I think this thread belongs in General.

eval- said:
The author is [mbm], not "Optical Delusions" ... that's just the name of his blog. And no, it does not flash your radio.
16:03 < [mbm]> anyway, sbf_flash can't reflash baseband
19:21 < [mbm]> right, sbf_flash has never touched the bp
19:21 < [mbm]> it just skips over those sections of the sbf
It's a great tool, but I think this thread belongs in General.
Click to expand...
Click to collapse
changed guide to reflect correct credits. and agreed. this thread can and should be moved to general.

neer2005 said:
This doesn't work for radio SBFs I believe?
Click to expand...
Click to collapse
Correct, sbf_flash has never flash radio. You will see RDL01 & CG05 don't even upload.
AnalogXDA said:
CWM for radios?
Click to expand...
Click to collapse
Sure. I posted one here for baseband version N_01.100.00R for example. Kudos to SamCripp for discovering we can now CWM the baseband.. in the past, before unlock (and when CWM was not in the recovery partition and ran via the charge_only_mode hack) we could not.
getabetterpic said:
Worked for me in Mac OSX (at least the radio flash)
Click to expand...
Click to collapse
No, it didn't. Prove it to yourself: check the baseband version in about phone. Unless [mbm] in the future adds support for talking to the BP (baseband processor) sbf_flash will not do radio. You will notice the baseband version in 'about phone' doesn't change as you flash different radios.

ceo.mtcl said:
Stop flashing with sbf... You guys have more safer methods using cwm.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Agree 100%
Sent from my unlocked atrix.

This still worked like a charm so thank you.
Sent from my MB860 using XDA App

Any idea if this can be done for other Moto devices as well? What needs to be changed? I tried it as instructed with my Droid Pro using OSX 10.7.3 and it didn't work. Didn't brick my phone or anything. I can post my output if that would help.

BenSWoodruff said:
Any idea if this can be done for other Moto devices as well? What needs to be changed? I tried it as instructed with my Droid Pro using OSX 10.7.3 and it didn't work. Didn't brick my phone or anything. I can post my output if that would help.
Click to expand...
Click to collapse
Old thread here I know but I am looking for some confirmation and maybe someone will answer. I am wanting to flash my phone back but do not have a carried specific SBF (Alltel). I will have to use a Verizon SBF but I don't want to flash the radio. Are we sure that this will not flash the radio so I will not lose my data connectivity?
I ran through the steps with the phone not connected and this is what I see:
SBF FLASH 1.24 (mbm)
http://opticaldelusion.org
=== SBF.sbf ===
00: RDL03 0x82000000-0x8204CFFF B942 AP
01: RDL01 0x00150000-0x001FFFFF DEFA BP
02: CG03 0x00000000-0x00904367 6F6F BP
03: CG31 0xB0280000-0xB02847FF 0EB7 AP
04: CG33 0xB1900000-0xB24C07FF 5CC1 AP
05: CG34 0xB0700000-0xB07047FF 75F3 AP
06: CG35 0xB1000000-0xB13FFFFF 119D AP
07: CG39 0xB2A00000-0xC41C07FF A8ED AP
08: CG42 0xB0800000-0xB083FFFF AC60 AP
09: CG47 0xB1400000-0xB18FFFFF 5728 AP
10: CG61 0xB0B00000-0xB0B7FFFF 5D7F AP
11: CG64 0xB0000000-0xB00047FF 1768 AP
12: CG65 0xB0180000-0xB01847FF 7167 AP
13: CG66 0xD0000000-0xDFFFFFFF 9B93 AP
>> waiting for phone:
Any help???

[GUIDE] Enable Internet Sharing on Omnia 7

Link: "http://bit.ly/sgA8o1" (copy paste this in your browser as i apparently can not post links, sorry!)
Folow the guide on that page or:
Code:
Want that fancy WiFi Hotspot internet sharing Tethering feature on you Windows Phone 7 device? If you are a Samsung Omnia 7 owner today is your lucky day. T-Mobile Germany pushed out a new firmware last night version I8700XXKI4 with the tethering / Internet Sharing feature enabled (thanks for the tip guys!). I’m a nice guy so I grabbed the firmware file and uploaded it so you can manually install it on your handset. Follow the instructions below (same a before and I’m not responsible if it doesn’t work for you):
- Download the firmware here (remember that’s not the OS but only the firmware bits) then download the WPupdate tools from here.
- Unzip the Tools in a folder then unzip the firmware in the same folder as the tools.
- Plug in your device, wait until the Zune client starts and then close it.
- Run the the Updater and press S or B (depending on the size of your balls..)
- your phone will then reboot in download mode and update (don’t unplug it or do stupid things with your PC during the whole process..)
Please note that this won’t work if you are running the latest I8700XXKI3 firmware from SFR (there’s a conflict with the 5.9.1.4 bootloader and maybe others too) so you will have to painfully revert back to an older firmware like the T-Mobile RC1 here (I8700XXKH2).
You should then have the following:
OS Version: 7.10.7720.68
Firmware revision number: 2424.11.9.4
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.9.1
Radio hardware version: 0.0.0.800
Bootloader version: 5.9.3.0
Chip SOC version: 0.36.2.0
Enjoy tethering your handset!
Direct Rom download link: http://bit.ly/rOyGCG
Direct Tools download link: http://bit.ly/sOTNzl
P.s: That is not my guide! I had the French SFR bootloader problem, i reverted as he said and it worked seamlesly. You loose all data though!

didn't work for me, unbranded omnia7
here's error from logs dir "UpdateErrors"
ERROR: E_GENERAL_FILE_COLLISION : File Name: CSC_Config.xml :
Following Package on the Device already contains this file:
Package: CSCPackage FROM Version: 0.0.0.0 TO Version: 2250.19.7389.4880 GUID = {C3AD84D2-E6AB-4FEF-9DC8-C76A9A864731}
But following Update Package is causing a File Collision because it also contains this file and it is trying to add it to the Device :
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\5FF6E1CF-87C8-4B68-A2B6-B7912F7292AE.1.pks\I8700DTMKI4.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.19.7720.6464 GUID = {39813B40-A115-11DF-981C-0800200C9A66}
ProcessGraphs :CheckFileOwnsership returned E_GENERAL_FILE_COLLISSION
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x8018001e
=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
UpdateOrderFromFileList failed with code 0x8018001e
BAD PACKAGE: I8700DTMKI4.cab.pkg ERROR CODE: 0x8018001E Total number of Bad Packages: 1
Process Failed with code 0x8018001e
UpdateValidator finished at 06:30:19 02/28/1980
================================================
START OF ULDR \ UPDATEAPP ERROR MESSAGES
ERROR: 0x8018001e : Updatevalidator in ULDR reported this error. Update cannot continue.
ideas on how to avoid it???

yes, i had the same error, just follow the instructions on that page, install the older mango version

here is the post where you downgrade your mango rom.
http://bit.ly/pK0v0N
Beware!!! If you follow the instructions in that post you will void your warranty, your new rom will be a T-mobile german rom (you will have to manualy change the language in english), t-mobile also will be all over your phone, lot's of crappy apps that you will have to uninstall manualy! Your search provider in internet explorer will be a combination of tmobile and german google, you can change that in the settings menu.
Direct Link for the rom Download http://bit.ly/tvsHop
In the archive you will find a bunch of files.
* WP7 Downloader Ver 7.41 for Publish (Add OASIS Latin).exe
* Samsung_Mobile_USB_Driver(V5.2)_V1.2.1050.0.exe
* PDA_I8700XXKH2_sec.nb0
* I8700XXKG2_02_RC1.bin
* I8700DTMKH2_ENG.PKS
* EBOOT_I8700XXKH2_CO04_REV02_sec.eb0
* CSC_I8700DTMKH2.csc
First unarchive in a folder.
Then install the samsung mobile driver (if you don't already have it)
Open the app WP7 Downloader Ver 7.41
load everything like in the attached photo
put your phone in download mode (with phone turned off press volUp+cameraButton and then power up while keeping those buttons pressed)
connect the phone and press start. Don't do any funny stuff on your pc. I prefer to do that on a laptop with full battery charge and plugged in!
After this install your phone should look like this :
Software: windows phone 7.5
os version: 7.10.7720.68
firmware revision number: 2424.11.8.2
hardware rev number: 3.15.0.4
radio soft. vers.: 2424.11.7.2
radio hardw. vers.: 0.0.0.800
Bootloader: 5.8.0.8
Chip SOC version 0.36.2.0
Now you can update to the new T-mobile rom that has thethering enabled!

thanks for the info but I think i will just wait for an official unbranded update maybe...
My omnia was a branded T-mobile DE before and i unbrande just because i don't like splash screens of something I'm not using
It's like having a bmw with a ducati engine

I have a tablet with no 3g so i was kinda desperate!

[GUIDE] How to build CM10.1 (Android 4.2.1) for the Nexus 4 (mako)

This is a guide to build cyanogenmod 10.1 (Android 4.2.1) for Google Nexus 4. This guide is for linux. I will add a guide to build on mac soon, but the basic principle is the same.
Preparation
You need a fully working build environment. If you don't have one running already, you can follow the official android guide on how to set up build environment. Follow the easy steps in the guide.
Check this guide by sylentprofet about how to get the build environment set up.
Your build environment is now set? Good, let's start!
Get the sources
Start by creating a new working directory for CM10.1. You can create this anywhere on your workstation.
Code:
$ mkdir ~/cm10.1
$ cd ~/cm10.1
£ mkdir -p bin
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync
Wait until it is finished. It will take a long time, depending on your internet connection.
Obtain the device build files and proprietary files:
To do this create a file named 'local_manifest.xml" in the .repo folder. This is a hidden folder, so you have to allow your visualisation of hidden files, alternatively run "open .repo" code from terminal. Or you can just run the code below to create the file directly into the folder.
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
For Mac you can use:
Code:
$ touch ~/cm10.1/.repo/local_manifest.xml
Paste the following lines into the file:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_mako" path="device/lge/mako" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/lge-kernel-mako" path="kernel/lge/mako" remote="github" revision="jellybean"/>
</manifest>
Save the file. And rerun the code:
Code:
$ repo sync
Download the necessary pre-builts:
Code:
$ ~/cm10.1/vendor/cm/get-prebuilts
That's all the sources ready now.
Edits for mac only
If you try building now you will get elf errors when the kernel is being compiled. There are different way for fix this, but I'm using this method.
Go to /kernel/lge/mako/scripts/mod/ folder, open the file 'mk_elfconfig.c' and replace
Code:
#include <elf.h>
with
Code:
#include "elf.h"
. Do the same in the file named 'modpost.h'. Next download the attached file named 'elf.h' and copy to the same folder. You are now ready to build.
Building CyanogenMod
Run the following command:
Code:
$ . build/envsetup.sh
and build by running:
Code:
$ brunch mako
Credits:
CyanogenMod team
Raum1807

Weow, your nice.
I was compiling CM10.1 for my mako and I have this following error
what about that ?
[[email protected] system]# . build/envsetup.sh && brunch mako
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
File "<string>", line 1
import os,sys; print os.path.realpath(sys.argv[1])
^
SyntaxError: invalid syntax
File "build/tools/roomservice.py", line 37
print "Device %s not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod)." % device
^
SyntaxError: invalid syntax
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[[email protected] system]#
Click to expand...
Click to collapse

Happened to me too. Re run ". build/envsetup.sh" and then "brunch mako". Worked for me the second time.
Edit: didn't read the post carefully, looks more like a build environment error
Sent from my Nexus 4 using xda app-developers app

Downgraded make, git and perl on my Arch Linux. Now works

I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium

Good to see another O2X convert here
Good guide, might start building my own stuff again for this phone.

Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?

Is there a guide on how to do cherry picks? Im interested in developing
Sent from my Nexus 4 using xda premium

dosangst said:
Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?
Click to expand...
Click to collapse
Check if you have the file "phone-xhdpi-2048-dalvik-heap.mk" in your repo.
jarjar124 said:
Is there a guide on how to do cherry picks? Im interested in developing
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Go go the gerritt review site, click on 'cherry-pick' and the copy the code displayed underneath. On terminal direct to the required folder and then paste the code on terminal. So if the change is in 'frameworks_base', do 'cd ~/cm10.1/frameworks/base' and then paste the code.

This might help..
https://android.googlesource.com/pl...815362c/build/phone-xhdpi-2048-dalvik-heap.mk
dosangst said:
Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?
Click to expand...
Click to collapse
Imperticus said:
Check if you have the file "phone-xhdpi-2048-dalvik-heap.mk" in your repo.
Go go the gerritt review site, click on 'cherry-pick' and the copy the code displayed underneath. On terminal direct to the required folder and then paste the code on terminal. So if the change is in 'frameworks_base', do 'cd ~/cm10.1/frameworks/base' and then paste the code.
Click to expand...
Click to collapse

I finally got Cm10.1 to build correctly on my own after days and days of troubleshooting. I wish I would have seen this guide earlier! I am having one slight problem though. Every time I sync, it hangs at 99%(353/356). It always hangs up on the last 3 projects. Everything builds fine. I think it has something to do with prop files. I've tried pulling them from the phone and using "The Muppets" github in local_manifest.xml, but it makes no difference. It hangs every time. I've let it sit for hours and nothing. It was syncing all the way through just fine, but a couple days ago it stopped and hasn't synced properly since. If anyone has any ideas I'd greatly appreciate it! Thanks.

how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?

jarjar124 said:
how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?
Click to expand...
Click to collapse
sorry i'm more familiar with mac, not linux.Try 'sudo chmod -R 755 cm-10.1-20121222-UNOFFICIAL-mako.zip'

jarjar124 said:
how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?
Click to expand...
Click to collapse
Why don't you set your build folder in the home directory?

Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.

kjacksonmusic said:
Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.
Click to expand...
Click to collapse
It should work on 12.04, as the cyanogenmod official guides are written for that version of ubuntu. I can't say whether the build environment will remain the same or not.

kjacksonmusic said:
Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.
Click to expand...
Click to collapse
There are different packages to set up the build environment in 12.04 that are listed on googles site. They work. You can upgrade, but you would have to install the new packages. They also work on 12.10 fyi.
I was wondering if anyone has successfully set up the build environment in Mint 14? The packages for 12.04 won't install. If anyone can help, I would be grateful.
Sent from my Nexus 4 using Tapatalk 2

In case anyone is following my upgrade, I upgraded to 12.04 and my Android Working Directory still compiles and builds as well as cm10.1:good:.
Thanks for the help.

kjacksonmusic said:
In case anyone is following my upgrade, I upgraded to 12.04 and my Android Working Directory still compiles and builds as well as cm10.1:good:.
Thanks for the help.
Click to expand...
Click to collapse
Even builds just fine for me on 13.04 mate. Just using the 12.04 required packages.

@OP - could you do a guide on how to build AOSP rom and adding in features from CM?
Many thanks!

[Q] Remote Object '/system/vendor/firmware/wl127X-Fw-4-Plt.bin' Does Not Exist

I've followed the directions here (wiki.cyanogenmod.org/w/Build_for_ovation) to build CyanogenMod 10.2 for the Nook HD+ (ovation). I've gotten all the way to the point where I have to extract the proprietary blobs:
Code:
[email protected]:~/android/system/device/bn/ovation$ ./extract-files.sh
Output from running extract-files.sh said:
Pulling hd-common files...
131 KB/s (13920 bytes in 0.103s)
3 KB/s (178 bytes in 0.056s)
83 KB/s (5444 bytes in 0.063s)
439 KB/s (160764 bytes in 0.357s)
524 KB/s (6876512 bytes in 12.811s)
remote object '/system/vendor/firmware/wl127x-fw-4-plt.bin' does not exist
remote object '/system/vendor/firmware/wl1271-nvs.bin' does not exist
remote object '/system/vendor/firmware/TIInit_7.6.15.bts' does not exist
remote object '/system/vendor/firmware/wl127x-fw-4-mr.bin' does not exist
remote object '/system/vendor/firmware/ini_files/RFMD_D_E5.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_S_2.6.ini' does not exist
remote object '/system/vendor/firmware/ini_files/RFMD_S_3.5.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_D_1.0.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_D_1.7.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_S_2.5.ini' does not exist
remote object '/system/vendor/firmware/wl1271-nvs_127x.bin' does not exist
remote object '/system/vendor/firmware/wl127x-fw-4-sr.bin' does not exist
Pulling omap4470-common files...
141 KB/s (13920 bytes in 0.096s)
3 KB/s (178 bytes in 0.054s)
88 KB/s (5444 bytes in 0.060s)
437 KB/s (160764 bytes in 0.359s)
495 KB/s (6876512 bytes in 13.563s)
remote object '/system/vendor/firmware/wl127x-fw-4-plt.bin' does not exist
remote object '/system/vendor/firmware/wl1271-nvs.bin' does not exist
remote object '/system/vendor/firmware/TIInit_7.6.15.bts' does not exist
remote object '/system/vendor/firmware/wl127x-fw-4-mr.bin' does not exist
remote object '/system/vendor/firmware/ini_files/RFMD_D_E5.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_S_2.6.ini' does not exist
remote object '/system/vendor/firmware/ini_files/RFMD_S_3.5.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_D_1.0.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_D_1.7.ini' does not exist
remote object '/system/vendor/firmware/ini_files/TQS_S_2.5.ini' does not exist
remote object '/system/vendor/firmware/wl1271-nvs_127x.bin' does not exist
remote object '/system/vendor/firmware/wl127x-fw-4-sr.bin' does not exist
Click to expand...
Click to collapse
I have a Nook HD+ with CyanogenMod 10.2 nightly (20140108) connected and working properly. Is this output normal?
I only see the following items in /system/vendor/firmware
ducati-m3.bin
hdcp.keys
smc_pa.ift
Is that normal?
I've searched the forums here, Googled, searched the CyanogenMod forums and posted on Google+. So far no luck. I'm going to try poking in the CyanogenMod nightlies that I have archived and see if there is something there I can manually grab.
Any tips/suggestions would be appreciated. Thanks!

deoren said:
I only see the following items in /system/vendor/firmware
ducati-m3.bin
hdcp.keys
smc_pa.ift
Click to expand...
Click to collapse
I looked at the CyanogenMod 10.2 nightlies, the latest snapshot for 10.2 and the factory 2.2.0 image (NookHDplus-factory-2.2.0-plain-stock.zip) that I found on leapinlar's thread here. The only two files present in the system/vendor/firmware/ folder are:
ducati-m3.bin
smc_pa.ift
I also looked back over the forums here and came across this thread:
COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]​
I recognized the steps listed, but when they got to the extract-files.sh step they did not list any errors or messages stating that some errors/warnings could be ignored.

You must change file 'proprietary-files.txt' (@device/bn/ovation/) and add to it all files from '/system/vendor' and '/system/etc/firmware'
- Blobs should be listed with their path relative to /system on the device
Click to expand...
Click to collapse

minowar age
wesnoth said:
You must change file 'proprietary-files.txt' (@device/bn/ovation/) and add to it all files from '/system/vendor' and '/system/etc/firmware'
Click to expand...
Click to collapse
Thanks for the info.
I went back and looked and saw that most of the files that extract-files.sh couldn't locate were actually in /system/etc/firmware/ instead of /system/vendor/firmware/ where the script attempted to grab them from.
Do you happen to know where I should submit a patch for the file once I correct it? No worries if you don't, just thought I'd check.
I did find one file in the list that was not on the CM 10.2 install:
/system/vendor/firmware/wl1271-nvs_127x.bin
Do you know anything about it?

wesnoth said:
You must change file 'proprietary-files.txt' (@device/bn/ovation/) and add to it all files from '/system/vendor' and '/system/etc/firmware'
Click to expand...
Click to collapse
I meant to also say in my last reply that the proprietary-files.txt file is located here (had to add spaces to url to work around "new account" restriction):
https:// github.com / CyanogenMod/android_device_bn_ovation/blob/cm-10.2/proprietary-files.txt
It uses relative paths like you mentioned, but the entries don't match what my Nook HD+ currently has. Most of the entries also don't match up with the CyanogenMod 10.2 nightlies, the latest snapshot for 10.2 and the factory 2.2.0 image.
After Googling some more I came across this thread:
http://forum.xda-developers.com/showthread.php?t=2535570
where it appears that others have also noticed this behavior. It sounds like they opted to commit their changes to their fork instead of asking for a pull request to fix the errors. They also found that a second file wasn't present (so I must have overlooked one).
Is the appropriate step here for me to fork the repo and submit a pull request with changes? I don't really know my way around Git, but I suppose I could manage.

deoren said:
Thanks for the info.
/system/vendor/firmware/wl1271-nvs_127x.bin
Do you know anything about it?
Click to expand...
Click to collapse
wl1271-nvs_127x.bin and all others for vendor can also be found on verygreens git -> https://github.com/verygreen/propri...cm-10.2/hd-common/proprietary/vendor/firmware

sandsofmyst said:
wl1271-nvs_127x.bin and all others for vendor can also be found on verygreens git -> https://github.com/verygreen/propri...cm-10.2/hd-common/proprietary/vendor/firmware
Click to expand...
Click to collapse
Thanks for that repo link. The rest of my reply is a little verbose in the hope that it will help someone else who runs into this issue.
---
Before you replied I stumbled across this forum thread:
building CM 10.x from source and some questions​
where fanoush showed how to create a new repo manifest to pull in the content via repo sync.
This was done by adding this content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_bn.git" path="vendor/bn" remote="github" revision="cm-10.2"/>
</manifest>
to this repo manifest file:
Code:
~/android/system/.repo/local_manifests/muppets_bn_manifest.xml
After some light research I see that verygreen forked his repo from the TheMuppets repo, but as of Jan 18th both are in sync. Since verygreen seems to be doing the bulk of the work on the CyanogenMod port for the Nook/Nook HD+, I'm going to use his repo instead.
Unless I mistyped something this is how the repo manifest file should look:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="verygreen/proprietary_vendor_bn-1.git" path="vendor/bn" remote="github" revision="cm-10.2"/>
</manifest>
Using the TheMuppets repo I was able to successfully build a CM 10.2 nightly and load it on my Nook. For reference I had to use the ClockworkMod v6.0.3.6 Recovery that leapinlar provided on this thread instead of the v6.0.4.6 that I found on the nook.rootshell.ru/hd/ site. If I tried using the v6.0.4.6 version I got assert errors and installation was aborted.
Once the current build I have running completes I'll switchover to using verygreen's repo.

6.0.4.6 cwm is required for cm11.

[HELP] "OLD" Xiaomi A2 Stuck in Bootloop after UPDATE

! CLOSE PLS !
Hi Guys,
a friend had his bricked A2 lying arround (for a year now i guess) and he gave it to me with the premise: If i can fix it i can keep it.
So now after reading a lot of Threads and Tutorials installing the USB Drivers and ADB Tools i came to the point where i cant find other solutions except the solution where I need to disamble the Phone and do the recovery by the "EDL Method".
I know this topic seems kinda unsolvable and there is a lot of Threads for it, i just wanted to be sure that i didnt miss a thing.
So I appreciate any Help and since i am new to the topic dont be too harsh with me
Device:
-USB Debugging is disabled
-I cant boot in recovery mode (vol-UP+Power) just boots to the white androidOne Screen and there it hangs
- I can enter fastboot(VOL-Down+power) mode
- My bootloader is locked.
I tried to unlock it but since no PC would recognize the Phone there is really no Deal to do anything with it via ADB and or similiar tools (MI FLASH, several deblocking tools)
I installed all necessary Drivers followed several Tutorials. Everything under WIN 10.
My Laptop (and other PCs) wouldnt recognize the Phone at any circumstances (Changed cables and USB Ports).
So i hope that answers some questions upfront.
Thanks for your Help!:fingers-crossed::good:

Did you solved it? i have the same problem too

cesarguaro said:
Did you solved it? i have the same problem too
Click to expand...
Click to collapse
No not really. My PC is recognizing the Phone but still not abled to flash a ROM or anything in this direction. All the commands over ADB are "locked". So i will try the EDL Mode next week and tell you if it worked.

lono.O said:
No not really. My PC is recognizing the Phone but still not abled to flash a ROM or anything in this direction. All the commands over ADB are "locked". So i will try the EDL Mode next week and tell you if it worked.
Click to expand...
Click to collapse
Hi bro, i fixed it my phone, i did a edl flash with the latest global rom stable android 10 and its working, remember on miflash set the option to clean all only...
After that the phone boot up with no issues...

I'm trying to enter EDL mode right now by shorting the two pin, but all I get is either:
"Flashing is not allowed in Lock State"
or "Missmatching image and device"
I'm using jasmine_global_images_V11.0.11.0.QDIMIXM_10.0 with Xiaomi Mi A2.

cnxsoft said:
I'm trying to enter EDL mode right now by shorting the two pin, but all I get is either:
"Flashing is not allowed in Lock State"
or "Missmatching image and device"
I'm using jasmine_global_images_V11.0.11.0.QDIMIXM_10.0 with Xiaomi Mi A2.
Click to expand...
Click to collapse
That`s happen because the edl mode is not detecting well the phone bro... in edl mode the phone must be detected like a port com device... you should check that...
I follow a tutorial on youtube, my device is lock too and with that tutorial i fixed it...
https://www.youtube.com/watch?v=5JaSIKoDDGg&t=107s

Yes, I think the problem is that I can't enter EDL mode. What should be the status of the phone when shorting the two pins? I can't turn it off, so I just put it in Fastboot mode, short the pins, and connect the USB-C from my PC. Is that supposed to work that way? In the video, he says the battery must be disconnected. If that a correct translation? Because I can see his battery is still in place.

cnxsoft said:
Yes, I think the problem is that I can't enter EDL mode. What should be the status of the phone when shorting the two pins? I can't turn it off, so I just put it in Fastboot mode, short the pins, and connect the USB-C from my PC. Is that supposed to work that way? In the video, he says the battery must be disconnected. If that a correct translation? Because I can see his battery is still in place.
Click to expand...
Click to collapse
OK. So the reason was I did not disconnect the battery... Maybe of the instructions on the web forget to mention this little detail...
I can see the Qualcomm COM port, and I can start flashing, but it quickly fails:
Code:
[12:09:44 AM]:3 COM3 12.0139016s resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: SDCC Error 29 (3)"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Write Failed sector 512, size 97"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to write 1 slot 0, partition 512, start_sector 97 num_sectors 0, error 3"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Finished programming start_sector 609 and TotalSectorsToProgram 97"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" />
</data>
Based on what I can see on the web, it looks like an hardware error (flash related). Not really surprised as the phone started to get fairly slow recently, and almost always full.
I've bought a new phone, since Xiaomi Mi A2 looks dead. I haven't had very good experience so far with Xiaomi. A1 lasted about a year due to eMMC flash failire, and A2 for about 20 months.