Database Info

[Q] Need help, bricked my Atrix 2

OK so I pulled a stupid move and flashed my phone with this data:
p3droid
Chief Of Staff
--------------------------------------------------------------------------------
Join Date: Dec 2009
Location: Arizona
Posts: 1,329
Device: Motorola DroidThanks: 9Thanked 1,369 Times in 119 PostsDownloads:0 Uploads:0
How to get your phone back on the upgrade path...
If you have been flashing things (and who hasn't) when the official update comes out you will want to be on the correct builds so that you can take it. I present you with the method that will get you back and allow you to take any update.
This has only been tested on Windows 7 (32/64)
1) Download this fastboot file moto-fastboot-win32.zip
2) Download this Zip (Contains both System and webtop images) Download Now
3) Create a folder on Desktop named "Stock" <----- can be anything you want
4) Place the contents of both zip files in the folder named Stock
5) Put phone in Fastboot mode, connect to computer
6) Open a command terminal and go to the Stock folder (cd Desktop/Stock)
7) type this command in the terminal window and wait for the flashing to finish before going to the next line.
----> moto-fastboot.exe flash webtop grfs.img (This file will be flashed in 4 parts)
----> moto-fastboot.exe flash system system.img (This file will be flashed in 2 parts)
----> moto-fastboot.exe reboot
************************************************** ****************
Your boot image (kernel) and radio files will never go back to stock !!!
************************************************** ****************
Your phone is now back on stock (well the parts that matter anyways) Congratulations.
Next post will tell you how to root your device!!
Now I get this:
fastboot flash mode (s) (boot failure)
battery is low
cannot program
transfer mode:
USB Connected
invalid cg otv (cg: system): Invalid sp data
invalid cg hab (cg system, status: 0x0035)
invalid cg otv (cg: system)
Looks like I need a proper webtop.img and system.img?

Perfect example of why you should read the whole thread before trying to apply a mod/tweak/update to your phone if you don't know what you're doing. Or did you not realize the forum that thread was posted in was for the Droid Bionic? That site doesn't even have an Atrix 2 forum so why you would attempt any of the mods for those other devices to yours is beyond me. Bet you won't do that again

Nope wont do that again. Thought I got there from an A2 link saying the root worked. Anyways, any help would be great.

msumrell said:
Nope wont do that again. Thought I got there from an A2 link saying the root worked. Anyways, any help would be great.
Click to expand...
Click to collapse
Like I said, perfect example of why you should read the whole thread first! The very last comment in that posts says "the next post will tell you how to root your device." That should have been a hint that what you were about to do was not what you wanted to do.

Sorry bud, no way to recover the phone at this point.

Ao there are no system images available? Is it something that will come available with time maybe?

msumrell said:
Ao there are no system images available? Is it something that will come available with time maybe?
Click to expand...
Click to collapse
No sir, that's one of the things we're waiting for to start flashing stuff.....the other is the actual ability to flash stuff, lol.

msumrell said:
Ao there are no system images available? Is it something that will come available with time maybe?
Click to expand...
Click to collapse
If you bought it at Best Buy in the last 30 days run, don't walk, to Best Buy and give them $9.95 for a month of coverage. Then they will replace the phone, even bricked

Unless you take it in and return it you have a paper weight for the time being. I would take it in myself, the worst they can do is say no.

There's sbf leak from china. It's worth trying to flash it with RSD Lite 5.6
http://forum.xda-developers.com/showthread.php?p=19745460#post19745460

Semseddin said:
There's sbf leak from china. It's worth trying to flash it with RSD Lite 5.6
http://forum.xda-developers.com/showthread.php?p=19745460#post19745460
Click to expand...
Click to collapse
Please! You have nothing to lose. Is the bootloader unlocked on the chinese version?
Sent from my MB865 using XDA App

916x10 said:
Please! You have nothing to lose. Is the bootloader unlocked on the chinese version?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
are you not able to get into the boot menu and select factory reset at this point?

razholio said:
are you not able to get into the boot menu and select factory reset at this point?
Click to expand...
Click to collapse
I can, my phone is fine.
Sent from my MB865 using XDA App

