Develop Bugs

[DEV][WIP][ROM] CM10.2 Development thread - CALLING ALL DEVELOPERS

THIS ISN'T A PUBLIC ROM RELEASE. THIS IS FOR DEVELOPMENT ONLY. THE ROM DOES NOT BOOT. FOR MORE INFO READ THE ENTIRE POST
I've been working on bringing our device onto par with a build of Android 4.3. I've set up a GitHub organization just for our device and it has everything we need to build for the device. Now I've been somewhat quiet with what I've been doing lately and I really don't have time to list everything I've done. @bradthomas127 and I have been communicating back and forth about building. I'd say he's done just about as much work as I've done trying to get 4.3 building. Well now, after some tips from him, I've got it building. It's using, in my opinion, the best up-to-date trees there are for our hardware. I am opening this project up to anyone that can help get it BOOTING. I don't need testers as right now I feel like I myself am the best tester for now because getting adb working on a device that sticks at a blank scree is a pain in the a**. So PLEASE I encourage anyone that knows how to maintain a GitHub and can compile and do a little coding to try to help us. The more people we can get, the faster and better we can get 4.3 actually running on our device.
Here is the GitHub:
https://github.com/Primo-Dev
If you feel you are capable of helping us dev this please PM me and I may add you to the GitHub so you can contribute.
Here is the latest build:
http://d-h.st/JSo
Logcat can be downloaded here:
http://d-h.st/SYz
Now, some basic rules for this forum:
1. DON'T ASK FOR ETA OR UPDATES - This kind of stuff is hard and takes time
2. Don't ask to test - I'll open this up for testing if we ever get it to boot
3. To all other people who aren't devs: Don't post here as this is for development only. I've made this thread in hopes of finding more devs to try to help with this, not open this up as a public ROM.
What needs attention:
I'll post bits and pieces of logcat here that shows things that need to be worked on
Code:
I/auditd ( 99): Starting up
E/auditd ( 99): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 99): Exiting
W/dalvikvm( 161): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument

I did not even notice this till you posted the logcat, libgenlock is not even building.
Code:
E/libEGL ( 1327): load_driver(/system/lib/egl/libEGL_adreno200.so): dlopen failed: could not load library "libgenlock.so" needed by "libEGL_adreno200.so"; caused by library "libgenlock.so" not found

Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.

robaho said:
Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.
Click to expand...
Click to collapse
That's what I've been thinking. All the devices that have been updated to cm10.2 have SELinux. Only problem is I'm not much of a kernel dev, but I can see what I can do. Also, if you take the main hardware libs from RhythmicRom and put them in cm10.2 you can get to the bootanimation.
Sent from my HTC One V using xda app-developers app

I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-

bradthomas127 said:
I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-
Click to expand...
Click to collapse
I'll logcat. I'll also post instructions on how I logcat on 4.2+.
Sent from my HTC One V using xda app-developers app

Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app

reV17 said:
Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks I'll do some research on github later. It has almost the same specs so it will be useful.
BTW: To anyone waiting for logcat instructions I'm trying to find a simplest way to do it with the little time I have between work and football, and school coming up.

Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip

bradthomas127 said:
Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip
Click to expand...
Click to collapse
Hey man I'll post how to when I get home
Sent from my C525c using Tapatalk 4

You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Sent from my One V using xda app-developers app

Lucky CDMA people with half working 4.3 o-o

robaho said:
You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Click to expand...
Click to collapse
I added ro.adb.secure=0 to the default.prop a couple days ago making the ramdisk/default.prop look like this now.
Code:
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
I've also tried moving adbkey.pub to data/misc/adb/pub_keys in TWRP but it gets erased as soon as i boot.

Is the USB driver working, that is, can you.see a USB device using your system devices view - varies by OS
Sent from my One V using xda app-developers app

This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.

awidawad said:
This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.
Click to expand...
Click to collapse
Not working for me, messed with it a couple times.

bradthomas127 said:
Not working for me, messed with it a couple times.
Click to expand...
Click to collapse
Strange... I've used that method multiple times in ubuntu.
Sent from my C525c using Tapatalk 4

awidawad said:
Strange... I've used that method multiple times in ubuntu.
Click to expand...
Click to collapse
Getting boot now, just boot loops every min.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:highfive:

bradthomas127 said:
Getting boot now, just boot loops every min.
:highfive:
Click to expand...
Click to collapse
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app

