[5.x] External Storage as Internal - Moto E Android Development

Hi guys, i'm working on it
I use External SD as internal in lollipop, the question is if there are any risks doing that!!!
http://source.android.com/devices/storage/config.html#android_5_x_and_earlier
storage list xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<StorageList
xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_internal" android:emulated="true" android:mtpReserve="100" />
<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
</StorageList>
Check that please and tell me if there is any risk using it, if not, i'll upload it soon!!
If you want to use it in AOSP 5.1.1 last build
Try and report
Download and flash it
XDA:DevDB Information
[5.x] External Storage as Internal , ROM for the Moto E
Contributors
ivan290
ROM OS Version: Lollipop
Version Information
Status: Alpha
Created 2015-11-10
Last Updated 2015-11-10

the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")

brundark said:
the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")
Click to expand...
Click to collapse
Could you upload a logcat?

So if I flash this on top of my present ROM, Do I get access to external SD as internal storage?

brundark said:
the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")
Click to expand...
Click to collapse
To fix it you only have to wait until the android starts to "omptimize apps"

Is this working??? Or needs more work to be done??

Exactly what does this do?
Does it work without any issues?
Can we install heavy space consuming games?

confused.
where is the method?

Thread closed - members are advised to exercise caution with this.

Related

[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.

[CWM] Updated 9/21/13 All variants CWM recovery

This recovery is CWM for the One SV. It is fully working and has no problems. All variants are supported below
K2_CL (Boost Mobile) -> Boost Download
K2_PLC_CL (Cricket) -> Cricket Download
K2_UL (EU LTE) -> EU LTE Download
K2_U (EU NON-LTE) -> EU Non-LTE Download
Sources:
Boost Mobile Source
Cricket Source
EU LTE Source
EU Non-LTE Source
To build these recoveries on your own, simply follow the directions below:
Clone the CyanogenMod repo. See their wiki at http://wiki.cyanogenmod.org
create a local_manifests file by issuing the command `mkdir -p .repo/local_manifests/` then `gedit .repo/local_manifests/k2.xml`
inside this new document place the following lines
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/msm8960-common" name="CyanogenMod/android_device_htc_msm8960-common" />
<project path="device/htc/s4-common" name="CyanogenMod/android_device_htc_s4-common" />
<project path="device/htc/k2_cl" name="SimonSickle/android_device_htc_k2_cl" revision="cwm" />
<project path="vendor/htc/k2_cl" name="SimonSickle/android_vendor_htc_k2_cl" revision="jellybean" />
<project path="device/htc/k2_plc_cl" name="SimonSickle/android_device_htc_k2_plc_cl" revision="cwm" />
<project path="vendor/htc/k2_plc_cl" name="SimonSickle/android_vendor_htc_k2_plc_cl" revision="jellybean" />
<project path="device/htc/k2_ul" name="SimonSickle/android_device_htc_k2_ul" revision="cwm" />
<project path="vendor/htc/k2_ul" name="SimonSickle/android_vendor_htc_k2_ul" revision="jellybean" />
<project path="device/htc/k2_u" name="SimonSickle/android_device_htc_k2_u" revision="cwm" />
<project path="vendor/htc/k2_u" name="SimonSickle/android_vendor_htc_k2_u" revision="jellybean" />
<project path="kernel/htc/k2" name="SickleKernels/android_kernel_htc_k2" revision="htc_3.4" />
</manifest>
now run `repo sync` and wait for this to finish. It will take a long time
With any luck, you now have the source. Your computer should already be set up to build so just do the following commands
. build/envsetup.sh
now you will want to lunch the right device (see the download section as a guide)
lunch cm_k2_cl-userdebug
and finally the make command is as follows
make -j5 recoveryimage
at the end you will see a welcoming path to your new recovery. Flash it in fastboot or with dd and enjoy!
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Works great Simon! Thanks.
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Hi;
The recovery file is not there. Can you reload it?
Sorry Simon, recovery doesn't boot.
Neither the k2u nor the k2ul.
k2u -> boots constantly into android, not recovery.
k2ul -> hangs on splash screen.
bkcokota's cwm works totally fine, but it has the framework bug.
This bug fixed and we have a stable CWM. But i know, devs do not work on others build.
I am going to do twrp then. Once those are confirmed booting ill use the TWRP folder and remove anything non twrp from them
PS- The issue with his build is a lack of source (problem one), the partitions are different (two), the devices have different code names which messes with the flashing of source built roms (problem three) and its not ready for 4.3 (4)
Updated 9/21/13
Sent from my C525c using Tapatalk 4
All of the links are dead. Where else can I get info for the Boost c525c?

[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

[CM-12.1][UNOFFICIAL][D2533]Xperia C3 Temp ROM

Xperia C3 first custom rom base original Cyanogenmod 12.1
This is just Test version
this rom release. cause I get many logs and yours participation
working now
cellurar Networking
Wi-Fi
Ambient light sensor
Magnetometer
audio
not working now
camera(i find reason why rebroken)
gps(but maybe working base ip or router)
brightness control
Accelerometer
known bugs
turn off hotspt after not working wifi(reboot please)
change dpi on settings. if you get buggy or black screen(just reboot please)
I can release possible..
but we can flash that made for c3 recovery...
so first time must use fastboot...
XDA:DevDB Information
Xperia C3 Temp ROM, ROM for the Sony Xperia C
Contributors
wwwhana
Source Code: https://github.com/wwwhana/android_device_sony_wukong
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: build 151201
Beta Release Date: 2015-12-02
Created 2015-12-01
Last Updated 2015-12-07
Download Links
151201 build
media fire
Change logs
Change logs
[15/12/01]firts release
Need UNLOCK
if you not yet follow this guid
The responsibility of all problems for you.
Fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot, boot.img, system.img in same folder
Click to expand...
Click to collapse
Flashtool
select button icon like thunder
select fastboot
click select kernel to flash
select boot.img
click select system to flash
select system.img
you must install fastboot driver
Click to expand...
Click to collapse
if you participation develop Xperia C3 cm?
this is my local manifest
if you try add vendor blub and resulte share please
or try driver build and after result. please share
Code:
<manifest>
<default revision="refs/heads/cm-12.1" remote="github" sync-c="true" sync-j="4"/>
<remote name="sony" fetch="git://github.com/sonyxperiadev/" />
<project name="wwwhana/android_device_sony_wukong" path="device/sony/wukong"/>
<project name="wwwhana/android_device_sony_msm8226-common" path="device/sony/msm8226-common" />
<project name="wwwhana/android_kernel_sony_wukong" path="kernel/sony/wukong" revision="19.4.A.0.xxx" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm"/>
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/dash"/>
<project name="CyanogenMod/android_hardware_sony_thermanager/" path="hardware/sony/thermanager/"/>
<project path="hardware/qcom/camera" name="wwwhana/android_hardware_qcom_camera" groups="device" remote="github" />
<project path="vendor/sony/system/macaddrsetup" name="macaddrsetup" groups="device" remote="sony" revision="master" />
<project path="vendor/sony/system/timekeep" name="timekeep" groups="device" remote="sony" revision="master" />
</manifest>
Reserved
Reserved
Sensor info
almost sensor is not working
this is find our device sensor list
that help find drivee.
i try build dash but that is hard....
some sensor drive in dash code ...
Sensors (14)
BMA250 Accelerometer
Vendor BOSCH
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 0.139 mA
Delay 8333 μs
AK8963 Magnetometer
Vendor AKM
Range 4911.9995 μT
Resolution 0.14953613 μT
Power 5.0 mA
Delay 16666 μs
AK8963 Magnetometer Uncalibrated
Vendor AKM
Range 4911.9995 μT
Resolution 0.14953613 μT
Power 5.0 mA
Delay 16666 μs
Proximity Prx_ALS Sensor
Vendor ams AG
Range 5.0 cm
Resolution 5.0 cm
Power 12.675 mA
Delay On Trigger
Light Prx_ALS Sensor
Vendor ams AG
Range 10000.0 lx
Resolution 0.009994507 lx
Power 0.175 mA
Delay 66666 μs
Gravity
Vendor QTI
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 5.1389923 mA
Delay 16666 μs
Linear Acceleration
Vendor QTI
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 5.1389923 mA
Delay 16666 μs
Rotation Vector
Vendor QTI
Range 1.0
Resolution 5.9604645E-8
Power 5.1389923 mA
Delay 16666 μs
Step Detector
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
Step Counter
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
Significant Motion Detector
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
GeoMagnetic Rotation Vector
Vendor QTI
Range 1.0
Resolution 5.9604645E-8
Power 5.1389923 mA
Delay 16666 μs
Orientation
Vendor QTI
Range 360.0°
Resolution 0.1°
Power 5.1389923 mA
Delay 16666 μs
Tilt Detector
Vendor QTI
Range 1.0
Resolution 1.0
Power 0.13899231 mA
Delay On Trigger
Thanks, will flash this weekend.
wwwhana said:
Reserved
Click to expand...
Click to collapse
Hi, I can't seem to reboot into recovery. The phone shows the purple LED then reboots at the Sony text, then reboots again into the normal sequence. Installing XZDR recovery did not help either.
Edit: Could you repack this into a working flashable zip? That way maybe I can get the recovery to work, so reverting back to stock rom won't be so tedious.
Temporary screen brightness fix: Go to Display > Live Display > Colour calibration and set the Red, Green, Blue value at 35%. Any amount works fine as long as they are the same number.
More edit: Yup, not gonna touch until the recovery is confirmed to be working as I depend on it as a backdoor in case anything goes wrong. I lost recovery, using fastboot to get it back failed, now I'm reflashing again to stock.
recovery is later....
AutumQueen92 said:
Hi, I can't seem to reboot into recovery. The phone shows the purple LED then reboots at the Sony text, then reboots again into the normal sequence. Installing XZDR recovery did not help either.
Edit: Could you repack this into a working flashable zip? That way maybe I can get the recovery to work, so reverting back to stock rom won't be so tedious.
Temporary screen brightness fix: Go to Display > Live Display > Colour calibration and set the Red, Green, Blue value at 35%. Any amount works fine as long as they are the same number.
More edit: Yup, not gonna touch until the recovery is confirmed to be working as I depend on it as a backdoor in case anything goes wrong. I lost recovery, using fastboot to get it back failed, now I'm reflashing again to stock.
Click to expand...
Click to collapse
i'm sorry. The first goal is working all function about hardware....after support recovery.
and you say flashable zip... i will try after my This semester final exams that is next week.
so i can't do it now....
maybe possible next friday on KST
my focus is sensors
i hard working about find sensors source and build module
but that is not easy
not working sensor that
Vendor: QTI
or
BMA250
and last
i think that some differnece light sensor...
cause not working in light module on wukong
so that is not working front led and bright control....
Thank u
use my test rom
wwwhana said:
i'm sorry. The first goal is working all function about hardware....after support recovery.
and you say flashable zip... i will try after my This semester final exams that is next week.
so i can't do it now....
maybe possible next friday on KST
my focus is sensors
i hard working about find sensors source and build module
but that is not easy
not working sensor that
Vendor: QTI
or
BMA250
and last
i think that some differnece light sensor...
cause not working in light module on wukong
so that is not working front led and bright control....
Thank u
use my test rom
Click to expand...
Click to collapse
sure, take your time. I'll wait for recovery and use stock rom since I'm kinda paranoid about this stuff
Edit: Recovery is also needed to install gapps and xposed. no rush though >.>
Working: CAMERA
Click to expand...
Click to collapse
How did you manage that? We haven't got the source... Surely the libraries from the Sony ROM don't fully work with CM12.1?
Anyways, My builds from source are finally compiling without errors (so far...), so I'll post a flashable zip in my thread when they finish. I've included the qcom camera source, but I don't know if it will work yet, as it is still building... Keeping fingers crossed...
rebroken camera r-.-
while try another thing...
so camera is maybe not working
i release cause working when test..
but i try rollback but notworking;;;
i will fix after next week...
and i find some sensor and try but that not easy....
AK8963 is exist source
but have compile error;;
so that try fix next week
Testing...
Posting because the subscribed function seems bugged. Hope this resets it
@wwwhana, @Riccorbypro, @cezer kiran
I found something that works!
AutumQueen92 said:
@wwwhana, @Riccorbypro, @cezer kiran
I found something that works!
Click to expand...
Click to collapse
that is working??
i boot now that
wwwhana said:
that is working??
i boot now that
Click to expand...
Click to collapse
Yes it does. There's a build.prop file in there, replace it with the one from C3. Do not flash the t2fix.zip.
I've asked if the OP minds if I adapt this and post it on these forums, hope he says yes. Would be really nice to debloat this ROM and have xposed as well...
Sent via Carrier Pigeon
HEY BRO I AM CRAZILY
WAITING FOR THIS ROM PLEASE GIVE ME THE DATES WHEN
YOU WILL FINALLY RELEASE A STABLE ROM
MAKE IT SOON BRO
A SPECIAL THANKS TO YOU FROM ALL THE C3 USERS:good::good::good:
nihar34 said:
HEY BRO I AM CRAZILY
WAITING FOR THIS ROM PLEASE GIVE ME THE DATES WHEN
YOU WILL FINALLY RELEASE A STABLE ROM
MAKE IT SOON BRO
A SPECIAL THANKS TO YOU FROM ALL THE C3 USERS:good::good::good:
Click to expand...
Click to collapse
Project is abandoned.
AutumQueen92 said:
Project is abandoned.
Click to expand...
Click to collapse
HEY THERE AUTUMQUEEN WHY DID YOU ABANDONED THE PROJECT BRO
I FLASHED THE ROM ON MY XPERIA C3 AND THINGS ARE WORKING NICE
CAMERA, MOBILE DATA, AUDIO,WIFI, HOTSPOT ALL ARE WORKING
THE PROBLEM IS JUST WITH THE SENSORS AND THE BRIGHTNESS OF THE SCREEN
EXCEPT THAT EVERY THING JUST WORKS LIKE CHARM. :good::good::good:

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

Categories

Resources