when I try to load this file 'edison_china_5.5.1-1_GC-86_EDSCHN-6_cfc.xml' on RSD Lite 5.6 it says .xml wrong format or missing files. this is the contents of the .xml I need help on how to use it I guess.
--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="EDISON" />
<software_version version="edison-user 2.3.5 5.5.1-1_GC-86_EDSCHN-6 6 release-keys2011-10-25 16:56 Off.Bld LUD_EDISON_R1E_PATCH_10_111025_1636 crh1090280_M570_PC_CARD_RAINB" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="reboot-bootloader" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin" MD5="baca44d9b608e6c1cce61d535377ad78" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="lbl" filename="lbl" MD5="517bf626d45934f8fbb75c448f6dc711" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617" />
<step operation="flash" partition="ebr" filename="ebr" MD5="99bd0461bf959c636b087afd7768868f" />
<step operation="flash" partition="mbr" filename="mbr" MD5="8e89b3905532099d0a0a11f2ea7bedce" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="1c0acd25a4de4074d572f6baf877df5d" />
<step operation="flash" partition="system" filename="system.img" MD5="b1901a6d1e944befb83dd7549669a352" />
<step operation="flash" partition="boot" filename="boot.img" MD5="3d898516a4d226f1b138fa231a91d225" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="029c71633dbb8f1f92523250d7d325bc" />
<step operation="erase" partition="cache" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="9a470c15978f2d6e22bb606849574a7a" />
<step operation="flash" partition="radio" filename="radio.img" MD5="530c92abd1c2e4650e65106a4bf9dddf" />
<step operation="flash" partition="webtop" filename="grfs.img" MD5="dabfc21a52e4034333ed5a8501b2e02b" />
</steps>
</flashing>

OK so I got the xml file to load in RSD Lite after redownloading it. However it will not flash on the phone. I get this message.
Failed flashing process 2/15 flash cdt.bin "cdt.bin" ->Phone returned FAIL ;phone connected

How are you getting the phone into RSD protocol mode? I tried doing it the same way as my OG ATRIX and don't get the option?
Nevermind I take it you're using AP fastboot mode? Went and dug around the RZR forums to see how they were doing it. You do have all the current Motorola drivers installed? I had problems with my OG ATRIX and had to uninstall them and reinstall them before getting it to work properly.

Null 10 char

Should be the same steps as the bionic.
Pretty cut and dry, make sure you're plugging it directly into your motherboard's usb ports.
It could simply not be compatible or signed with different keys...
Installation
1.Install the Motorola Mobile Drivers
2.Install RSD Lite 5.5
3.Make sure your Motorola Droid Bionic is powered on and backed up.
◦Alternatively, boot into AP Fastboot mode by powering down (or pulling battery), then press and hold the volume down button while powering on. From there, continue with Step 4.
4.Plug your Motorola Droid Bionic into a back USB port on your computer.
◦Front USB ports are often unreliable when it comes to power levels. They should not be used for flashing.
5.Run “RSD Lite” on your computer
6.Press the “. . .” button next to the box labeled “Filename”
7.Browse and open the FXZ file
8.Wait for the program to read the file, then choose “Uncompress And Start Flashing”
9.Now, the device will slowly flash the FXZ file.
10.When flashing completes, the device will reboot into recovery and install the two radio images.
11.Congratulations! You’ve restored your Motorola Droid Bionic
Click to expand...
Click to collapse

Msumrell, i hope this works then atleast we have something to fall back on if somebody brick's there phone. Good luck!
Sent from my MB865 using xda premium

at this point I have to say it does not work. I have tried from different usbs and get the same results. failed. It is certainly an easy enough process. A am guessing it is not a compatable image? dont know. I also tried just loading teh system.img and grfs.img with moto-fastboot in a dos window and no go their either. Keep waiting for good image I guess.

[GUIDE] Enabling Apps for Pen Window without ROOT