robaho said:
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Do you mean this one? https://github.com/bradthomas127/an...mmit/9af6efa20ece323155a853ff508563a87670e2f0
Rukin added it 4 months ago.
You did just open my eyes though, i thought i commited the SELinux stuff but just noticed i didn't on this kernel, maybe why i am having reboots and SD card is not mounting (reason for no screen shot). Thanks :good:

[ROM][ALPHA][WIP][Jul/24] - Asteroid OS \\ ( Non-Android Wear )

Asteroid OS​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction and Warning:
YouTube Video: https://www.youtube.com/watch?v=b_GJiQYTAIk
Rom Alpha 7/24/2017
Downloads:
Official prebuilt Asteroid OS image : https://release.asteroidos.org/nightlies/sturgeon/
Instructions:
1. Make sure you have an ADB installation (Minimal adb and fastboot should do) and your watches' bootloader is unlocked and debugging is enabled from the settings.
2. Download the two files in the download section and place them in the same folder and connect the watch to the computer
3. Open up the shell or command prompt (cmd) and navigate to that folder
4. Issue these commands:
Code:
adb push asteroid-image-sturgeon.ext4 /sdcard/linux/rootfs.ext4
adb reboot bootloader
fastboot boot zImage-dtb-sturgeon.fastboot
5. The watch will reboot into Asteroid OS. Every time you want to boot into asteroid you have to issue the last two commands or else you will boot into android wear normally.
6. The Bluetooth synchronization app for Android is named AsteroidOSSync.apk. Be careful that dory is the only port with Bluetooth capabilities and this app will be of no use with other watches yet.
Download : AsteroidOSSync.apk
Removal Instructions:
Just open up shell or command prompt (cmd), connect the watch to the computer and issue this command:
Code:
adb shell rm /sdcard/linux/rootfs.ext4
Credits:
kido - Creator of the OS
Bencord0 - sturgeon port
Everyone on the #asteroid IRC
Links:
Webpage: asteroidos.org
Twitter: @asteroidOS
IRC: #asteroid

Can this interact with android at all? Like texts/notifications, etc?

phishfi said:
Can this interact with android at all? Like texts/notifications, etc?
Click to expand...
Click to collapse
The Bluetooth synchronization app for Android is named AsteroidOSSync for Android only
AsteroidOSSync.apk

CadBuRy.VN said:
The Bluetooth synchronization app for Android is named AsteroidOSSync for Android only
AsteroidOSSync.apk
Click to expand...
Click to collapse
Nice. I checked the website, too, but it doesn't have an actual answer. What can asteroid do? I see the apps that are available, but does the calendar get events from my gCalendar? Does it sync messages and contacts? I'll probably try this out tomorrow if I have time anyways, I just want to know if it's worth jumping into or if it's a heavily hamstrung OS for folks who are used to AW.

what does it look like in a rounded face?

Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.

phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
i got the same problem here.

phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
same here

phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
flo071 said:
i got the same problem here.
Click to expand...
Click to collapse
CVLover said:
same here
Click to expand...
Click to collapse
Dont want to sound rude (I really just wanna help)
Are you sure you downloaded both files? 509MB ext4 and 9MB fastboot?
Are both files in the same directory where you run your adb/fastboot commands?
Maybe we also need some permissions. I'm gonna check it later...
Also I will create a script (either shell or tasker script [maybe even an apk]) to easily boot into astroid os.
Both would be possible: on phone or on watch...

BIade said:
Dont want to sound rude (I really just wanna help)
Are you sure you downloaded both files? 509MB ext4 and 9MB fastboot?
Are both files in the same directory where you run your adb/fastboot commands?
Maybe we also need some permissions. I'm gonna check it later...
Also I will create a script (either shell or tasker script [maybe even an apk]) to easily boot into astroid os.
Both would be possible: on phone or on watch...
Click to expand...
Click to collapse
thank you.
and yes i did all the things.
is it possible that asteroid os needs an older version of the bootloader? maybe one from the older android wears.
btw an app for booting into asteroid os would be really nice.

flo071 said:
thank you.
and yes i did all the things.
is it possible that asteroid os needs an older version of the bootloader? maybe one from the older android wears.
btw an app for booting into asteroid os would be really nice.
Click to expand...
Click to collapse
that is a really good point. I guess you were also on aw2.0-official-rooted (not dev-pre-custom-rom)
EDIT:
PREFERRED_PROVIDER_virtual/android-headers = "android"
PREFERRED_PROVIDER_virtual/android-system-image = "android"
PREFERRED_VERSION_android = "marshmallow"
PREFERRED_PROVIDER_virtual/kernel = "linux-sturgeon"
PREFERRED_VERSION_linux = "3.10+marshmallow"
Click to expand...
Click to collapse
hmmmm.....

