Hi! I am trying to build Lineage OS for my Neuxus 5X, but about 10 minutes in, it gives me an error that says:
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
It has some other things as well, which I will post later, but that's the general message.
Can someone please help with this? Thanks
NateDev473 said:
Hi! I am trying to build Lineage OS for my Neuxus 5X, but about 10 minutes in, it gives me an error that says:
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
It has some other things as well, which I will post later, but that's the general message.
Can someone please help with this? Thanks
Click to expand...
Click to collapse
Post the full log or noone will help you...
Enviado desde mi Nexus 6P mediante Tapatalk
alexiuss said:
Post the full log or noone will help you...
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
OK, it's building again right now so once it gives the error I will post the log on pastebin.
EDIT: http://pastebin.com/Y9a6cKXY
The log doesn't go the full way to the beginning because my terminal cuts it.
NateDev473 said:
OK, it's building again right now so once it gives the error I will post the log on pastebin.
EDIT: http://pastebin.com/Y9a6cKXY
The log doesn't go the full way to the beginning because my terminal cuts it.
Click to expand...
Click to collapse
Are you using OpenJDK8?
Enviado desde mi Nexus 6P mediante Tapatalk
Yes, I am.
Hi, did you succeed in overcoming this issue? It drives me crazy. I just can't compile all, it is always stuck at cmsdk.
NateDev said:
Yes, I am.
Click to expand...
Click to collapse
Related
Hello guys,
I'm starting this new topic because I'm having problems trying to build AOSP image of KK from Sony's tutorial.
I've synced android's 4.4.4 tree succesfully (I guess because when I follow the tutorial, in this step: repo init -u https://android.googlesource.com/platform/manifest -b android-4.4.4_r2, I have an issue: please see my first two pictures attached) but when I try to git cherry-pick (Add necessary patches from the AOSP upstream branch) I get another error (please, see the next picture attached).
Can anybody help me to succesfully create the ISOs so I can flash it and have vanilla Android?
Thank you very much!!
git already show you error:
fatal: unable to auto-detect email address.
Click to expand...
Click to collapse
Try:
Code:
git config --global user.email "[email protected]"
git config --global user.name "Your.Name"
EDIT: In future: please translate git errors. Not everyone in here uses spanish
Did command repo sync finished successfully? It should work for a pretty long time because its long list of files to download...
Ups, sorry! I'll take a look and translate it into English the next time. I'm sorry!
I've managed to fix that bug changing the device's name. Now it detects my email adress.
The repo in sync succesfully. The problem I have right now is the "git cherry-pick" because it seems not to be working (the one that shows in the last picture I attached).
I hope I can get a fix soon. Thanks for answering!
Enviado desde mi D5103 mediante Tapatalk
Ok, so i've go through tutorial on sony developer webpage and i've built an images without errors - are you certain that nothing modified your files?
I can upload image files if you want to try, but for now its not ready for everyday work - speakers (probably mic too), camera and nfc is not working.
Pergert said:
Ok, so i've go through tutorial on sony developer webpage and i've built an images without errors - are you certain that nothing modified your files?
I can upload image files if you want to try, but for now its not ready for everyday work - speakers (probably mic too), camera and nfc is not working.
Click to expand...
Click to collapse
Well, I've seen how to fix what I did wrong so I'll try again later but if you're telling me that AOSP KK is not working fine, I'll dessist. I thought tha problems existed in LP version, not Kit Kat's...
Thanks for answering!
Enviado desde mi D5103 mediante Tapatalk
Cm 12 freexperia no boot
gbueno6 said:
Well, I've seen how to fix what I did wrong so I'll try again later but if you're telling me that AOSP KK is not working fine, I'll dessist. I thought tha problems existed in LP version, not Kit Kat's...
Thanks for answering!
Enviado desde mi D5103 mediante Tapatalk
Click to expand...
Click to collapse
U mean we can have pure android KitKat on T3
avayrocks said:
U mean we can have pure android KitKat on T3
Click to expand...
Click to collapse
What I mean is that we can have pure android KK in our T3 but it's not fully working yet.
I'll try to build it again but I'll not be stable according to Pergert.
Enviado desde mi D5103 mediante Tapatalk
gbueno6 said:
What I mean is that we can have pure android KK in our T3 but it's not fully working yet.
I'll try to build it again but I'll not be stable according to Pergert.
Enviado desde mi D5103 mediante Tapatalk
Click to expand...
Click to collapse
K try hard we are waiting for the pure stable KitKat ROM for T3
avayrocks said:
K try hard we are waiting for the pure stable KitKat ROM for T3
Click to expand...
Click to collapse
I don't have to work hard because I'm not a senior developer. I only followed the tutorial Sony gave us in their website to build the images.
I don't know HOW to FIX all the bugs it has. I'm sorry! Better ask other great developers we have here in xda!
Enviado desde mi D5103 mediante Tapatalk
gbueno6 said:
I don't have to work hard because I'm not a senior developer. I only followed the tutorial Sony gave us in their website to build the images.
I don't know HOW to FIX all the bugs it has. I'm sorry! Better ask other great developers we have here in xda!
Enviado desde mi D5103 mediante Tapatalk
Click to expand...
Click to collapse
I got that but someone (SENIOR DEVS) please make some custom ROMs or stock 4.4.4 ROM for T3
The Moto E4 has been released running Android 7.1 out of the box. Frustrating for probably most of us running 7.0, but this is a good indication that we will get the 7.1 update. Just thought it'd be an interesting tidbit for those who want 7.1.
Screenshot:
So?
Enviado desde mi potter mediante Tapatalk
abeloman said:
So?
Enviado desde mi potter mediante Tapatalk
Click to expand...
Click to collapse
It's a sign that our device may get 7.1.
abeloman said:
So?
Enviado desde mi potter mediante Tapatalk
Click to expand...
Click to collapse
Why comment if that's all you've got to say
Of course we will get 7.1+ the device is only a few months old... Just of matter of when....
JoRocker said:
Of course we will get 7.1+ the device is only a few months old... Just of matter of when....
Click to expand...
Click to collapse
Lenovo hasn't really been reliable with updates... It took over 6 months to get Nougat on the G4, I wouldn't put it past them to skip straight to 8.0. But this is a good sign... Hopefully I won't have to wipe my phone and go to the unofficial Lineage to get it.
In order to have the forum cleaner, I open this new thread. This ROM isn't made by me, this is the original post where the ROM comes from: http://bbs.nubia.cn/forum.php?mod=viewthread&tid=989561
DOWNLOADS:
Original download link here: https://share.weiyun.com/b35f985310ba4cf1f33166f66ef56e2b
Mirror (GDrive) for 20170728 build:
https://drive.google.com/file/d/0B39cOh_mAq3ddFRyUVk3OVJXTEU/view?usp=sharing
Mirror (MEGA) for 20170808 build:
https://mega.nz/#!MIAWUILa!RZLiufqyHDI86GwxhA8xf399LKYaE9-VdUxEbFFV3hk
Debloater: http://cloud.tapatalk.com/s/598b40110944a/removeapps5.8.4.zip
GApps: http://opengapps.org
You have to choose Platform: ARM64 and Android: 7.1, you can choose any variant, but I recommend pico.
INSTRUCTIONS:
1.- Download the ROM, GApps and Debloater.
2.- Advanced Wipes of System, Data, Cache and ART/Dalvik Cache.
3.- Flash the ROM, Debloater and GApps.
4.- Enjoy!
Note: to update is better to do a fresh install (wipes in instructions) to avoid problems...
SCREENSHOTS:
See attachments
THANKS to:
@rasimyagubov for 20170728 build mirror
@ndv92 for 20170808 build mirror
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
IronJacob said:
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
Click to expand...
Click to collapse
Now that I look, my bootloader is locked as well... I made a clean flash and I restored apps with Titanium with no problems.
Enviado desde mi A0001 mediante Tapatalk
arceoxis said:
Now that I look, my bootloader is locked as well... I made a clean flash and I restored apps with Titanium with no problems.
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
I was able to restore backup as well.
You flashed rom with locked bl?
IronJacob said:
I was able to restore backup as well.
You flashed rom with locked bl?
Click to expand...
Click to collapse
I don't know if it was locked when I flashed, but all is working without issues
Enviado desde mi A0001 mediante Tapatalk
Thanks. I'll try it ASAP.
I've no personal apps installed from now.
The phone is actually full stock (no time)
IronJacob said:
Good idea to open a new thread for RR.
I just tried to update from previous version, but after rom flash i got relocked bootloader and unable to boot system. Anyone faced this problem?
Click to expand...
Click to collapse
I wiped system and flash RR + Gapps. It worked.
ndv92 said:
I wiped system and flash RR + Gapps. It worked.
Click to expand...
Click to collapse
I'll try on next update. For now i made a data backup in twrpclean flash and restored data.
Thank you
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
talsoake said:
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
Click to expand...
Click to collapse
Read, the dev of the ROM isn't here, he's Chinese... What's wrong with ext4? ?
Enviado desde mi NX563J mediante Tapatalk
talsoake said:
Tried to install it on f2fs partition, but it cause in bootloop.
So my question is: Does RR support F2FS and if not could you add support in the next update?
Click to expand...
Click to collapse
I remember the kernel and recovery must support f2fs then f2fs works. I guess this kernel doesn't now. The developer is a Chinese and no one knows if he will read this thread.
Arceoxis - I am in exactly the same position. Now boots straight into fastboot. I tried re-unlocking the boatloader. Device state shows as being locked. TWRP still accessible so I have options.
I was running the previous RR and device was unlocked, rooted and running fine. Looks like something in the flash is causing the phone to be re-locked? For info I did also flash the updated debloat.
EDIT: Clearing system, Data etc solved the problem. I realise that the instructions are clear - but this doesn't usually apply when updating to the same ROM.
Bob
boboskins said:
Arceoxis - I am in exactly the same position. Now boots straight into fastboot. I tried re-unlocking the boatloader. Device state shows as being locked. TWRP still accessible so I have options.
I was running the previous RR and device was unlocked, rooted and running fine. Looks like something in the flash is causing the phone to be re-locked? For info I did also flash the updated debloat.
EDIT: Clearing system, Data etc solved the problem. I realise that the instructions are clear - but this doesn't usually apply when updating to the same ROM.
Bob
Click to expand...
Click to collapse
I always make a clean flash, when I update too, so I didn't have that problem. I will add this info to the OP, thanks!
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
I always make a clean flash, when I update too, so I didn't have that problem. I will add this info to the OP, thanks!
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
I got this problem, too.
it's best to do a backup before flash.
I installed it. I think that charging speed is slow Is the quick charge valid?
hero-no said:
I installed it. I think that charging speed is slow Is the quick charge valid?
Click to expand...
Click to collapse
I don't know, but my phone charges fast...
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
I don't know, but my phone charges fast...
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
It was displayed from 78% to 100%, 1 hour 50 minutes remaining. The charger and cable you are using are using the accessories.
hero-no said:
It was displayed from 78% to 100%, 1 hour 50 minutes remaining. The charger and cable you are using are using the accessories.
Click to expand...
Click to collapse
It charges fast with stock charger and cable or Aukey cable and Aukey charger QC3.0 and It chsrges slow with Aukey cable and Nillkin charger.
Enviado desde mi NX563J mediante Tapatalk
arceoxis said:
It charges fast with stock charger and cable or Aukey cable and Aukey charger QC3.0 and It chsrges slow with Aukey cable and Nillkin charger.
Enviado desde mi NX563J mediante Tapatalk
Click to expand...
Click to collapse
I used the charger and cable bundled at the time of purchase. Charging was quick when it was probably an original ROM.
---------- Post added at 03:49 PM ---------- Previous post was at 03:21 PM ----------
hero-no said:
I used the charger and cable bundled at the time of purchase. Charging was quick when it was probably an original ROM.
Click to expand...
Click to collapse
Charging quickly became faster after rebooting. I will see a little more. Thank you.
Hey guys, is there any possibility to add an EIS to a custom Rom? Just curious about.
This is a beta rom so as the name implies you may encounter various problems/bugs.
Fastboot (unlocked bootloader)(erases all your internal storage):
http://bigota.d.miui.com/8.3.1/scor....1_20180301.0000.00_8.0_global_7127f41234.tgz
Recovery (TWRP and unlocked bootloader)(full wipe highly recommended):
http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
The update has been suspended at the moment but download links are still working... Anyway you flash the packages at your own risk, I don't assume any responsibilities for any bricked or exploded devices! This is only for sharing purposes!
Thank I very much for sharing
Thank you!
Thank you! But download from this server is a pain... could you upload it to another site?
Enviado desde mi MI Note 2 mediante Tapatalk
Hmmm, the mentioned version is basing on nougat 7.0... would be interesting to see if it is really basing on oreo
Gesendet von meinem Mi Note 2 mit Tapatalk
strumbol said:
Thank you! But download from this server is a pain... could you upload it to another site?
Enviado desde mi MI Note 2 mediante Tapatalk
Click to expand...
Click to collapse
Sorry i can't, my connection is too slow
haarmatte said:
Hmmm, the mentioned version is basing on nougat 7.0... would be interesting to see if it is really basing on oreo
Gesendet von meinem Mi Note 2 mit Tapatalk
Click to expand...
Click to collapse
Those two versions posted here are based on Oreo.
Are you sure?
realjumy said:
Are you sure?
Click to expand...
Click to collapse
If you updated through OTA or you downloaded from the miui forum you will have the nougat one. There are two versions of the 8.3.2 build: one is nougat and the other (the one I posted) is oreo
alexmanu1 said:
Those two versions posted here are based on Oreo.
Click to expand...
Click to collapse
Spezia12 said:
If you updated through OTA or you downloaded from the miui forum you will have the nougat one. There are two versions of the 8.3.2 build: one is nougat and the other (the one I posted) is oreo
Click to expand...
Click to collapse
Any link to something we can use with locked bootloader?
realjumy said:
Any link to something we can use with locked bootloader?
Click to expand...
Click to collapse
Nothing at the moment
I was reading some comments of the OTA bricking phones... Are you having any problem so far?
---------- Post added at 08:07 PM ---------- Previous post was at 08:01 PM ----------
I wonder if we can use this: http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
I think it's the right file... But maybe right beta privileges are needed?
realjumy said:
I was reading some comments of the OTA bricking phones... Are you having any problem so far?
---------- Post added at 08:07 PM ---------- Previous post was at 08:01 PM ----------
I wonder if we can use this: http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
Click to expand...
Click to collapse
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
realjumy said:
I think it's the right file... But maybe right beta privileges are needed?
Click to expand...
Click to collapse
Very likely
Spezia12 said:
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
Click to expand...
Click to collapse
No risk, no fun... I used the option in the updater and it doesn't allow me to install it. Probably because I need special privileges... In any case, these are excellent news for custom ROMs
Edit: previous to the installation of the .ZIP it asks me to be connected to the internet... It can't be connected without being connected to the internet. So definitely they check if the user is allowed to install it.
Anyways. Anyone using the ROM can give some feedback, please?
Installed by twrp and running perfect ... for now no failure
routed with magisk 16.0
So installed last TWRP, wiped all data and storage for decryption, all went ok, inastalled oreo beta rom and magisc 16, during booting phone first get encrypted again and then rom boots up. Restarting back to TWRP is asking for password again to decrypt phone. So because of that I get back to nougat and TWRP 3.1.1.0 because that is only one that is not asking password. So please help and inlight me what I was doing wrong.
Spezia12 said:
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
Click to expand...
Click to collapse
A hard brick for a snapdragon device does not exist.
realjumy said:
No risk, no fun... I used the option in the updater and it doesn't allow me to install it. Probably because I need special privileges... In any case, these are excellent news for custom ROMs
Edit: previous to the installation of the .ZIP it asks me to be connected to the internet... It can't be connected without being connected to the internet. So definitely they check if the user is allowed to install it.
Click to expand...
Click to collapse
You have to be in the Beta Team to install those packages with the updater app. The method the Super Moderator recommended me is fastboot because it's an android version update. The ROM worked fine in the first day , no important bug that can prevent it to be a daily driver.
Please, I have a problem with my onclite, when I try to flash miuimix the recovery say: "This package is for onc devices, this is a onclite," and the updater end with ERROR 7. But the rom is right.
Can someone post a stock boot.img? Thank you
b1961786 said:
Please, I have a problem with my onclite, when I try to flash miuimix the recovery say: "This package is for onc devices, this is a onclite," and the updater end with ERROR 7. But the rom is right.
Can someone post a stock boot.img? Thank you
Click to expand...
Click to collapse
Try to wipe cache, art cache /dalvik, data/ system n make a format, reboot in recovery n flash miuimix if error persist tomorrow I'll which is the problem...let me know after do what I told u
Inviato dal mio MI PAD 4 utilizzando Tapatalk
In those days I'll publish a new release of miuimix...I'll work on it in those days...
For miuimix problem u told I flashed again yesterday without any problem, u resolved?
Inviato dal mio MIX 3 utilizzando Tapatalk
PeppeCNN said:
In those days I'll publish a new release of miuimix...I'll work on it in those days...
For miuimix problem u told I flashed again yesterday without any problem, u resolved?
Inviato dal mio MIX 3 utilizzando Tapatalk
Click to expand...
Click to collapse
yes, I resolved thank to your suggestions, thank you, I will wait for your new miuimix, thank you for your work and your answers
onclite
Hi,
I have exactly same problem with my HM 7.
I managed to get Pitchblack recovery working, copied the miuimix_ONCLITE to my phone. Started flashing and thats it.
Pls see the attached pics. And yes phone has been officially unlocked
Strangely enough if I check with "getvar all" the phone claims to be "onc" and not "onclite"
Purchased it in Shanghai direct from Xiaomi
Tks for any hint
Henning
PS on the pic you see the test result with a different rom. But result is same with miuimix......
homer276 said:
Hi,
I have exactly same problem with my HM 7.
I managed to get Pitchblack recovery working, copied the miuimix_ONCLITE to my phone. Started flashing and thats it.
Pls see the attached pics. And yes phone has been officially unlocked
Strangely enough if I check with "getvar all" the phone claims to be "onc" and not "onclite"
Purchased it in Shanghai direct from Xiaomi
Tks for any hint
Henning
PS on the pic you see the test result with a different rom. But result is same with miuimix......
Click to expand...
Click to collapse
Flash it in TWRP and you will be fine
H4nYcz said:
Flash it in TWRP and you will be fine
Click to expand...
Click to collapse
Tks, after several attemps I could convince the phone to believe that the ROM is really "ONCLITE" and not "ONC"
That phone was really stubborn ......
Case closed
homer276 said:
Tks, after several attemps I could convince the phone to believe that the ROM is really "ONCLITE" and not "ONC"
That phone was really stubborn ......
Case closed
Click to expand...
Click to collapse
Here xiaomi confused cards on table, redmi 7 if u make a getvar all in adb is onc, but call roms onclite. Onclite is redmi y 3 but calls roms onc... anyway i did a thread for last MiuiMiX
homer276 said:
Tks, after several attemps I could convince the phone to believe that the ROM is really "ONCLITE" and not "ONC"
That phone was really stubborn ......
Case closed
Click to expand...
Click to collapse
Yeah I was confused, because I was unable flash anything with Pitchblack recovery, only solution was use twrp every time. You're welcome
PeppeCNN said:
Here xiaomi confused cards on table, redmi 7 if u make a getvar all in adb is onc, but call roms onclite. Onclite is redmi y 3 but calls roms onc... anyway i did a thread for last MiuiMiX
Click to expand...
Click to collapse
Thank you