Hello Friends,
Just want to share another GUIDE/MOD this time for NON-ROOT users - ENABLING Apps for PEN Window without Root.
Without root, the only way to add more apps for Pen Window is modifying the app yourself or getting developers to add pen window support to their apps. But it involves a bit of knowledge in decompiling, editing, recompiling and resigning apps with apktool, jarsigner or some similar tool like Apk Manager, Apk Multitool and a lot others. I won't go into a tutorial about decompilation. I was a noob once and I did my best to search and learn about this stuff so if you are interested then a few google or xda search would give you tons of links on how to decompile/recompile apk files.
TOOLS:
1. Knowledge of modding apk files
2. ApkManager or other similar tools
3. Notepad++ or something similar
GUIDE:
1. Decompile apk file using ApkManager or your tool of choice.
2. Open the AndroidManifest.xml file of the decompiled apk file using Notepad++ or your editor of choice. Below is a sample AndroidManifest.xml file.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
3. Look for the acivity which has "<category android:name="android.intent.category.LAUNCHER" />"
and add "<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />" below it.
Below is the same AndroidManifest.xml above with the change highlighted in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
</application>
</manifest>
4. Look for "</application>" which is the closing tag of the <application...> node. Then add
"<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />" above it. Below is the same AndroidManifest.xml file above with the all changes in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
[COLOR="Red"]<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />[/COLOR]
</application>
</manifest>
5. Recompile and Resign apk file and push to your phone. If you are using ApkManager that is all done in one go with option 14 while phone is connected.
6. Have FUN! A COFFEE would be Nice. he he
THANKS to @soloilmeglio for testing and making sure it works before I write and share this guide.

Great news for all non-rooted gn3 eh eh.... great work as always
Inviato dal mio SM-N9005 utilizzando Tapatalk

So is it possible for you to do an app that automaticly does the magic?
Like some drag and drop .apk to make it work on penwindow (and why not in multiwindow too?)

Thanks, it works

I got it work only in one app (tried for ~5 apps)
Dunno if the problem is using APK Multi-Tool instead of ApkManager? And I believe problem is in .apk or tool.. Not in your guide
And why I can't find those lines already in app that has multiwindow, pen window or both already? How those are made then?
But thanks anyway very useful guide
ps. Didn't try to only add pen window, but multiwindow too at same time
Sent from my SM-N9005 using XDA Premium HD app

Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....

Amdathlonuk said:
Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....
Click to expand...
Click to collapse
It's not that hard really, it took a while for me but even I managed to make it work
If you got Java JDK and ADB installed (Google how to install if not)
Google APK Multi-Tool, you'll find a link to some topic on XDA where is download link (and instructions how to use it)
When you got all ready and multi tool running, type 24 and enter, choose your apk file (if you have that apk on computer and moved to Multi-Tool apk edit folder) and enter again. Then type 9 and enter to decompile, go to projects folder and edit AndroidManifest.xml. Then delete that app from your phone if already installed, connect your phone to pc using USB cable and then type 15 in Multi-Tool and hit enter. Now it should compile, sign and install that app to your phone, if everything went right.
Sorry for messy message but I'm at work. Ask if somethings not clear to you
Sent from my SM-N9005 using XDA Premium HD app

Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse

erlos said:
Add the red string under penwindow tweak and you unlock Multiwindows too
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
Click to expand...
Click to collapse
would anything of this work with Waze?

valtersboze said:
would anything of this work with Waze?
Click to expand...
Click to collapse
?????
I did Not understand...
This is OLD tips on note 1
Inviato dal mio SM-N9005 utilizzando Tapatalk

erlos said:
?????
I did Not understand...
This is OLD tips on note 1
Click to expand...
Click to collapse
before i spend hours trying to figure out the apk tool - i wanted to ask if anyone has applied the penwindow/multiwindow tags to Waze apk and if it works. In city driving waze is critical to be open but it is waste of screen real estate to see just waze. i would like whatsapp or music apps open and visible too.

I Will be try later!
Inviato dal mio SM-N9005 utilizzando Tapatalk

nice work...

itworks thanks

What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?

Dewdropkorn said:
What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?
Click to expand...
Click to collapse
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />

Spere said:
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:

Thanks
Sent from my SM-N900 using XDA Premium 4 mobile app

Dewdropkorn said:
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:
Click to expand...
Click to collapse
Nice to hear it works
Sent from my SM-N9005 using XDA Premium HD app

Has anyone done this with Spotify? I've successfully modded about 6 apps now but the .apk I recompiled and signed for Spotify has "parsing" errors when I try to installing it. Anyone else with better luck?