BIade said:
that is a really good point. I guess you were also on aw2.0-official-rooted (not dev-pre-custom-rom)
Edit incoming.. (just testing)
Click to expand...
Click to collapse
i am on last dev preview unrooted

I'm on the 2.0 build, unrooted, stock everything.
I definitely followed the instructions to the letter.

Just tried with AW1.5 , same problem... (yes I flashed it, because im crazy)

Same problem. Still boot into AW2.0. Official AW2.0 + rooted. Bootloader version is 4.3

wzhy said:
Same problem. Still boot into AW2.0. Official AW2.0 + rooted. Bootloader version is 4.3
Click to expand...
Click to collapse
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...

BIade said:
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...
Click to expand...
Click to collapse
Go here can get older version factory image with older version bootloader
https://developer.android.com/wear/preview/downloads.html
BTW, which bootloader version does this os develop on?
---------- Post added at 22:32 ---------- Previous post was at 22:01 ----------
I found why still boot into android wear!!
The asteroid os system image's path has been change!
Move it to /sdcard/asteroidos.ext4 then go into bootloader and boot zImage.

BIade said:
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...
Click to expand...
Click to collapse
i tried with 4.2 same problem as before...

flo071 said:
i tried with 4.2 same problem as before...
Click to expand...
Click to collapse
Just rootfs path has been change! !
New path is "/sdcard/asteroidos.ext4"

wzhy said:
Just rootfs path has been change! !
New path is "/sdcard/asteroidos.ext4"
Click to expand...
Click to collapse
it gives me the logo but doesnt boot. just stays there for a long time. may try again

[New Update][NON-ANDROID] SailfishOS 3.0 [3.0.3.9]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sailfish OS (also styled as SailfishOS or abbreviated to SFOS) is a mobile operating system combining the Linux kernel for a particular hardware platform use, the open-source Mer core middleware, a proprietary UI contributed by Jolla, and other third-party components.
https://img.xda-cdn.com/sP516dFVJKyUezAnTyIGYjZ1iU0=/http%3A%2F%2Fpraxistipps-images.chip.de%2FZfsIsgbRpVTn3hYYVzeQ91Fxnz0%3D%2F0x0%2Ffilters%3Ano_upscale%28%29%3Aformat%28jpeg%29%2Fpraxistipps.s3.amazonaws.com%252Fdas-jolla-phone_210d4af5.png
It's a beautiful OS developed by the Jolla and the mer team. The UI is totally guesture based. So say good bye to your boring Android navigation bar. The OS is fast and butter smooth with zero lags. This is a totally new experience and certainly a delightful one from the same old boring mundane Android which has had almost the same UI since 5.0 .
Flashing Process:
Note: This has to be flashed over LineageOS 15.1
1. Download LineageOS 15.1: LineageOS 15.1
2. Download Sailfish OS 3.0: SailfishOS 3.0
3. Wipe cache, dalvik cache system and data. Copy the two ROMs to your phone.
4. Flash LineageOS 15.1 first, then Sailfish 3.0 .
Bugs:
Bluetooth.
WiFi once turned off won't work
MTP
Maybe other stuffs I dont Know
Please Note: It is in pre-alpha condition. Not stable. Only for the Curious minds. Stable build will be uploaded in a while. But you can still flash and get a feel of it.
I hope i wasn't too late pushing out a new build. Sorry if I was late
XDA:DevDB Information
SailfishOS, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
PseudoDev, krnlyng, mal, sledges
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2017-10-20
Last Updated 2019-05-19

Wow, very interesting

Great work man..........hope it continues i give it a try when call start working as z 2 is my primary device great work really appreciate....

Hey, Great Work Man!!! I Am Using It As My Daily Driver. Please Fix Those Audio/Video And Calling bug. And Make It Official Please.... Got So Much Bored From Android. Please Make It Stable And Official And Continue The Development. Thanks For Your Work.

Very interesting, I'll watch this thread closely and I'll give it a try asap. Thanks for sharing your work.

Really interesting... Do we have screenshots?

