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
Related
SailfishOS for Galaxy Nexus (GSM)
{
"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"
}
This is a community port of Jolla's SailfishOS for the Galaxy Nexus.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different operating system.
It only uses parts of Android for hardware enablement (drivers).
Special Thanks to vakkov, sledges, mugna91, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Galaxy Nexus port is considered to be of alpha quality.
Though depending on your usage it might be stabile enough for daily use.
Bug reports:
Please issue bugreports at the Nemo Project Bugzilla.
Known issues:
Due to an issue with ofono, reading from SIM does not work. You'll need to remove your PIN lock before flashing.
Setting an ambiance (color theme & wallpaper) causes hangs. Either needs the battery to be pulled, or you can SSH into the device and run:
systemctl --user restart lipstick
The startup wizard is getting skipped for now, due to the issue above.
The Jolla Store currently does not work. As an alternative you can try Warehouse for OpenRepos.
The camera does not work.
Due to redistribution issues the codec for MP3 can't shipped. To enable the codec run the following command:
devel-su zypper in gst-av
Instructions & Download:
Make a backup
Factory Reset (Wipe /data & /cache)
Wipe /system
Install CyanogenMod 10.1.3
Install SailfishOS on top:
Mirrors:
beidl.eu
Reboot
Old versions:
Alpha1:
XDA
beidl.eu
XDA:DevDB Information
SailfishOS for Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
beidl, vakkov, sledges
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-08-03
Last Updated 2014-08-24
Reserved
Changes:
August 24th, 2014:
Notification LED working
Bluetooth activation/deactivation fixed
Changes for Video playback (work in progress)
August 3rd, 2014:
Initial release
Nice & interesting..
Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).
Justice™ said:
Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).
Click to expand...
Click to collapse
Mirror to my private server added.
Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.
freshgiammi said:
Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.
Click to expand...
Click to collapse
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.
beidl said:
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.
Click to expand...
Click to collapse
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.
i couldnt select allow untrusted software to install warehouse. it does nothing when i select accept to allow it o settings.
freshgiammi said:
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.
Click to expand...
Click to collapse
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.
beidl said:
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.
Click to expand...
Click to collapse
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
edit:
ah yeah it does ext4..
z3n0x1 said:
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
Click to expand...
Click to collapse
Yes, I would assume it needs to be EXT4
Justice™ said:
Yes, I would assume it needs to be EXT4
Click to expand...
Click to collapse
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..
z3n0x1 said:
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..
Click to expand...
Click to collapse
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.
Justice™ said:
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.
Click to expand...
Click to collapse
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
EDIT:
open terminal
type cd ~/Downloads
type pkcon install-local ./downloaded-package.rpm
got "fatal error:nothing provides libsailfishapp.so.1 needed by harbour-warehouse-0.3-20.armv7h"
need the libsailfishapp.so.1.. lookfor it now..
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm
z3n0x1 said:
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm
Click to expand...
Click to collapse
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
From terminal, root
Install a package
rpm –ivh packagename
upgrade a package
rpm –Uvh packagename
you can find out what the switches mean by doing a rpm --help from the command line.
Click to expand...
Click to collapse
I think -ivh would indicate installation and -uvh being the uninstall process
Justice™ said:
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
I think -ivh would indicate installation and -uvh being the uninstall process
Click to expand...
Click to collapse
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
EDIT:
error: failed dependdencies:
libsailfishapp.so.1 is needed by harbour-warehouse-0.3-20.armv7h
so i perssume it the libsailfishapp.so.1 the problem..
http://forum.xda-developers.com/showpost.php?p=53171554&postcount=90
he's said that just copy it from /usr/lib/ . but how come even we don't have filemanager..
i'll try the pkcon install jolla-fileman (the native file manager from jolla) apprently the rpm are not there..
just maybe.. even we have the native file manager.. the missing libsailfishapp.so.1 still occur..
z3n0x1 said:
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
Click to expand...
Click to collapse
I must've misread it as uninstall then, yeah.
Justice™ said:
I must've misread it as uninstall then, yeah.
Click to expand...
Click to collapse
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?
z3n0x1 said:
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?
Click to expand...
Click to collapse
You could try and SSH in and run the commands, which may be easier, I'm trying to get the warehouse installed now
{
"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
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
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.
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as OTAs.
Complete procedure can be followed from this detailed guide
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and Changelogs for all the versions.
Builds with and without minimal Google services (GApps) included are provided for convenience.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Join the Telegram group for support and extras
Donate
If you found my work useful and want to continue supporting development contribute by becoming a
Patron for early releases and better support.
You can also provide a small donation through PayPal
Indian users can support through UPI: [email protected]
Kernel source code
ROM source code
Reserved
Install without problems, nice stock rom like HentaiOs.
For everybody no Faceunlock or did I miss something, didn't find it.
How to install Magisk? If I flash Twrp nothing happens just a black screen if I boot to Recovery.
r3sp said:
Install without problems, nice stock rom like HentaiOs.
For everybody no Faceunlock or did I miss something, didn't find it.
How to install Magisk? If I flash Twrp nothing happens just a black screen if I boot to Recovery.
Click to expand...
Click to collapse
Does it come with aosp apps such as dialler, contacts? Or using google apps
Sorry doesn't looked up so deep, im right now on another rom so far because of magisk and faceunlock.
r3sp said:
Install without problems, nice stock rom like HentaiOs.
For everybody no Faceunlock or did I miss something, didn't find it.
How to install Magisk? If I flash Twrp nothing happens just a black screen if I boot to Recovery.
Click to expand...
Click to collapse
Twrp is not supported
And for magisk you can just patch the provided boot image and flash from bootloader mode.
About faceunlock there is no open-source implementation made for aosp ROMs.
Any bug on ProtonAOSP rom?
Good work. Great rom... everything goes perfect and very good consumptions. In my opinion is the best Aosp for our device.
Dividi54 said:
Good work. Great rom... everything goes perfect and very good consumptions. In my opinion is the best Aosp for our device.
Click to expand...
Click to collapse
How is battery life? is it widevine L1? any bug? ... I would like to know your feedback sir
castanedajor said:
¿Cómo dura la batería? ¿Es widevine L1? algún error? ... Me gustaría conocer sus comentarios, señor
Click to expand...
Click to collapse
The battery so far so good... yesterday almost 11 hours of screen time with 37h. The widevine is L1 and I haven't found any bugs. I don't know if people will like it, as it's very stock, but I hope it will have continuity.
Deleted.
uriii13 said:
Maybe a "how to flash" guide? I'm new with the phone; just unlocked the bootloader and going to flash it... if I see how hahaha
Click to expand...
Click to collapse
There is a detailed guide in the first post.
Ultraschorsch said:
There is a detailed guide in the first post.
Click to expand...
Click to collapse
True. Thanks!
{
"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"
}
I can not find this step. Someone helps?
And I have to add that "fastboot --setactive=a" command was not doing anything:
uriii13 said:
View attachment 5355217
I can not find this step. Someone helps?
And I have to add that "fastboot --setactive=a" command was not doing anything:
View attachment 5355231
Click to expand...
Click to collapse
Try "fastboot --set-active=a" instead
Belerefontis said:
Try "fastboot --set-active=a" instead
Click to expand...
Click to collapse
Still nothing:
And these are the files I have:
Edit: still blocked there I guess it has to be something related to the "adb" folder and the fastboot.exe. I have the "adb" folder from my last ROG Phone 2. Anyway, in the tutorial it doesn't say anything about that folder, but as long as I'm reading in the cmd, it's trying to find something there, innit?
I used
fastboot --set-active=a
and no problems.
uriii13 said:
Still nothing:
View attachment 5355235
And these are the files I have:
View attachment 5355233
Edit: still blocked there I guess it has to be something related to the "adb" folder and the fastboot.exe. I have the "adb" folder from my last ROG Phone 2. Anyway, in the tutorial it doesn't say anything about that folder, but as long as I'm reading in the cmd, it's trying to find something there, innit?
Click to expand...
Click to collapse
Did you try using CMD? Probably this is not a problem, but, sometimes Powershell is not completely compatible with some tools .... If you are on Powershell just type cmd and click enter, you should be good to go.
uriii13 said:
Still nothing:
View attachment 5355235
And these are the files I have:
View attachment 5355233
Edit: still blocked there I guess it has to be something related to the "adb" folder and the fastboot.exe. I have the "adb" folder from my last ROG Phone 2. Anyway, in the tutorial it doesn't say anything about that folder, but as long as I'm reading in the cmd, it's trying to find something there, innit?
Click to expand...
Click to collapse
There shouldn't be a space between "--" and "set-active=a"
Wrong -- set-actice=a
Right --set-active=a
Also download the latest platform tools and unpack them and type cmd in the address bar of that folder (which would launch cmd window) and use fastboot commands from there
castanedajor said:
Did you try using CMD? Probably this is not a problem, but, sometimes Powershell is not completely compatible with some tools .... If you are on Powershell just type cmd and click enter, you should be good to go.
Click to expand...
Click to collapse
arifqur said:
There shouldn't be a space between "--" and "set-active=a"
Wrong -- set-actice=a
Right --set-active=a
Also download the latest platform tools and unpack them and type cmd in the address bar of that folder (which would launch cmd window) and use fastboot commands from there
Click to expand...
Click to collapse
r3sp said:
I used
fastboot --set-active=a
and no problems.
Click to expand...
Click to collapse
I knew the prob now. My bro "illuminated" my brain: I had to use Minimal ADB & Fastboot 1.4.3 to apply "fastboot --set-active=a" cmd, but actually what I was using was the normal/Windows cmd on the folder where I had the Boot and Vendor files (shift + right click opens Windows, not the Minimal 1.4.3 fastboot).
So what I did was:
(with the normal cmd: shift + right click)
fastboot flash boot_a boot.img
fastboot flash vendor_boot_a vendor_boot.img
(closing the normal. Going to the Minimal 1.4.3 and executing fastboot.exe)
fastboot --setactive=a
It worked.
I was writting well the --setactive=a, but it was returning me a "-- setactive" idk why.
Now what I will try, as you said, to insert "cmd" on the platform-tools folder and done.
EDIT:
Possible bugs:
- Weird stuff adding in the setup the Google Account (like had to repeat it twice)
- Telegram, Instagram, Whatsapp, etc. audios-vocals, are sent/recorded in quite low voice
- Periodically, Wifi stops working: it doesn't find any wifi. It happened once in 2 days, so it's not so, so bad (I'm in a place with around 20 wifi sources). Always solved by a system reboot, so nothing important.
Tryied to factory reset and, for now, these are the bugs on both factory reset. I will add more when I know.