[Q&A] [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for

[Q&A] [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for
Q&A for [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for falcon
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Ubuntu Touch - Utopic][PORT]STOPED][Test-BUILD][2014-08-27] Ubuntu Touch for falcon. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Is there any way to flash the boot.img and system.img using multirom. I found about multirom installer (*.mrom files). But didn't had any luck with it.

I tried to compile the Android pieces on my own but I get an error with libmake_f2fs_intermediates:
make: *** No rule to make target `<.....>/out/target/product/falcon/obj/STATIC_LIBRARIES/libmake_f2fs_intermediates/export_includes', needed by `<.....>/out/target/product/falcon/obj/EXECUTABLES/recovery_intermediates/import_includes'. Stop.
I checked out the Ubuntu Touch code using Canonical's manifest. I did not use h2o64's manifest.
In my local manifest I added the CyanogenMod projects for falcon, as well as dependencies:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="github" />
<project name="cyanogenmod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />
<remove-project name="aosp/platform/hardware/qcom/display" />
<project name="cyanogenmod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" revision="cm-11.0" />
<remove-project name="aosp/platform/hardware/qcom/media" />
<project name="cyanogenmod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
Apart from that I did not make any changes. Just trying to get the sources compiled.
Can somebody tell me why I get this error and how to fix it?

The system is restarting all the time
I followed all the steps of the fórum and the system is restarting all the time

multirom
is it possible to install the ubuntu touch image via multirom manually?

Errors during build
I have finished downloading the sources including your local manifest. Now I am trying to build and will report some errors here. Once I have a successful build, I am happy to share logs (if accessible) and help debugging.
I directly encountered this error:
build/core/base_rules.mk:134: *** hardware/qcom/display/msm8x26/liblight: MODULE.TARGET.SHARED_LIBRARIES.lights.msm8226 already defined by device/motorola/falcon/liblight. Stop.
So I renamed old module to lights.msm8226.old
hardware/qcom/display/msm8x26/liblight/Android.mk:160:
LOCAL_MODULE := lights.$(TARGET_BOARD_PLATFORM).old
No the build process stops after only a few lines with:
make: *** No rule to make target `[...]/Ubuntu_Touch/out/target/product/falcon/kernel', needed by `prebuilt'. Stop.
---------- Post added at 07:50 PM ---------- Previous post was at 07:40 PM ----------
I also noticed that not all the dependent projects are added in the local manifest.
android_device_motorola_falcon
depends on
android_device_motorola_msm8226-common
depends on
android_device_qcom_common
android_kernel_motorola_msm8226
android_hardware_qcom_fm
android_hardware_qcom_display-caf-new
android_hardware_qcom_media-caf-new
Will add the missing ones and try to build again.
Edit: Just saw that you included the files already in device/motorola/falcon.

the_MUKe said:
I have finished downloading the sources including your local manifest. Now I am trying to build and will report some errors here. Once I have a successful build, I am happy to share logs (if accessible) and help debugging.
I directly encountered this error:
build/core/base_rules.mk:134: *** hardware/qcom/display/msm8x26/liblight: MODULE.TARGET.SHARED_LIBRARIES.lights.msm8226 already defined by device/motorola/falcon/liblight. Stop.
So I renamed old module to lights.msm8226.old
hardware/qcom/display/msm8x26/liblight/Android.mk:160:
LOCAL_MODULE := lights.$(TARGET_BOARD_PLATFORM).old
No the build process stops after only a few lines with:
make: *** No rule to make target `[...]/Ubuntu_Touch/out/target/product/falcon/kernel', needed by `prebuilt'. Stop.
---------- Post added at 07:50 PM ---------- Previous post was at 07:40 PM ----------
I also noticed that not all the dependent projects are added in the local manifest.
android_device_motorola_falcon
depends on
android_device_motorola_msm8226-common
depends on
android_device_qcom_common
android_kernel_motorola_msm8226
android_hardware_qcom_fm
android_hardware_qcom_display-caf-new
android_hardware_qcom_media-caf-new
Will add the missing ones and try to build again.
Edit: Just saw that you included the files already in device/motorola/falcon.
Click to expand...
Click to collapse
I'm fixing things guys
Wait
(I'll tell here when the major issues (building issues) are fixed
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
the_MUKe said:
I tried to compile the Android pieces on my own but I get an error with libmake_f2fs_intermediates:
make: *** No rule to make target `<.....>/out/target/product/falcon/obj/STATIC_LIBRARIES/libmake_f2fs_intermediates/export_includes', needed by `<.....>/out/target/product/falcon/obj/EXECUTABLES/recovery_intermediates/import_includes'. Stop.
I checked out the Ubuntu Touch code using Canonical's manifest. I did not use h2o64's manifest.
In my local manifest I added the CyanogenMod projects for falcon, as well as dependencies:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="github" />
<project name="cyanogenmod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
<project name="cyanogenmod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />
<remove-project name="aosp/platform/hardware/qcom/display" />
<project name="cyanogenmod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" revision="cm-11.0" />
<remove-project name="aosp/platform/hardware/qcom/media" />
<project name="cyanogenmod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
Apart from that I did not make any changes. Just trying to get the sources compiled.
Can somebody tell me why I get this error and how to fix it?
Click to expand...
Click to collapse
You forgot to add "CyanogenMod/android_external_f2fs-tools" revison cm-11.0
And include it in main.mk

KMSG log file
I hope it's useful.
Logfile is attached.
thx

omniaholic said:
I hope it's useful.
Logfile is attached.
thx
Click to expand...
Click to collapse
The last build is useless and outdated
But thank you for sending. I'll notificate you when a new build will come

Update on build process
First thanks for the responses. Indeed I forgot to add the subdir in main.mk before. However, now I making sure that all subdirs are included...
Just to inform you about what I have done so far. I started building based on the phablet repo and added my own local manifest (attached).
added device/motorola/falcon and dependencies
copied vendor/motorola from existing (and recent) CyanogenMod
added subdirs in build/core/main.mk
added external/f2fs-tools
removed APKs and JARs from vendor/motorola/msm8226-common/proprietary
replaced hardware/qcom/keymaster with CyanogenMod version (some error with original keymaster)
replaced all hardware/qcom project with CyanogenMod versions (helpful?)
Workaround: deleted gps from device/motorola/msm8226-common (libnativehelper would be required, plus several undeclared constants)
Workaround: force include of all subdirs in device/qcom/common/Android.mk (dtbToolCM is required)
Workaround: deleted power in device/qcom/common (some undeclared constants)
Now the build process runs through but there are errors with creating the recovery image and the boot image.
However, I noticed that h2o64 made some changes to android/system/core, in particular mkbootimg. So I will see if I can also use the CyanogenMod version here.
If anyone has better solutions for these Workaround items, please let me know.

the_MUKe said:
First thanks for the responses. Indeed I forgot to add the subdir in main.mk before. However, now I making sure that all subdirs are included...
Just to inform you about what I have done so far. I started building based on the phablet repo and added my own local manifest (attached).
added device/motorola/falcon and dependencies
copied vendor/motorola from existing (and recent) CyanogenMod
added subdirs in build/core/main.mk
added external/fsf2-tools
removed APKs and JARs from vendor/motorola/msm8226-common/proprietary
replaced hardware/qcom/keymaster with CyanogenMod version (some error with original keymaster)
replaced all hardware/qcom project with CyanogenMod versions (helpful?)
Workaround: deleted gps from device/motorola/msm8226-common (libnativehelper would be required, plus several undeclared constants)
Workaround: force include of all subdirs in device/qcom/common/Android.mk (dtbToolCM is required)
Workaround: deleted power in device/qcom/common (some undeclared constants)
Now the build process runs through but there are errors with creating the recovery image and the boot image.
However, I noticed that h2o64 made some changes to android/system/core, in particular mkbootimg. So I will see if I can also use the CyanogenMod version here.
If anyone has better solutions for these Workaround items, please let me know.
Click to expand...
Click to collapse
Changing hardware/qcom was a BIG mistake!
Revert it and try to change things line by line.
Anyway! Good job!

Accessing the boot log...
@h2o64: Great to hear that you made progress!
In my repo I managed to finish the build process. I flashed the boot.img and ran the rootstock-touch-install script without errors. I needed to raise the size of the ext4fs: make_ext4fs -l 256M $WORKDIR/system.img $TMPMOUNT
The 256M are just a value I put in there, no idea which value would be best.
Unfortunately, when booting the device, the screen remains at the Motorola logo.
I bootet into recovery and took the dmesg output. Not sure whether this also includes the previous boot log or only the log of booting into recovery...
In the Ubuntu Wiki in the Deprecated Porting Guide they suggest to look at /proc/last_kmsg
In the Debug section they also recommend to pass command line arguments to the kernel:
If you encounter initrd issues while booting you can add to your kernel boot arguments the following line "break=top"...
This should then pause the boot process and open an adb shell.
But in which file can I set the kernel arguments? There are several config files in the kernel directory...
Well, as soon as h2o64 has finished updating his repo, I will try with his local manifest. And then try to provide boot logs, etc.

the_MUKe said:
@h2o64: Great to hear that you made progress!
In my repo I managed to finish the build process. I flashed the boot.img and ran the rootstock-touch-install script without errors. I needed to raise the size of the ext4fs: make_ext4fs -l 256M $WORKDIR/system.img $TMPMOUNT
The 256M are just a value I put in there, no idea which value would be best.
Unfortunately, when booting the device, the screen remains at the Motorola logo.
I bootet into recovery and took the dmesg output. Not sure whether this also includes the previous boot log or only the log of booting into recovery...
In the Ubuntu Wiki in the Deprecated Porting Guide they suggest to look at /proc/last_kmsg
In the Debug section they also recommend to pass command line arguments to the kernel:
If you encounter initrd issues while booting you can add to your kernel boot arguments the following line "break=top"...
This should then pause the boot process and open an adb shell.
But in which file can I set the kernel arguments? There are several config files in the kernel directory...
Well, as soon as h2o64 has finished updating his repo, I will try with his local manifest. And then try to provide boot logs, etc.
Click to expand...
Click to collapse
You made a very impressive work
Last_kmsg is the best we can take... The kernel patch... Hmm... It's not fit me.
To be honest I'm kind of lazy xD
I need to redo the hardware qcom part..
Do you have hangout? We can talk about it with more serious details?

hardware/qcom projects
No, I don't use Hangouts. Maybe IRC might do?
But I am also fine to post the (bigger) issues here. Then also somebody else could possibly find a solution.
The hardware/qcom part seems to be indeed a bit tricky.
When using the projects from Ubuntu Touch repo, eventually some kernel headers cannot be found, e.g. a file inside hardware/qcom/display/... includes "linux/msm_ion.h" which cannot be found.
I tried manually setting the kernel_includes in hardware/qcom/display/msm8x26/common.mk: kernel_includes := kernel/motorola/msm8226/include
But this only leads to multiple C++ errors like: narrowing conversion of 'dst->copybit_image_t::w' from 'const uint32_t {aka const unsigned int}' to 'int' inside { } is ill-formed in C++11 [-Werror=narrowing]
Also the liblight module is duplicated (but one can easily be renamed).
These problems do not occur when using the corresponding projects from CyanogenMod instead.
I am still undecided whether to stick to the original Ubuntu Touch projects for hardware/qcom or better go consistently with all the hardware/qcom projects from CyanogenMod. Not sure which other interdependencies exist there...

the_MUKe said:
No, I don't use Hangouts. Maybe IRC might do?
But I am also fine to post the (bigger) issues here. Then also somebody else could possibly find a solution.
The hardware/qcom part seems to be indeed a bit tricky.
When using the projects from Ubuntu Touch repo, eventually some kernel headers cannot be found, e.g. a file inside hardware/qcom/display/... includes "linux/msm_ion.h" which cannot be found.
I tried manually setting the kernel_includes in hardware/qcom/display/msm8x26/common.mk: kernel_includes := kernel/motorola/msm8226/include
But this only leads to multiple C++ errors like: narrowing conversion of 'dst->copybit_image_t::w' from 'const uint32_t {aka const unsigned int}' to 'int' inside { } is ill-formed in C++11 [-Werror=narrowing]
Also the liblight module is duplicated (but one can easily be renamed).
These problems do not occur when using the corresponding projects from CyanogenMod instead.
I am still undecided whether to stick to the original Ubuntu Touch projects for hardware/qcom or better go consistently with all the hardware/qcom projects from CyanogenMod. Not sure which other interdependencies exist there...
Click to expand...
Click to collapse
I did fix it on the previous release. I'll do it again.

the_MUKe said:
No, I don't use Hangouts. Maybe IRC might do?
But I am also fine to post the (bigger) issues here. Then also somebody else could possibly find a solution.
The hardware/qcom part seems to be indeed a bit tricky.
When using the projects from Ubuntu Touch repo, eventually some kernel headers cannot be found, e.g. a file inside hardware/qcom/display/... includes "linux/msm_ion.h" which cannot be found.
I tried manually setting the kernel_includes in hardware/qcom/display/msm8x26/common.mk: kernel_includes := kernel/motorola/msm8226/include
But this only leads to multiple C++ errors like: narrowing conversion of 'dst->copybit_image_t::w' from 'const uint32_t {aka const unsigned int}' to 'int' inside { } is ill-formed in C++11 [-Werror=narrowing]
Also the liblight module is duplicated (but one can easily be renamed).
These problems do not occur when using the corresponding projects from CyanogenMod instead.
I am still undecided whether to stick to the original Ubuntu Touch projects for hardware/qcom or better go consistently with all the hardware/qcom projects from CyanogenMod. Not sure which other interdependencies exist there...
Click to expand...
Click to collapse
I start working back on it.
Check my github

Will download your .img files, flash them and provide my last_kmsg log.
Will probably also build it using your manifest - just to check if build goes through also on my machine (Ubuntu 14.04 64-bit).
I noticed in the recent log provided by Awesomeslayerg that the init process could not find a system partition:
[ 4.326129,1] initrd: Couldn't find a system partition.
It's towards the end of the log. There were a few other errors but this might be a critical one?
I also had this error with my previous build (when using all hardware/qcom projects from CyanogenMod).
And did you make any changes in the rootstock-touch-install script?

It will work on 5.0.1 lollipop bootloader??

Results with provided .img files
The recovery you provided is not working in my case - I get a blank screen. So I flashed back to TWRP.
I actually had the Ubuntu recovery (a reduced CWM with Ubuntu Logo) working when using all hardware/qcom projects from CyanogenMod.
I also flashed your boot.img and used the rootstock-touch-install script to get the system.img together with vivid files onto the phone. The script finished very fast but all steps were completed.
When booting up, the phone gets stuck while the Motorola logo is still showing.
So I rebooted into recovery and obtained the last_kmsg log (attached).

the_MUKe said:
The recovery you provided is not working in my case - I get a blank screen. So I flashed back to TWRP.
I actually had the Ubuntu recovery (a reduced CWM with Ubuntu Logo) working when using all hardware/qcom projects from CyanogenMod.
I also flashed your boot.img and used the rootstock-touch-install script to get the system.img together with vivid files onto the phone. The script finished very fast but all steps were completed.
When booting up, the phone gets stuck while the Motorola logo is still showing.
So I rebooted into recovery and obtained the last_kmsg log (attached).
Click to expand...
Click to collapse
Very nice.
Yeah... My hardware display & media are weirdly inconsistent... I'll redo them
Thanks for your report!
(please, speak on the main thread )
---------- Post added at 12:03 AM ---------- Previous post was at 12:03 AM ----------
ADr0n said:
It will work on 5.0.1 lollipop bootloader??
Click to expand...
Click to collapse
Nope

[Completed] [Q] Weird error after "lunch"ing on AOSPB build.

Hey!
I am trying to port AOSP-B to my LG G4. I added the following to my manifext.xml follow and synced
Code:
<remote name="mups" fetch="https://www.github.com/themuppets" revision="cm-13.0" />
<remote name="cm"
fetch="https://github.com/cyanogenmod"
revision="cm-13.0" />
<project path="device/lge/h811" name="android_device_lge_h811" remote="cm" />
<project path="device/lge/g4-common" name="android_device_lge_g4-common" remote="cm" />
<project path="kernel/lge/msm8992" name="android_kernel_lge_msm8992" remote="cm" />
<project path="vendor/lge" name="proprietary_vendor_lge" remote="mups" />
and synced up. Everything I added was there. Perfect!
I run "./build/envsetup.sh" and everything goes fine.
I type "lunch" and see my device
Code:
8. cm_h811-userdebug
I hit "8" and get this:
Code:
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
Device h811 not found. Attempting to retrieve device repository from AOSPB Github (http://github.com/AOSPB).
Repository for h811 not found in the AOSPB Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/aospb_manifest.xml
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
** Don't have a product spec for: 'cm_h811'
** Do you have the right repo manifest?
Where could I go wrong? I know since I'm building AOSP that it's probably missing something from CM. What would I need to add? I've already reached out to a dev that ported this AOSPB to the G3 with no response yet.
I did not modify anything I downloaded. Just sync and build.
Any ideas?

bradym512 said:
Hey!
I am trying to port AOSP-B to my LG G4. I added the following to my manifext.xml follow and synced
Code:
<remote name="mups" fetch="https://www.github.com/themuppets" revision="cm-13.0" />
<remote name="cm"
fetch="https://github.com/cyanogenmod"
revision="cm-13.0" />
<project path="device/lge/h811" name="android_device_lge_h811" remote="cm" />
<project path="device/lge/g4-common" name="android_device_lge_g4-common" remote="cm" />
<project path="kernel/lge/msm8992" name="android_kernel_lge_msm8992" remote="cm" />
<project path="vendor/lge" name="proprietary_vendor_lge" remote="mups" />
and synced up. Everything I added was there. Perfect!
I run "./build/envsetup.sh" and everything goes fine.
I type "lunch" and see my device
Code:
8. cm_h811-userdebug
I hit "8" and get this:
Code:
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
Device h811 not found. Attempting to retrieve device repository from AOSPB Github (http://github.com/AOSPB).
Repository for h811 not found in the AOSPB Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/aospb_manifest.xml
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
** Don't have a product spec for: 'cm_h811'
** Do you have the right repo manifest?
Where could I go wrong? I know since I'm building AOSP that it's probably missing something from CM. What would I need to add? I've already reached out to a dev that ported this AOSPB to the G3 with no response yet.
I did not modify anything I downloaded. Just sync and build.
Any ideas?
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for XDA Assist.
This is not a help desk. XDA Assist is a place for new members to get help finding their way. Our purpose is to provide a link to where they should post and get the help they seek. As a Senior member, you are expected to be able to use the search feature and ask in the correct forum yourself.
Thanks.
Thread closed.

Building CM 13 CAF

Hello, I'm trying to build cm 13 caf rom myself (i have never done it before) and I'm following this guide. I have done everything to the step "download the source code" from https://github.com/CyanogenMod/android.git. Now I should "Prepare the device-specific code", but the guide is for hammerhead CM (non-caf) and, if I'm right, I should add some local_manifests but I have no idea of how to do this. (in fact if I type $ breakfast hammerheadcaf it starts downloading and then it says
** Don't have a product spec for: 'cm_hammerheadcaf'
** Do you have the right repo manifest?)
Can anyone explain it to me, please?

Hello apon97!
You can search the CAF thread a bit - a lot of question regarding building CyanogenMod for hammerheadcaf have been already covered there. However, the thread is huge and searching it is a pain in the b*tt sometimes so I'll try to help you here.
You have to know the following:
Downloading the source code will 'only' download the default projects. This usually takes a few hours to download depending on your internet connection. However, to build for a specific device (hammerheadcaf in this case) you also have to get two more things: It's dependencies (device- and kernel-tree) and the vendor proprietary files - usually simplified as 'blobs'.
So after you've downloaded the source code you don't have any local manifests. A simple 'breakfast hammerheadcaf' will look for cm.dependencies in the device-tree and automagically add these to your default local manifest (called 'roomservice.xml').
The proprietary stuff has to be manually added to the local manifest. Just open up /SOURCE/.repo/local_manifests.xml and you should see that the kernel and device tree is already there (because you breakfasted...). Now add another line for the blobs. These can be found on TheMuppets: github.com/TheMuppets/proprietary_vendor_lge
So your local manifest 'roomservice.xml' should look something similar to this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
PS: myfluxi updated the proprietary files for hammerheadcaf on his personal GitHub. You're free to use this project instead if you want to be up-to-date. However, he says that we don't need necessarily up-to-date blobs. Then the last project would look like this:
Code:
<project name="myfluxi/proprietary_vendor_lge" path="vendor/lge" remote="github" />
Now you have everything set up and ready to build CM13 CAF for the Nexus 5!
You don't have to go through this everytime you want to build. Next time just use
'repo sync'
'source build/envsetup.sh'
Optionally 'make clean' or 'make clobber' <- This will delete stuff from previous builds. Doing a clean build will take longer...
and finally...
'brunch hammerheadcaf'
Much fun building!

Everything looks clear. Yes, I have searched your thread but couldn't find the answer (maybe I could have tried a little more). I hope I will not have to bother you anymore
Thank for such a complete answer and for everything you do for our Nexus 5

Yeah I know, the thread is a bit messy but I can't do anything about it
Don't hesitate to ask if you need a bit more help