Awesome work dev! I used it on my old redmi 2 and fell in love with it, had since been hoping someone would port it for zuk z2!
Is there any way to use WhatsApp on this build?

himzz0007 said:
Great work man..........hope it continues i give it a try when call start working as z 2 is my primary device great work really appreciate....
Click to expand...
Click to collapse
ChetanLokhande said:
Hey, Great Work Man!!! I Am Using It As My Daily Driver. Please Fix Those Audio/Video And Calling bug. And Make It Official Please.... Got So Much Bored From Android. Please Make It Stable And Official And Continue The Development. Thanks For Your Work.
Click to expand...
Click to collapse
Calling works. Just restart once.
Goldexplorer said:
Really interesting... Do we have screenshots?
Click to expand...
Click to collapse
Will upload in a while

PseudoDev said:
Calling works. Just restart once.
Will upload in a while
Click to expand...
Click to collapse
I have to question...
What we have to do if we want to go back to nouget roms after installing this...?
And WhatsApp and youtube
works in this rom?

@PseudoDev
I cannot get it to boot. When flashing sailfish OS right after flashing CM13, it does not install and gives error (screenshot attached)
It installs successfully after rebooting to TWRP after installing CM13, but on boot, the phone freezes with dim white LED always on. I ran that adb shell command yet it does not boot . I couldn't take logs at that time as phone was not recognized in adb.

hp5942 said:
@PseudoDev
I cannot get it to boot. When flashing sailfish OS right after flashing CM13, it does not install and gives error (screenshot attached)
It installs successfully after rebooting to TWRP after installing CM13, but on boot, the phone freezes with dim white LED always on. I ran that adb shell command yet it does not boot . I couldn't take logs at that time as phone was not recognized in adb.
Click to expand...
Click to collapse
Are you using twrp 3.1? Actually, i forgot to mention that you won't be able to flash this on twrp 3.1.
Holdon, lemme upload twrp 3.0.x
It is chinese but you can change the language in settings. After that, follow the steps again.
Edit: Uploaded. Download the recovery from the downloads tab

PseudoDev said:
Are you using twrp 3.1? Actually, i forgot to mention that you won't be able to flash this on twrp 3.1.
Holdon, lemme upload twrp 3.0.x
It is chinese but you can change the language in settings. After that, follow the steps again.
Edit: Uploaded. Download the recovery from the downloads tab
Click to expand...
Click to collapse
Yes I was using Official TWRP 3.1. I will try using 3.0.x and report later by evening. Thanks for the info

Can i try this rom with dual boot patcher ?

Finally something new , Hope it gets stable soon and development of this rom continues

PseudoDev said:
Calling works. Just restart once.
Will upload in a while
Click to expand...
Click to collapse
where to write in twrp the command i am writing on terminal in twrp its not working ??

himzz0007 said:
where to write in twrp the command i am writing on terminal in twrp its not working ??
Click to expand...
Click to collapse
Did you try on twrp 3.0?
It wont flash on 3.1
The commands run perfectly fine. Probably something wrong in your doing. Try again

PseudoDev said:
Did you try on twrp 3.0?
It wont flash on 3.1
The commands run perfectly fine. Probably something wrong in your doing. Try again
Click to expand...
Click to collapse
no i am not writing in 3.1 i first flash the twrp which u given ..then i install the cm13 then sailfish os then i go in advance of twrp in which terminal in their i go in the terminal and i wrote the command u given but somehow it showing error.....the problem is when i go in fastboot/bootloader option of zuk z 2 it do not show my device in adb in my computer but when i connect my device in 7.1.2 and then i wrote adb devices in terminal its shows...

himzz0007 said:
no i am not writing in 3.1 i first flash the twrp which u given ..then i install the cm13 then sailfish os then i go in advance of twrp in which terminal in their i go in the terminal and i wrote the command u given but somehow it showing error.....the problem is when i go in fastboot/bootloader option of zuk z 2 it do not show my device in adb in my computer but when i connect my device in 7.1.2 and then i wrote adb devices in terminal its shows...
Click to expand...
Click to collapse
What error do you see on terminal when you type it in the twrp terminal? Also, you don't have to go to fastboot. You need to stay on recovery and connect your device. From there, run the commands on PC.

PseudoDev said:
What error do you see on terminal when you type it in the twrp terminal? Also, you don't have to go to fastboot. You need to stay on recovery and connect your device. From there, run the commands on PC.
Click to expand...
Click to collapse
i have done everything as u said but their is only white light coming f in notification bar no boot animation etc....

