Database Users

Lineage OS (official nightly) installation problem

I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.

Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.

i am on zui 2.3.045

hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
i am on zui 2.3.045 tell me full installation process if possible

Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?

+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Can i flash in fastboot or install Lineage os recovery?

Mikuzukz1 said:
Can i flash in fastboot or install Lineage os recovery?
Click to expand...
Click to collapse
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.

+∆bhijith said:
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
Click to expand...
Click to collapse
it's showing error that way

Mikuzukz1 said:
it's showing error that way
Click to expand...
Click to collapse
Even now? Even after rebooting to recovery via ADB?

+∆bhijith said:
Even now? Even after rebooting to recovery via ADB?
Click to expand...
Click to collapse
I don't know how to boot via adb ijust wiped all partitions in twrp

got it working finally....installed it over cm13.0 and done

Mikuzukz1 said:
got it working finally....installed it over cm13.0 and done
Click to expand...
Click to collapse
Wonderful ! Good to go for any 7.x.x rom now...
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Because i faced same problems before and searched in XDA and that is the solution available right now.

Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
I think file is not completely downloaded...
Once same happened when I checked I chose wrong file wwhich was half downloaded.. Check it

i'm facing the same problem. i don't know how to use adb boot.
isn't there any other way.
also i checked the file was completely downloaded
and i'm on zui 2.5

I also have problem when flash nuclearom from cm13. I have some zuk devices but got problem with 2
First, it has bootloop
I have to flash China ROM then it works
I can flash CM 13
But up to 14 or 7.x will have bootloop again
Pls help

Unable to flash custom ROM (error executing updater binary in zip)

I am trying to install this ROM: https://forum.xda-developers.com/zuk-z1/development/rom-resurrection-remix-n-5-8-3-t3592452
I tried installing it through TWRP 3.0.2 but that was showing an error saying
'updater process ended with error 255'
I then switched to an unofficial TWRP (2.8.7.0) and now it shows this error:
'error executing updater binary in zip'
Does anyone know a solution?
I was trying a clean install so I completely wiped the stock ROM without taking a back up so I am kinda stuck.

Pranay08 said:
I am trying to install this ROM: https://forum.xda-developers.com/zuk-z1/development/rom-resurrection-remix-n-5-8-3-t3592452
I tried installing it through TWRP 3.0.2 but that was showing an error saying
'updater process ended with error 255'
I then switched to an unofficial TWRP (2.8.7.0) and now it shows this error:
'error executing updater binary in zip'
Does anyone know a solution?
I was trying a clean install so I completely wiped the stock ROM without taking a back up so I am kinda stuck.
Click to expand...
Click to collapse
Try rebooting back to recovery and retry installation of rom.
Or Please flash twrp 3.0.2 or 3.1.0... Then retry...
Check if enough storage space is available for installation of rom.
See if you have any other rom file on phone.. Install that and then see..
Plus it will give you a working phone for a while.. Also, you would be able to check if rom file is fine or it is corrupted or not fully downloaded.
---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------
Also google/ search in xda..
error 255 twrp.
You will get results about it.
Sent from my Zuk Z1 using XDA Labs
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Also see the screenshot attached

vikas966591 said:
Try rebooting back to recovery and retry installation of rom.
Or Please flash twrp 3.0.2 or 3.1.0... Then retry...
Check if enough storage space is available for installation of rom.
See if you have any other rom file on phone.. Install that and then see..
Plus it will give you a working phone for a while.. Also, you would be able to check if rom file is fine or it is corrupted or not fully downloaded.
---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------
Also google/ search in xda..
error 255 twrp.
You will get results about it.
Sent from my Zuk Z1 using XDA Labs
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Also see the screenshot attached
Click to expand...
Click to collapse
Sent from my Zuk Z1 using XDA Labs

Error 255
Same problem I am facing, I even tried that screenshot solution, but didnt work

irulegod said:
Same problem I am facing, I even tried that screenshot solution, but didnt work
Click to expand...
Click to collapse
Sorry but that's all that i could find...
Also.. See if there is permission issues on the phone..
Sent from my Zuk Z1 using XDA Labs

