Related
HI. Please help me! I wasn't able to modify an article on the WIKI (wiki.xda-developers.com).
All the time I press the "Edit" Button, FireFox give me the option to download the php file :?: :?: :shock: WEIRD
The address I was modifying was:
http://wiki.xda-developers.com/index.php?pagename=List of HimaUpgradeUt.exe Error Code
After trying it several times, I could get inside and edit the page, then I saved it, and now is BLANK!!!!
HEEEEELLPPPP
The contets of the page at the time of my edit were:
--------------------------
ERROR 100: MODEL ID ERROR
Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like MAGICIAN, BlueAngel or Alpine
Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM
ERROR 101: CONNECTION ERROR
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
ERROR 103: ROM IMAGE FILE NOT FOUND
ERROR 104: CANNOT OPEN ROM IMAGE FILE
ERROR 105: OPEN PORT FAILURE
ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE
WARNING 111: POWER ADAPTER NOT PLUGGED IN
ERROR 112: CE ROM UPDATE ERROR
ERROR 113: EXTENDED ROM UPDATE ERROR
ERROR 114: RADIO ROM UPDATE ERROR
ERROR 115: INVALID VERSION OF ACTIVESYNC
ERROR:116 GENERAL ERROR
ERROR 117: INVALID MODEL ID
ERROR 120: COUNTRY ID ERROR
ERROR 121: LANGUAGE ID ERROR
ERROR 122: EXTENDED IMAGE FILE CHECKSUM ERROR
ERROR 123: RADIO IMAGE FILE CHECKSUM ERROR
ERROR 130: CREATE CE ROM IMAGE ERROR
ERROR 131: ALLOCATE MEMORY ERROR
ERROR 132: WRITE DATA ERROR
ERROR 133: COMMUNICATION ERROR
ERROR 134: READ CE ROM IMAGE ERROR
ERROR 135: COMMUNICATION ERROR
ERROR 136: COMMUNICATION INTERRUPT
ERROR 137: COMMUNICATION ERROR
ERROR 150: ROM UPGRADE UTILITY ERROR
ERROR 200: WRITE EXTENDED ROM FAIL
Error 201: GET DEVICE DATA ERROR
This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.
Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.
Error 202: READ IMAGE ERROR
ERROR 210: CREATE EXTENDED ROM IMAGE ERROR
ERROR 211: ALLOCATE MEMORY ERROR
ERROR 212: WRITE DATA ERROR
ERROR 213: COMMUNICATION ERROR
ERROR 214: READ EXTENDED ROM IMAGE ERROR
ERROR 215 COMMUNICATION ERROR
ERROR 216: COMMUNICATION INTERRUPT
ERROR 310: CREATE RADIO ROM IMAGE ERROR
ERROR 311: ALLOCATE MEMORY ERROR
ERROR 312: WRITE DATA ERROR
ERROR 313: COMMUNICATION ERROR
ERROR 314: READ RADIO ROM IMAGE ERROR
ERROR 315: COMMUNICATION ERROR
ERROR 316: COMMUNICATION INTERRUPT
ERROR 317: COMMUNICATION ERROR
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Yup, I thought it was a temporary problem. Moreover, I'm having the same strange behaviour in some wiki links.
For instance:
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
It is the first link on this page:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Radio
Thanks for your answer. I'll try later........
oltp said:
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Click to expand...
Click to collapse
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Luckily, I think you can allways get an older version of the page.
Cheers
oltp said:
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Click to expand...
Click to collapse
arieltools said:
Luckily, I think you can allways get an older version of the page.
Click to expand...
Click to collapse
Ok learned something again, I didn't know that.
Just posting this as requested in another thread, It's an Android 2.0 ROM for Sapphire.
This is an update from the original, now a complete working ROM.
Known issues
Camera not working - This isn't yet available to the AOSP, Until it is, it's unlikely we'll have it.
Accelerometer
Gallery
No port for 32A - Patch up - Working on this
Everything else should be working - Please report issues, comments, etc. as a reply to this post. (and add any issues here: http://code.google.com/p/android-sapphire/issues/list)
As the rom is custom built, it is rootable (ro.secure=0) but does not come rooted (with "su") - This may change in the future.
This ROM contains your standard Google stuff you expect to see, and the new Facebook application ripped from the Motorola Droid.
This ROM has been tested on the HTC Magic & Google ION handsets (32B) - We plan to support 32A very soon.
We accept no responsibility for any loss, including bricked phones. Please backup your content before trying to update.
Finally, The download location:
http://code.google.com/p/android-sapphire/downloads/list
At present, This ROM is considered stable and is available for general use
Current Build: jd02
Last update: 25/11/09
Will give it a shot
Does this have the Navigation software?
Edit: Cant download it
"This file can only be downloaded by becoming a Premium member
There are no more download slots available for free users right now. If you don't want to become a premium member, you might want to try again later."
Mirror please
This looks amazing!
I own a 32A, so I'm not flashing right now, I'm waiting for one of our gurus to provide a safe way to do so (so to avoid high risk of having a cool black brick instead of a phone)..
Anyway, I'll test this as soon as its reasonably safe to do so..
In the meanwhile, great work, please keep on working on this!
WebghostDK said:
Does this have the Navigation software?
Click to expand...
Click to collapse
Not at present, No - Does not mean it won't forever - Although I don't really want to add to much to the code, I might look at install scripts etc.
At present it's only exactly what you will find if you were to compile the code yourself.
OzJD said:
Just posting this as requested in another thread, It's the official Android 2.0 ROM for Sapphire.
I may post updates later as this is directly out of the AOSP repository
Known issues
1) Bluetooth not working.
Please report issues, comments, etc, here.
As the rom is custom built, it is rootable but does not come rooted.
Try "su" in the ADB shell.
This is a vanilla ROM, and does not contain anything you do not see in the repository (except for possible bugfixes).
Tested on HTC Magic/Google ION (32B) - Is there a reason this wouldn't work on 32A? - Please report failures/success here.
I will take no responsibility for your actions/bricked phones.
Why no update.zip?
Because that's not how I roll. You can use the fastboot utility to install this rom, just goto the directory containing the img's and type "fastboot flashall".
Note: You may require certain software on your phone to install this.
Finally, The download location: http://rapidshare.com/files/309784805/Official_Sapphire_AOSP_by_JD.zip [Mirrors Wanted - PM if you can mirror]
If there is a lot of community response/feedback (and use of these images), I may consider doing frequent updates with the newest Android versions - To keep everyone up to date.
Click to expand...
Click to collapse
I am looking into the build process myself to build the 2.0 for the 32b, I would like to have a automatic daily build if possible. maybe you could try that?
Will test Android 2.0. I own a 32a. I know how to get back if it doesn't. Will keep you guys posted.
opcode1300 said:
I am looking into the build process myself to build the 2.0 for the 32b, I would like to have a automatic daily build if possible. maybe you could try that?
Click to expand...
Click to collapse
I could do something like this (I was thinking of it earlier), with these issues:
The source code doesn't change daily - Is it worth it? (easily overcome)
It may become common for it to not work due to bugs in source code
If I were to, an automatic update feature might be nice!
I need reliable mirrors :-(
It's definately on the cards though - The repo client does all the merging, so I don't see why I can't batch it.
outcorpse said:
Will test Android 2.0. I own a 32a. I know how to get back if it doesn't. Will keep you guys posted.
Click to expand...
Click to collapse
Look forward to hearing your results!
Well Dun!
Hope to have mine compiled soon... I went out... left it going... and came back and its still goin, no errors! shocked!
Will try the old nav thing after i`ve done the initial compiling... hope gps works ok
i can't update i get the error:
E:No Signature (6 Files)
i'm on a 32b!!
Added a few mirrors (see first post), you shouldn't have any issues getting it now
niceeee..
few questions: htc sense ui? FLASH PLAYER??!?!?!?!?
i might wait to hear from outcorpse before i try this.
edding3k said:
i can't update i get the error:
E:No Signature (6 Files)
i'm on a 32b!!
Click to expand...
Click to collapse
I thought this might happen (thats why I added this line):
OzJD said:
Note: You may require certain software on your phone to install this.
Click to expand...
Click to collapse
I think you will need an engineering SPL to allow unsigned images to be used - Just like the ADP2 (Google ION), Please see here: http://forum.xda-developers.com/showthread.php?t=529019
Side note: I'm using 1.33.2005
Please let me know how you go
delete me... wrong forum!
~removed: [quotes deleted text]
Any idea what the problem could be with bluetooth? Do we just need the proprietary drivers for 32B from HTC or is this not a driver problem?
I'm creating my own.
I'll try yours.
Good....
i have 2010 spl i'm on 32a board..still confuse on how to flash this rom..
so i must enter fastboot mode right? then using adb i just do fastboot flashall?
can you give me step by step how to do this?
another question does camera work ? and what about google service?
thanks..
Firstly I recommend a full backup, If you're unsure about how to do this you probably shouldn't be flashing ROMs yet.
%FOLDER% refers to any folder of your choice.
Download the file in the original post, and extract to %FOLDER%
Download the fastboot binary for your operating system from http://developer.htc.com/google-io-device.html to to %FOLDER%
Boot your phone into "fastboot" mode
Open a terminal window (command prompt) and change directory to %FOLDER%
type: "fastboot flashall" (without the quotes)
Hopefully you should see something like this:
Code:
< waiting for device >
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: HT96WMG01288
--------------------------------------------
checking product... OKAY
sending 'boot' (1838 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2088 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (62895 KB)... OKAY
writing 'system'... OKAY
rebooting...
OzJD said:
Firstly I recommend a full backup, If you're unsure about how to do this you probably shouldn't be flashing ROMs yet.
%FOLDER% refers to any folder of your choice.
Download the file in the original post, and extract to %FOLDER%
Download the fastboot binary for your operating system from http://developer.htc.com/google-io-device.html to to %FOLDER%
Boot your phone into "fastboot" mode
Open a terminal window (command prompt) and change directory to %FOLDER%
type: "fastboot flashall" (without the quotes)
Click to expand...
Click to collapse
oke..thanks..doing nandroid backup..will report to you asap..
i'm very curious, does cam work? google service??
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lp gapps)
XDA:DevDB Information
CyanogenMod 12.0 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-03-02
Last Updated 2015-03-02
Reserved
error installing
cwm error log
Code:
-- Installing: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Finding update package...
I:Update location: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Opening update package...
Installing update...
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/systemabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
erasing 627200 blocks
blkdiscard failed: Invalid argument
writing 118679 blocks of new data
lseek64 failed: Invalid argument
E:Error in /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
(Status 1)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Cannot load volume /misc.
I:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host/mmc1
runoverheads said:
cwm error log
Code:
-- Installing: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Finding update package...
I:Update location: /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
Opening update package...
Installing update...
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/systemabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
erasing 627200 blocks
blkdiscard failed: Invalid argument
writing 118679 blocks of new data
lseek64 failed: Invalid argument
E:Error in /storage/sdcard1/cm-12-20150302-UNOFFICIAL-mondrianlte.zip
(Status 1)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Cannot load volume /misc.
I:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host/mmc1
Click to expand...
Click to collapse
Try again with tomorow's nightly build. I missed a commit to mondrianwifi which fixes the ability to flash the build on EUR devices which have a smaller /system/ partition. I just pushed that change and it will be picked up in tomorrow's build. If that doesn't fix it, let me know.
YESSSS!!!!! Very thanks, you are the number one
---------- Post added at 07:11 AM ---------- Previous post was at 06:18 AM ----------
"Error: unable mount /system" during the flash via TWRP
No SIM
the new build works but does not recognize the sim
adrenalynik said:
the new build works but does not recognize the sim
Click to expand...
Click to collapse
Try removing this line from /system/build.prop:
persist.radio.apm_sim_not_pwdn=1
crpalmer said:
Try removing this line from /system/build.prop:
persist.radio.apm_sim_not_pwdn=1
Click to expand...
Click to collapse
Great! Work very well, but the apn settings are missing. The " Cellular Network" in "Setting" is not visible.
adrenalynik said:
Great! Work very well, but the apn settings are missing. The " Cellular Network" in "Setting" is not visible.
Click to expand...
Click to collapse
I can't believe I never noticed that was missing... Doh!
You can either wait for tomorrow's build or add this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This is the standard set of telephony features for a GSM phone. -->
<permissions>
<feature name="android.hardware.telephony" />
<feature name="android.hardware.telephony.gsm" />
</permissions>
in the file:
Code:
/system/etc/permissions/android.hardware.telephony.gsm.xml
.
the file does not exist, I have create it and the menu is appeared.
You are the best!
Dear crpalmer,
short report from germany:
Having a german SM-T325 with t-mobile sim, running your CM11
Backup of apps with titanium backup
Factory reset plus formatted /system with twrp 2.8.4.0
Installed image 20150303 plus pa-gapps plus SuperSU
Rebooted
Language selector did not detect the german sim
Initial setup without any topic
Restored apps with titanium
Applied the mods from post #7 and #9
Rebooted
Everything fine: Calling, texting and ussd codes are working.
"Mobile Networks" available under settings.
This looks very promising!
Thanks a lot!
Stefan
i purchased a couple of days ago a 2nd hand set, 2 days which were enough to get me pissed bout samsung os crap
So I installed this and I can finally breathe. I can't be very accurate but it seems to me that it depletes battery a bit too fast when "idling" so I just got wakelock detector installed and will monitor, meanwhile someone more familiar with the device than me can confirm this CM12 is indeed not a batteryguzzler and it's just mine the exception ?
PS: Thanks to crpalmer for the beautiful rom, i have yet to insert the sim so I wouldnt have noticed the error posted above. Works great here and supersmooth.
Thx @crpalmer - great job with this first CM12 port, so far all works without any hickups and the 2 little changes to enable APN worked flawlessly.
Thumbs up
The setting "Cellular network" continues to disappear and if I set the camera resolution to 6mpx, the image is distorted.
wonderful rom many thanks for the lollipop flavor update so far so good you rock!!
adrenalynik said:
The setting "Cellular network" continues to disappear and if I set the camera resolution to 6mpx, the image is distorted.
Click to expand...
Click to collapse
I had to give all wipes with the new nightly, i try a dirty update and network didnt work
now everything is perfect
Anyone having WiFi issues?
I can connect fine to my virgin router 5ghz but can't connect to any of my Cisco WAP devices on 5 or 2.4 GHz frequencies
Was a fresh wipe and install and have tried the 4 different versions posted
Everything works fine here! Thanks crpalmer for the great work!!
Two questions:
- anyone noticed some little lags browsing the launcher pages or opening apps?
- do you use any tweak to hide root in certain apps?
Sent from my SM-T325 using XDA Free mobile app
Thanks für that great ROM!!!! I sent you a donation via paypal.
I tried latest version aka cm120703 but there was 1 big problem. Cyanogenmod setting screen went fine to point where it asks for cm account. No matter if i skip it or sign in ...i'm directed to begining where to select language, set wlan and then again cm account... Here we go again to select language and so on. I tried reboot and other stuff but all i got was cycle as previously mentioned. I'll try 0603 version next.
Edit: 0603-version installed nicely. No problems.
'm trying to build AOSP for a supported device (sony Xperia z5) (aosp_mips64-eng) I follow the instruction here: https://forum.xda-developers.com/t/...sp-pie-custom-rom-for-xperia-devices.3921641/ After download the source, Initializing device type for ROM building. I Encounter an error while trying to build the custom ROM:
I there anything i could do? Have I done something wrong? I'm pretty sure i did the previous steps correctly.
============================================
ninja: no work to do.
ninja: no work to do.
No need to regenerate ninja file
No need to regenerate ninja file
ninja: error: 'device/generic/common/nfc/libnfc-nci.conf', needed by 'out/target/product/generic/system/etc/libnfc-nci.conf', missing and no known rule to make it
10:29:40 ninja failed with: exit status 1
build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
helloguys2489574 said:
build AOSP for a supported device (sony Xperia z5) (aosp_mips64-eng)
Click to expand...
Click to collapse
You have to build for your device, not for a mips64 device as you can read in your mentioned instruction:
Code:
source build/envsetup.sh && lunch aosp_[device_model]-userdebug
Please take a closer look into the numerous tutorials available at the internet.
Please don't ask for further assistance if you don't know exactly what you're doing!
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
david3709 said:
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
Click to expand...
Click to collapse
What software tools are you using to build your ROM?
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
david3709 said:
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
Click to expand...
Click to collapse
david3709 said:
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
Click to expand...
Click to collapse
Using newer ROMs on older devices is going to cause lag, that is normal. The problem is not the ROM, the problem is your hardware wasn't designed to use newer, more demanding software.
yes, you are right, that is why i want to try android PIE, the reason for building AOSiP Pie is i want to do more practice, after more try, i can really build my own custom rom, right now what i only can do now is to rebuild some custom rom.