himzz0007 said:
i have done everything as u said but their is only white light coming f in notification bar no boot animation etc....
Click to expand...
Click to collapse
While running the command, do you see any error?
Like, not found or something like that

[Unknown] China Device P40 Pro+

Dear XDA-Dev-Community,
i have here a china-import with a supposed Android 10.
I would like to install a linaege or other ROM, but which one should I use?
Can you help me?
Basic knowledge for installing and testing is available...
In the appendix you can find some pictures for evaluation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nobody can help?
Maybe I can build my own Custom Rom for this device?
What i hove to do? Save the Drivers?!?!
Anybody know a good guide for me?

Probably a faked one... what build.prop entry ro.board.platform says?
And/or ro.mediatek.platform?

next message

CXZa said:
Probably a faked one... what build.prop entry ro.board.platform says?
And/or ro.mediatek.platform?
Click to expand...
Click to collapse
adb devices -l gives this:
Code:
device usb:1-2 product:P40 Pro+ model:U2 device:Smartphone transport_id:1
Code:
[ro.board.platform]: [mt6580]
[ro.mediatek.platform]: [MT6580]
complete getprop:
https://pastebin.com/h66R0mNk

So, MT6580 and probably a Lollipop. Could be worse.
There is some jlinksz (maker of these) threads here.
Also at 4pda, where there is more info and stuff.
Jlinksz K960 - Обсуждение - 4PDA
Jlinksz K960 - Обсуждение, Планшет, 9.6"
4pda.ru
I would not do much to it if it works well enough as it is. But if you do take a backup first as finding correct one later can be really really hard...

CXZa said:
So, MT6580 and probably a Lollipop. Could be worse.
Click to expand...
Click to collapse
Why worse? What problems you see?
CXZa said:
I would not do much to it if it works well enough as it is.
Click to expand...
Click to collapse
This is not an option. Its so creepy and full of preinstalled apps i can´t trust, u know?
So can i build a custom rom by extract the drivers and AOSP? Is this possible with beginner skills on coding?

0

Seppppx said:
I might be able to help. The kernel source is missing, but there are some device trees for other mt6580 phones. I will try to craft a device tree for this phone.
Click to expand...
Click to collapse
Thanks a lot! I will deliver how fast i can. But this took a long time and i get some troubles:
Seppppx said:
For now i need these things:
1. The android version.
Click to expand...
Click to collapse
Labeld as Android 10, but it's a fake. It looks like Android 6 / Marshmallow
2. raw dd'ed boot image of the device
3. raw dd'ed system image of the device
Click to expand...
Click to collapse
here the trouble beginns...
3. raw dd'ed system image of the device
[/QUOTE]
So i tried to get root by some tools, from this site here:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
But nothing works! by adb sideload or apk-install...
Some advice?

I have the exact same phone, same issues as Ronny has. Have made a backup image of the phone but it's quite large in size ( over 5gb broken into 3 files). Would this be of use in in figuring out how to Root the phone?
B

BruizerBG said:
Have made a backup image of the phone but it's quite large in size ( over 5gb broken into 3 files).
Click to expand...
Click to collapse
Yeah, i´m not alone ;D
Would like to hear how you done this!
And my offer to host your files for downloading on my nextcloud instance.
Could give you an uploadlink (password save) and publish the link here...

Seppppx said:
I might be able to help. The kernel source is missing, but there are some device trees for other mt6580 phones. I will try to craft a device tree for this phone.
For now i need these things:
1. The android version.
2. raw dd'ed boot image of the device
3. raw dd'ed system image of the device
Click to expand...
Click to collapse
Hi Seppppx, I have this phone with Android 5.1 on it. I use Linux so I am assuming I can set the phone up and do the dd's via an adb command?
Any guidance you can give on the correct way to do this would be good and I can try and get the files available for you .
B

ronnyst said:
Yeah, i´m not alone ;D
Would like to hear how you done this!
And my offer to host your files for downloading on my nextcloud instance.
Could give you an uploadlink (password save) and publish the link here...
Click to expand...
Click to collapse
Hi Ronny, you can backup the files on the phone by entering Recovery mode. Switch off the phone. Then, at the same time, hold down the power and volume up buttons down until a small menu appears in the middle of the screen. Choose the recovery option, volume up scrolls through the list, volume down selects which option you want from recovery, fastboot or normal. You'll have a android image pop up, maybe with the message "no command " , just wait or press the same button combination again and the recovery menu should appear . In the list will be the system or user files backup. I see from your images though that you have already figured most of the out.
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B