You will have to do this:
1. Open the rom file in your computer/laptop using winrar
2. go to META-INF > COM > GOOGLE > ANDROID > UPDATER-SCRIPT
3. Open this UPDATER-SCRIPT in notepad++ or any other text editor software
4. You will find a line starting with "assert", just remove this whole statement (starting from "assert" and ending with brackets & semi colon just like this => ");")
*. After removing above statement, Nuclea Rom's updater-script file looks like this:
ui_print("Target: ZUK/ham/Z1:7.1.2/N2G47O/3bee626032:userdebug/test-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
..............................................(& so on)
You will be able to install this rom now

Error on rooting
Hi there vinay here,
Am unable to root any ROM,
Its mentioning unknown commend (log),,,
Before doing it i have cleaned all cache and storage ,,
But Nothing working.....
Please help guys,,

[Help] Anyone have boot.img or NotoColorEmoji.ttf file for nougat x Style?

Basically i rooted systemlesly and changed my emojis to the IOS ones with an app on the playstore. Then i reset my phone because of reasons. Now i want to remove my root and get magisk and xposed. To do this i need to remove my SU root and flash magisk, however magisk will only flash with an unmodified system.
This is where my problem occurs. When i reset my phone my original emojis were removed, leaving me with the IOS emojis. I made no backup of my original emojis. When i click restore emojis on the app no emojis change, and when i install the nougat emojis from the app my system is still considered "modified"
Therefore, im asking if anyone has a boot.img of my Moto x style, as i think flashing that would fix it. I also think that if anyone has the original NotoColorEmoji.ttf file, i can replace it with mine and it could fix it aswell. If anyone has any of these 2 files it would be much appreciated ??

Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX

dzidexx said:
Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX
Click to expand...
Click to collapse
Trying to restore boot from SuperSU resulted in it saying uninstallation failed. I also tried looking through the general section and none that ive found have a boot.img file i can just flash.

Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX

dzidexx said:
Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX
Click to expand...
Click to collapse
Funny indeed ? That image doesn't have a -3 at the end, and mine does, so idk if it will work and i wanna be sure

For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.

dzidexx said:
For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.
Click to expand...
Click to collapse
Ive already uninstalled supersu, i just said no when it asked to restore ti stock boot because when i chose yes it said failed. The only backups i have are of marshmallow 18-8 and nougat, but with the changed emojis (pretty stupid on my part)
I also have no idea what u mean by boot(kernel)

Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.

dzidexx said:
Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.
Click to expand...
Click to collapse
Lol its fine. Well eventually i managed to install magisk. I downloaded the boot/sys backup from https://forum.xda-developers.com/mo...gust-2017-security-patch-nph25-t3673373/page3 and restored it via twrp, then flashed magisk and it worked

lineage os pb2-650y

Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.

https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site

dlsega said:
Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.
Click to expand...
Click to collapse
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code

sushil888 said:
https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site
Click to expand...
Click to collapse
i tried, but avast shows the site as a security risk. I supose you found something for the pb2-650M?

reggiexp said:
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code
Click to expand...
Click to collapse
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file

Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??

sushil888 said:
Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??
Click to expand...
Click to collapse
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/

reggiexp said:
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
Click to expand...
Click to collapse
They're pretty much the same, the difference is on the LTE bands, the M has works with more I think. (besides the retail region).
I had a similiar problem, and the issue was that the bootloader wasn't being unlocked flashing the commands. It turns out that the thing keeping the bootloader from unlocking was that little OEM UNLOCK check in the DEVELOPER OPTIONS. After I checked that one, tried again, and this time it worked, I first noticed it because the phone started wiping to a factory reset automatically. After that I just put it into fastboot mode, flashed TWRP. And done.
I don't know if this is the same issue you're having. But for me it was a little frustrating trying and trying without success, until I noticed that little detail and that was it.
At the moment I have it rooted with xposed working just fine. The only issue (don't know if it's only me), is when recording a video using 3rd party apps like instagram or snapchat, the audio is garbage, like some noise cancellation going wrong.

im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.

reggiexp said:
im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.
Click to expand...
Click to collapse
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk

frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
didn't even try.
it's my majn phone still so not really wanna mess with it. still to lazy to flash RR on my redmi note 3

frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
still not switch phone? any one got any updates on the roms??? like this forum is dead.././

Custom rom for lenovo pb2-650m
I request the developers to provide custom rom for lenovo pb2-650m.

subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
it are the same phones anyway i just cant figur out the unlock and twrp flash

subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
Were you able to find any custom rom for lenovo pb2-650m?

Error 7, only on slot B? Help

So i was flashing the stock rom to both A/B before flashing a custom rom, and successfully flashed oxygen then twrp installer to slot A, rebooted to recovery, but then when I tried to do it to slot B, i get this error 7 message. Ive looked around and can't seem to find a solution. Any help is greatly appreciated

What versions? What ROM? International 6T or TMobile?
Error 7 generally means the ROM is not compatible with that device. If you are sure it is you can remove this check if you know what you are doing. However this is generally not recommended.

Yes

What version of TWRP? Error 7 means most of the time that TWRP is to old to deal with the ROM flash script. Flash latest twrp 3.3.1-31 installer again and reboot to recovery
---------- Post added at 08:06 AM ---------- Previous post was at 08:06 AM ----------
neopunk1 said:
Yes
Click to expand...
Click to collapse
This is quite an answer, congrats

My bad Was trying to open a new thread re Goofgle Duo screen freeze but could not post so I just picked a random thread and typed yes to see if it is the Xda app that was the problem Didnt take long at all lol