BruizerBG said:
Hi Seppppx, I have this phone with Android 5.1 on it. I use Linux so I am assuming I can set the phone up and do the dd's via an adb command?
Click to expand...
Click to collapse
At first: You need to be root do dd boot and systemimages. After you got it you get try this:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com
But i tried this and i failed because a doesn´t have su (root). So i tried to use adb push but even then i cant access the Boot/system-image folders (cause no root). See my previous posts for...

BruizerBG said:
Hi Ronny, you can backup the files on the phone by entering Recovery mode. Switch off the phone. Then, at the same time, hold down the power and volume up buttons down until a small menu appears in the middle of the screen. Choose the recovery option, volume up scrolls through the list, volume down selects which option you want from recovery, fastboot or normal. You'll have a android image pop up, maybe with the message "no command " , just wait or press the same button combination again and the recovery menu should appear . In the list will be the system or user files backup.
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B
Click to expand...
Click to collapse
Just look at my pictures from previous posts... I´d already done this...

BruizerBG said:
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B
Click to expand...
Click to collapse
Sorry Bruizer, but this option gives us only a dump of the userdata. this will doesn´t help Seppppx.

Any update on this? I have received a phone to use as back up until I get my own and it's the same type of deal as far as chinese phone goes.

Also, I forgot to mention that I was looking through the adb pull screen shot and even though I do not currently have root I can still cd to /dev/block/platform/mtk-msdc.0/ without viewing contents but when i try to cd by-name there is no directory by that name.... I want to be able to achieve root and also possibly make a custom rom for this device and I'm willing to follow any suggestions anybody has. Clearly the boot.img and such are in a different directory but I'm going to have to do more digging.

whizpopthat said:
Any update on this? I have received a phone to use as back up until I get my own and it's the same type of deal as far as chinese phone goes.
Click to expand...
Click to collapse
sorry no updates. we (BruizerBG and me) aren´t able to dd the boot partition.
I would be happy for any advice or help!!!

ronnyst said:
sorry no updates. we (BruizerBG and me) aren´t able to dd the boot partition.
I would be happy for any advice or help!!!
Click to expand...
Click to collapse
I'm trying to find some time to do some digging about finding the boot partition because as I stated in my last post the by-name dir doesn't exist but obviously we are unable to find out which dirs do exist without root... If I come up with something I will be sure to let you know.

Where to download LineageOS? Why is there two options?

I'm a bit confused where to download lineageos for my phone.
I found two official links, why are there two?
Which link should i use to download lineageos and why?
LineageOS Downloads
download.lineageos.org
Sony Xperia XA2 (pioneer) - LineageOS ROMs
LineageOs ROM Sony Xperia XA2 (pioneer) Official roms Download last nightly build (2023-01-05) (mirror EU).LineageOS 19.1 – [ Android 12.1 (Snow Cone) ] [Recovery file (2023-01-05) (mirror EU)] Previous version (nightly) (2022-04-21) LineageOS 18.1 – [ Android 11.0 (Red Velvet Cake) ] [Recovery...
lineageosroms.com
The "top domain" which brought me to the download page was this:
LineageOS Downloads
download.lineageos.org
Home - LineageOS ROMs
Welcome to LineageOS ROMs, this site is listing the official changes and downloads for LineageOS and many other useful tools, such as CF-ROOT, G-APPS (Google Apps), Recoveries (TWRP Recovery, CWM Recovery) and much more. DISCLAIMER: LineageOS does not develop official ROMs for all brands and...
lineageosroms.com
Both these links provide a list of support phone manufactuers and models.
Why are there two different lists with sometimes different results?

lineageos.org is the real deal (or at least I'd love to believe so, the other one doesn't even list any maintainers)
Still, interesting and valid question - i don't know neither who is running the other one... but perhaps this helps:
https://forum.xda-developers.com/t/lineageosrom-com.3535772/#post-70692025

SigmundDroid said:
lineageos.org is the real deal (or at least I'd love to believe so, the other one doesn't even list any maintainers)
Still, interesting and valid question - i don't know neither who is running the other one... but perhaps this helps:
https://forum.xda-developers.com/t/lineageosrom-com.3535772/#post-70692025
Click to expand...
Click to collapse
Damn, i downloaded lineageos from lineageosroms.com and already installed it.
To be honest even if that doesn't mean anything it looks legit, there is no trace of google on my device and it works fine.
One thing i noticed, i can't even find a lineageosrom for my device on lineageos.org, it simply isn't listed.
In case you are woondering, i have a samsung galaxy s7.
This is where i downloaded the rom https://lineageosroms.com/herolte/
I can't find any rom for the S7 on the lineage org domain...
LineageOS Downloads
download.lineageos.org
Devices | LineageOS Wiki
wiki.lineageos.org
Wikipedia says lineageos.org
But what choice do i have.. none there is no rom on the org domain so ill have to trust the .com version..
Wired.
Edit: The rom i downloaded is a nightly build, there is no stable one, maybe that's the reason?

Librem5OS said:
samsung galaxy s7
Click to expand...
Click to collapse
Ah, I see, that'll be tricky then...
I just checked and seems most people are on LOS17:
https://stats.lineageos.org/model/herolte
Remembered something vaguely from webarchive and found this:
https://archive.org/search.php?query=lineageos 17 backup
Alas, couldn't see any herolte
Finally found this:
https://forum.xda-developers.com/t/stable-lineageos-17-1-for-galaxy-s7-build-38.3980101/
https://ivanmeler.github.io/devices/herolte.html
Should be a better choice than lineageosroms, eh?

SigmundDroid said:
Ah, I see, that'll be tricky then...
I just checked and seems most people are on LOS17:
https://stats.lineageos.org/model/herolte
Remembered something vaguely from webarchive and found this:
https://archive.org/search.php?query=lineageos 17 backup
Alas, couldn't see any herolte
Finally found this:
https://forum.xda-developers.com/t/stable-lineageos-17-1-for-galaxy-s7-build-38.3980101/
https://ivanmeler.github.io/devices/herolte.html
Should be a better choice than lineageosroms, eh?
Click to expand...
Click to collapse
Thank you so much!! Appreciated!
I would have never found that, already installed!
Also the statistics you sent very interesting https://stats.lineageos.org/model/herolte, second most users have set their region to unknown, mine is US but im not from the US, can i change the region by any chance? Can't see to find an option. I can't remember selecting US at all.

Wow, the new lineageos version is... it is...
There are some apps like storage manager or shell that have access to physicall motion detection and much much more permissions and the problem is, the option to disable that access IS GREYED OUT, what's going on with lineageos??

Librem5OS said:
what's going on with lineageos??
Click to expand...
Click to collapse
Blame google at this point, I suffer from similar problems (backup with syncthing). It's about time for better system like plasma mobile...
Librem5OS said:
can i change the region by any chance
Click to expand...
Click to collapse
Yes, can be tricky if you have weird combos (like english and non-english settings, eg ISO-date). It's called localization and you'll find in the settings. Apropos, spend an evening or so and check every single item of there - there is so much finetuning available
Don't get me wrong but welcome home in the ever changing world of LOS (both in sarcastic and an honest way)

SigmundDroid said:
Blame google at this point, I suffer from similar problems (backup with syncthing). It's about time for better system like plasma mobile...
Yes, can be tricky if you have weird combos (like english and non-english settings, eg ISO-date). It's called localization and you'll find in the settings. Apropos, spend an evening or so and check every single item of there - there is so much finetuning available
Don't get me wrong but welcome home in the ever changing world of LOS (both in sarcastic and an honest way)
Click to expand...
Click to collapse
Are you saying google has influence over lineageos? I mean as far as i know, google owns android.
However android is opensource (atleast most of it as far as i know, but not fully open source).
It's just.. i think lineageos is great but i am not sure if it can really be trusted anymore, these changes that i noticed are a bit suspicious in my opinion.
> Apps > Special Acces > Useage Data Access
By default all apps have useage access... This was not the case in previous versions
> Apps > Special Acces > Device Administrator
Is storage manager an active device administrator in lineage 19.1 yes or no?
The "show system" option is gone so there is no way to know if the app has access or not...
Under privacy settings what happened to the setting "start on boot"
In previous versions there was this option to deny individual app access, now it's gone...
This doesn't seem good at all...
PS: my region changed automtically (or it was after i changed language)
But why does the lanuage have impact on region?? Anyways this is not important, but what i would like to know is how so many devices have their region shows as "unknown" in the statistics you sent.
How do i set my location to unknown?
And the things i mentioned above, have you got any tip where i could share this in form of a question to the developers? I just want to know why this changes happened and if lineageos is going a bad path.

Librem5OS said:
google owns android.
However android is opensource
Click to expand...
Click to collapse
Well, it's "complicated". Making a recent android run on specific devices is no easy thing (companies)... not any easier on older devices (devs/maintainers).
Still, I think LOS is one best things (just consider the companies' bloatware)
Librem5OS said:
not the case in previous versions
Click to expand...
Click to collapse
Quite specific, eh? I wouldn't know, still on LOS18... but such things are part of "the ever changing world" Perhaps asking again in "your" device's forum?
PS: Consider a second device for testing other/new versions/ROMs/OSes... you don't wanna brick your main gadget.

SigmundDroid said:
Well, it's "complicated". Making a recent android run on specific devices is no easy thing (companies)... not any easier on older devices (devs/maintainers).
Still, I think LOS is one best things (just consider the companies' bloatware)
Quite specific, eh? I wouldn't know, still on LOS18... but such things are part of "the ever changing world" Perhaps asking again in "your" device's forum?
PS: Consider a second device for testing other/new versions/ROMs/OSes... you don't wanna brick your main gadget.
Click to expand...
Click to collapse
If i would have to find a new phone today most likely would go for google pixel (i hate google) but then flash grapheneOS on it, or maybe librem or fairphone, but i'm not familiar with them yet.
PS: i have no second device.
Also late me share an issue that i ran into today
I installed TWRP 3.6.2 and LineageOS 19.1 on my Samsung Galaxy S7, then i installed whatsapp (for testing purposes not to use it, because its facebook spyware) then after the testing was done i wanted to uninstall whatsapp but when i pressed uninstall the responsible service always stopped, but i was able to uninstall ANY other app expect whatsapp (facebook) decided to dig itself so deep in my phone i was unable to uninstall it, (besides even if i managed to uninstall it i am sure there will remain some "hidden" whatsapp activity on the device.
ANYWAYS, i decided to wipe my phone clean by using TWRP, after doing that i used TWRP to flash/install LineageOS 19.1 on my phone again, however i am now STUCK in the TWRP "loading screen" it simply won't go to recovery mode so i am unable to install LineageOS or do anything at all.
Next i will try to use adb to boot into recovery, if that doesn't work i will try to flash LineageOS 17 or 18 on the device.
The only thing working now is downloadmode.
EDIT:
I tryed useing universal adb drives, not to be confused with adb fastboot and platformtools.
Downloaded here https://adb.clockworkmod.com/
Don't know if this is legit https://developer.android.com/studio/releases/platform-tools
I just didn't download it after seeing the license agreement and google involvement. Can it be trusted?
Anyways... in cmd i typed adb devices
Output: daemon started succesfully
Output: list of devices attached
I tryed using: adb reboot recovery
Output: error no devices/emulators found
Then i tryed flashing the oldest twrp 3.0.0 with odin and it worked, but after odin said PASS the phone behaviour has not changes, it's the same as before stuck in twrp mode but not booting into recovery.
My phone is now useless it does not boot at all, not in twrp mode and not in recoverymode, however this is only the case when the phone is not connected to a charging/usb cable, if it is connected the phone vibrates once and the display goes on saying "samung galaxy s7 powered by android".
This display is forever, nothing happens it's stuck.
I am unable to boot into recovery (twrp) mode by presing home+power+volumeup, however the ONLY thing i can do now is boot into downloadmode by pressing home+power+volumedown.
I can use oding to flash a recovery or OS, i can use adb.
But i don't know what to do now.
(One person with same issue said they took out they battery, well f*ck modern phones...)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT:
adb devices no longer working (reason unknown - atleast as far as i can tell...)
will try flashing stock rom...

EDIT SOLVED
fixed it... flashed twrp like 6 times... sometimes it got stuck, sometimes it worked, then stuck on twrp loadingscreen but now it booted into recovery... i used "nand erase" on the last attempt, maybe that did the job, who knows..
UPDATE
twrp 3.6.2 is now installed and booting to recovery.
but after installing lineageos 19.1 the phone is stuck in a boot loop.
twrp shows "running open recovery script" it displays some errors and reboots eternal.

UPDATE - DONE
Woah... finally after all this wired mess... formated data with twrp and wiped everything then lineageos installation worked, no stockrom needed.

Holy, missed most of your last posts but glad you made it! Looks like real work - as in blood, sweat and tears... and probably a lot of cursing