Project Treble makes it possible to have Updates even on lower end devices.
But is here someone that can actually confirm that the P10 Lite
Is able to run Treble once it gets Oreo?
AymZ12 said:
Project Treble makes it possible to have Updates even on lower end devices.
But is here someone that can actually confirm that the P10 Lite
Is able to run Treble once it gets Oreo?
Click to expand...
Click to collapse
I have seen rumors that P10 Lite will get Oreo with Treble support but since we don't have Oreo yet, it's not really possible to confirm. However similar devices like Mate 10 Lite and 7X did get Treble with their Oreo update I believe.
Trixanity said:
I have seen rumors that P10 Lite will get Oreo with Treble support but since we don't have Oreo yet, it's not really possible to confirm. However similar devices like Mate 10 Lite and 7X did get Treble with their Oreo update I believe.
Click to expand...
Click to collapse
Well heres a link from XDA itself
https://www.xda-developers.com/list-android-devices-project-treble-support/
The P10 Lite is listed there.
I think it pretty much confirms Treble and Oreo.
With that major Updates and good Custom Roms shouldnt be a Problem anymore
AymZ12 said:
Well heres a link from XDA itself
https://www.xda-developers.com/list-android-devices-project-treble-support/
The P10 Lite is listed there.
I think it pretty much confirms Treble and Oreo.
With that major Updates and good Custom Roms shouldnt be a Problem anymore
Click to expand...
Click to collapse
I did see that but they're not linking a source whereas they do so for other devices so I'm kinda questioning the accuracy.
Trixanity said:
I did see that but they're not linking a source whereas they do so for other devices so I'm kinda questioning the accuracy.
Click to expand...
Click to collapse
Yeah I noticed that too wich is why I was looking for someone here to confirm it.
Its pretty much safe that we will get Oreo and seeing that they add Treble Support for devices like the p10 wich was shipped with Nougat is another strong indication that those Phones that revieve the Update get Treble Support aswell
AymZ12 said:
Yeah I noticed that too wich is why I was looking for someone here to confirm it.
Its pretty much safe that we will get Oreo and seeing that they add Treble Support for devices like the p10 wich was shipped with Nougat is another strong indication that those Phones that revieve the Update get Treble Support aswell
Click to expand...
Click to collapse
We do have Treble on P10 Lite.
{
"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"
}
Sent from my WAS-LX1 using Tapatalk
AymZ12 said:
Project Treble makes it possible to have Updates even on lower end devices.
But is here someone that can actually confirm that the P10 Lite
Is able to run Treble once it gets Oreo?
Click to expand...
Click to collapse
I've actually already tested a treble ROM by @phhusson and it works quite well, besides the unnavaiability of gapps since we don't have a recovery supporting Oreo yet.
Hope that was useful
geeklynx said:
I've actually already tested a treble ROM by @phhusson and it works quite well, besides the unnavaiability of gapps since we don't have a recovery supporting Oreo yet.
Hope that was useful
Click to expand...
Click to collapse
doesnt phusson have one image that already has both gapps and root?
oh and btw you can flash recovery from Huawei P Smart, it appears to work, but is some chinese fork of TWRP, you can change language in settings on it so its okay. remember to flash to recovery_ramdisk partiton
geeklynx said:
I've actually already tested a treble ROM by @phhusson and it works quite well, besides the unnavaiability of gapps since we don't have a recovery supporting Oreo yet.
Hope that was useful
Click to expand...
Click to collapse
Did you tested Android 8.1? The smoothness is better than stock?
Sent from my WAS-LX1 using Tapatalk
I couldn't get phhussons images to work, not sure why. I only got bootloop tried wiping data too but that also bootlooped and threw me into eRecovery...
restored stock system with P Smart TWRP luckily so no damage done heh.
once I got home I got it to work, resize partition with resize2fs /dev/block/mmcblk0p51
4,5gb system! wow lord!
then install gapps stock package wooo!
but adb is not working... and nfc seems to not be in the rom. otherwise is perfect
GizmoTheGreen said:
I couldn't get phhussons images to work, not sure why. I only got bootloop tried wiping data too but that also bootlooped and threw me into eRecovery...
restored stock system with P Smart TWRP luckily so no damage done heh.
once I got home I got it to work, resize partition with resize2fs /dev/block/mmcblk0p51
4,5gb system! wow lord!
then install gapps stock package wooo!
but adb is not working... and nfc seems to not be in the rom. otherwise is perfect
Click to expand...
Click to collapse
I ****ed up... Can someone give me a stock boot/ramdisk img?
geeklynx said:
I ****ed up... Can someone give me a stock boot/ramdisk img?
Click to expand...
Click to collapse
https://jaizu.moe/RAMDISK.img
It's uploading atm, give it 5 minutes to get uploaded.
GizmoTheGreen said:
I couldn't get phhussons images to work, not sure why. I only got bootloop tried wiping data too but that also bootlooped and threw me into eRecovery...
restored stock system with P Smart TWRP luckily so no damage done heh.
once I got home I got it to work, resize partition with resize2fs /dev/block/mmcblk0p51
4,5gb system! wow lord!
then install gapps stock package wooo!
but adb is not working... and nfc seems to not be in the rom. otherwise is perfect
Click to expand...
Click to collapse
So, we need a good TWRP recovery in the first place. One made for the P10 Lite, because I don't really know if we have the same partitions on P10 Lite vs P Smart. On the Mate 10 or P10 I don't remember exactly they get decyrption working in TWRP, we just need a dev who can deal this and make a Oreo compatibile TWRP. Maybe @HassanMirza01 can help us. I can do it too if I do some research but I don't have the time for this.
One question: /dev/block/mmcblk0p51 what partition is this ? System or data ? /data needs to be F2FS for AOSP or EXT4 ?
Eurofighter_ty said:
So, we need a good TWRP recovery in the first place. One made for the P10 Lite, because I don't really know if we have the same partitions on P10 Lite vs P Smart. On the Mate 10 or P10 I don't remember exactly they get decyrption working in TWRP, we just need a dev who can deal this and make a Oreo compatibile TWRP. Maybe @HassanMirza01 can help us. I can do it too if I do some research but I don't have the time for this.
One question: /dev/block/mmcblk0p51 what partition is this ? System or data ? /data needs to be F2FS for AOSP or EXT4 ?
Click to expand...
Click to collapse
51 is System, it is already in the right format since you flash it as .img!
I think the rom supports f2fs for data but you can use ext4 probably... I am going back to huawei oreo because phh-aosp on this device refused to pass safety net in magisk and modules didnt work, only root :/
GizmoTheGreen said:
51 is System, it is already in the right format since you flash it as .img!
I think the rom supports f2fs for data but you can use ext4 probably... I am going back to huawei oreo because phh-aosp on this device refused to pass safety net in magisk and modules didnt work, only root :/
Click to expand...
Click to collapse
So, so after you flash the system.img the system partition gets the wrong size and we need to resize it via TWRP ?
Eurofighter_ty said:
So, so after you flash the system.img the system partition gets the wrong size and we need to resize it via TWRP ?
Click to expand...
Click to collapse
yes, for Treble system roms, the img is an entire formatted filesystem and it has no free space (minimal size to be installable on the most phones, it's not good if it was 4gb and system partition was only 2gb on some midels, right? )
so we resize it to take up all the space of the real partition so we have room for gapps
Jaizu said:
https://jaizu.moe/RAMDISK.img
It's uploading atm, give it 5 minutes to get uploaded.
Click to expand...
Click to collapse
Thank you, I've actually solved it right after I posted this... You still get the good karma tho
Eurofighter_ty said:
So, we need a good TWRP recovery in the first place. One made for the P10 Lite, because I don't really know if we have the same partitions on P10 Lite vs P Smart. On the Mate 10 or P10 I don't remember exactly they get decyrption working in TWRP, we just need a dev who can deal this and make a Oreo compatibile TWRP. Maybe @HassanMirza01 can help us. I can do it too if I do some research but I don't have the time for this.
One question: /dev/block/mmcblk0p51 what partition is this ? System or data ? /data needs to be F2FS for AOSP or EXT4 ?
Click to expand...
Click to collapse
i can do that but issue is i dont own any Oreo device for now... oreo not coming for P9 Lite... waiting for some other device with oreo so i can do things on oreo too....
HassanMirza01 said:
i can do that but issue is i dont own any Oreo device for now... oreo not coming for P9 Lite... waiting for some other device with oreo so i can do things on oreo too....
Click to expand...
Click to collapse
Thanks anyway ! The thing is that I compiled TWRP with decryption support for the P10 Lite but when I get invalid argument in the command log of the TWRP on every partition declared in the fstab and one dev said that is a upstream problem.
Related
Hello Guys, I Know how all of you Are sooo Crazyyy about having to Get 5.0 Lollipop for your Note 2.... No More Waiting....
Im Clearly Stating Here this really aint a Normal Daily Driver....
Here is the Link: https://www.mirrorcreator.com/files/...7100.zip_links <-- Mirror Link but Be Warned about the Bugs
Gapps Link: http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
Root ( Use this Supersu Package for now ): http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Flashable Busybox: http://forum.xda-developers.com/attachment.php?attachmentid=3007867&d=1415593576
What Works:
1. Bluetooth
2. Music/Sound
3. RIL but Partially
4. LEDS/ Notification Light
5. WIFI But Partially Something is Wrong but dont know Exact for now.
Requirements/Procedure:
1. Install Latest TWRP Recovery ( I Recommend )
2. Should Be on Latest Stock Touchwiz 4.4.2 Kitkat
3. Factory Reset... ( Clear Dalvik Cache, Cache , System and Data )
4. Select the Rom and Flash Away... Choose Whichever Gapps Package you Seem to like to install but should be the lollipop Package
5. Reboot and Viola
All Credits Go to the Respective Developer and Also To the Team Behind it '' Nameless Rom ''
I Am Just Sharing the Above Link for Others to Enjoy and Test it on your GT-N7100 and until Nameless Rom theirSelves Dont have a thread of it... GT-I9300 Got it.
Good Luck And Have Fun Flashing....
Some Important Answers for Some People:
Yes Nova Launcher Works on 5.0 Lollipop
Yes Viper4android works on 5.0 Lollipop ( Enable it, and then use Compatibility Mode... Should Have Root and Use Selinux mode changer from Play Store and Set to Permissive ) <--- On your Own Risk
People Who Have Issues, Problems while Flashing... Errors You Can Comment Below and Share in this Thread For Now So our whoel community can also know and try to help the Developers... but this is just a normal thread when the official thread is made all issues will be reported there not here...
{
"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"
}
Bugs/Issues:
1. Bootanimation Has Weird White Effect Coming and Going
2. Some Reboots i See
3. Wifi Isnt Connecting to my Home Network Even after inputting the correct password
4. Reboots Alot (One Way to fix is reboot and clear dalvik and cache) <--- Com.android.phone has somthing to do with all the Reboots or Else the Rom is working good
5. Camera Getting Stuck Freezes/Some Hal Related Issue i Guess ( Use Google Camera from Play Store )
6. Mobile Network Doesnt Work but Still Shows the H or H+ Signal
ikaster17 said:
Hello Guys, I Know how all of you Are sooo Crazyyy about having to Get 5.0 Lollipop for your Note 2.... No More Waiting....
Here is the Link: https://build.nameless-rom.org/
What Works:
1. Bluetooth
2. Music/Sound
3. RIL but Partially
4. LEDS/ Notification Light
5. WIFI But Partially Something is Wrong but dont know Exact for now.
Requirements/Procedure:
1. Install Latest TWRP Recovery ( I Recommend )
2. Should Be on Latest Stock Touchwiz 4.4.2 Kitkat
3. Factory Reset... ( Clear Dalvik Cache, Cache , System and Data )
4. Select the Rom and Flash Away... Choose Whichever Gapps Package you Seem to like to install but should be the lollipop Package
5. Reboot and Viola
All Credits Go to the Respective Developer and Also To the Team Behind it '' Nameless Rom ''
I Am Just Sharing the Above Link for Others to Enjoy and Test it on your GT-N7100 and until Nameless Rom theirSelves Dont have a thread of it... GT-I9300 Got it.
Good Luck And Have Fun Flashing....
Some Important Answers for Some People:
Yes Nova Launcher Works on 5.0 Lollipop
Yes Viper4android works on 5.0 Lollipop ( Enable it, and then use Compatibility Mode... Should Have Root and Use Selinux mode changer from Play Store and Set to Permissive ) <--- On your Own Risk
People Who Have Issues, Problems while Flashing... Errors You Can Comment Below and Share in this Thread For Now So our whoel community can also know and try to help the Developers... but this is just a normal thread when the official thread is made all issues will be reported there not here...
Click to expand...
Click to collapse
Thnk a lot fr da info bro....
Hit thanks if you like my post or if I helped you in any ways...
:laugh::laugh::laugh::laugh:
I'm going to flash immediately!
ikaster17 said:
Bugs/Issues:
1. Bootanimation Has Weird White Effect Coming and Going
2. Some Reboots i See
3. Wifi Isnt Connecting to my Home Network Even after inputting the correct password
4. Reboots Alot (One Way to fix is reboot and clear dalvik and cache)
Click to expand...
Click to collapse
Hey and wat abt the gapps package....means is it released yet...??
[email protected] said:
Hey and wat abt the gapps package....means is it released yet...??
Click to expand...
Click to collapse
I'm going to flash this
http://forum.xda-developers.com/goo.../gapps-google-apps-flashable-package-t2930260
Edit: for now I'm in a bootloop...
Edit 2: BOOTED The first boot takes long and rom reboots itself on setup wizard -.-
WARNING
RIL seems to have some issues... on EVERY boot I got locked out from my SIM, requesting PUK CODE to unlock and set a new pin... so be careful.
I'm going to switch off pin code request.
KEYBOARD NOT WORKING ON FIRST BOOT... I'd to activate it on settings (not a problem)
WiFi WORKING.
CAMERA FREEZING THE PHONE
Someone try with multirom?
Inviato dal mio GT-N7100
FUSIONdev said:
WARNING
RIL seems to have some issues... on first boot I got locked out from my SIM, requesting PUK CODE to unlock and set a new pin... so be careful.
Click to expand...
Click to collapse
Yes It will be having those issues... and yeah i understand your issue Especially if you have a sim code lock on your phone it might get a puk code so please dont try it with a pin code...
as for the reboot issue i dont understand it, i got the phone to run used it for half hour i got lucky but after that it rebooted again but for the time being it was really fast smooth and Project Volta FTW (Y)
Does this ROM boot to someone?
mimmo13 said:
Does this ROM boot to someone?
Click to expand...
Click to collapse
It boots ! Just wait the long boot process... it's because of ART ! It's slower on first boot!
mimmo13 said:
Does this ROM boot to someone?
Click to expand...
Click to collapse
This Rom Boot, Only it takes a little while... You need to Wait for Some Mins... It's Due to ART...
FUSIONdev said:
WARNING
RIL seems to have some issues... on EVERY boot I got locked out from my SIM, requesting PUK CODE to unlock and set a new pin... so be careful.
I'm going to switch off pin code request.
KEYBOARD NOT WORKING ON FIRST BOOT... I'd to activate it on settings (not a problem)
WiFi WORKING.
CAMERA FREEZING THE PHONE
Click to expand...
Click to collapse
Camera Issue thanks for Pointing out i have update OP Also... You Can Use Google Camera From Play Store if you Make it till there
ikaster17 said:
Yes It will be having those issues... and yeah i understand your issue Especially if you have a sim code lock on your phone it might get a puk code so please dont try it with a pin code...
as for the reboot issue i dont understand it, i got the phone to run used it for half hour i got lucky but after that it rebooted again but for the time being it was really fast smooth and Project Volta FTW (Y)
Click to expand...
Click to collapse
The rom is ****ing awesome. As it's the first build, I'm really impressed of it.
Runs smooth, only the dialer app seems laggy.
Camera doesn't work neither with third party, so it's something hal related. (I tried Snap Camera and Google Camera... "impossible to connect camera".)
EXTERNAL SD is not mounting.
Here an early benchmark:
Weird issue: if you enable on developer settings "quick boot mode", the shutdown menu doesn't work
LOL...
just a minor issue, but I report it
Well That Means Some Hal Related Issue is There, and Well Good To Know There are minor Quinks to be fixed and it would become Soon Usable for Many People Great... and i personally thank you for testing this properly... i'll try to get all these errors notified to Nameless team if i can so that their next bulild on their original thread would be a much greater one
Thanks to Nameless for all the Great Work
Ok first boot is slower. I'm in boot from more than 20 mins. Is It normal?
ikaster17 said:
Well That Means Some Hal Related Issue is There, and Well Good To Know There are minor Quinks to be fixed and it would become Soon Usable for Many People Great... and i personally thank you for testing this properly... i'll try to get all these errors notified to Nameless team if i can so that their next bulild on their original thread would be a much greater one
Thanks to Nameless for all the Great Work
Click to expand...
Click to collapse
I'm reeaaaaaally impressed by your work. THANK YOU for porting lollipop so early to us!
I'm recording a quick video of the rom...:silly:
mimmo13 said:
Ok first boot is slower. I'm in boot from more than 20 mins. Is It normal?
Click to expand...
Click to collapse
Uhh did you have the latest twrp? Did you have stock touchwiz 4.4.2? and if you were on any other rom did you at first wipe everything before flashing this rom?
I'm sorry, My mistake. I'm on carbonrom and With cwm recovery.
mimmo13 said:
I'm sorry, My mistake. I'm on carbonrom and With cwm recovery.
Click to expand...
Click to collapse
Wipe System, Cache, Dalvik and data of rom.... I Tried with TWRP so twrp would be a better choice for flashing the 5.0 rom... follow the instructions from the OP
{
"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"
}
Welcome everyone to Pure N5 Rom support thread. In this topic you are free to share your experience , report bugs , request features , basically anything related to the ROM.
This is one of the best roms ever made , thanks to @malbert16442 :good:
Current bugs
-Videos not working on browser : This is already fixed in V6.5.
-Air command
-S note
-Screen modes not working
Useful files
-LP bootloaders : here
-LP modems : here
Mods
-All mods are here
Frequently asked questions
- Can you add some mods to the rom ?
>No , Malbert want to keep the rom clean , it's a "Pure" rom.
- Can i dirty flash the rom while updating ?
>Do it at your own risk , but if you have issues clean flash and test again before reporting.
-Is this rom stable ?
>This rom is more than stable , one of the best you can get.
-I have youtube lag , how to fix it ?
>Honestly i never had this issue , but if you are facing it change your model name in build.prop to "G903F".
Thread will be updated with the common bugs , and mods available
First
Sent from my SM-N920C using Tapatalk
S note. Action memo, air command bugs in pure note.. others OK and very smooth . . So I changed to deathnote ...
Any solution for this.. thanks. .
Xposed link any.. ?
DeeJaa said:
S note. Action memo, air command bugs in pure note.. others OK and very smooth . . So I changed to deathnote ...
Any solution for this.. thanks. .
Xposed link any.. ?
Click to expand...
Click to collapse
You can use the last Xposed V80 by wanam , they work very well
Sent from my SM-G900F using XDA Free mobile app
Action memo, so note, aircommand, browser problem. . Any solution. .?
Thanks. .
Waiting for two roms ..
One is pure note other is deathnote. .
Both have few bugs in new version. .
DeeJaa said:
Action memo, so note, aircommand, browser problem. . Any solution. .?
Thanks. .
Waiting for two roms ..
One is pure note other is deathnote. .
Both have few bugs in new version. .
Click to expand...
Click to collapse
List of bugs updated.
6.5 is coming soon , malbert is rebasing the rom so stay tuned
Sent from my SM-G900F using XDA Free mobile app
This ROM is amazing I use this ROM in my s5.
U can port this ROM for one plus x bcoz I have also a one plus x or give guide for port to this ROM for one plus x
@sh3nd0 Look do a fresh start. Flash a stock rom , flash philz recovery and flash supersu.zip , then reboot install supersu from play store. Boot into recovery and flash the rom it should work
Soufiansky said:
@sh3nd0 Look do a fresh start. Flash a stock rom , flash philz recovery and flash supersu.zip , then reboot install supersu from play store. Boot into recovery and flash the rom it should work
Click to expand...
Click to collapse
Hi brother Soufiansky .. I couldn't flash this ROM without having issues so I tried using the S5 Revolution v5.3 and it flashed with no issues and without even flashing any kernels. I'm running it on my phone atm. Maybe I will just wait for the new update and try to flash it again. I really don't know why it does that but works on Revolution v5.3.
sh3nd0 said:
Hi brother Soufiansky .. I couldn't flash this ROM without having issues so I tried using the S5 Revolution v5.3 and it flashed with no issues and without even flashing any kernels. I'm running it on my phone atm. Maybe I will just wait for the new update and try to flash it again. I really don't know why it does that but works on Revolution v5.3.
Click to expand...
Click to collapse
Maybe corrupted file ? A bad download i guess..Retry when V6.5 is available
Soufiansky said:
Maybe corrupted file ? A bad download i guess..Retry when V6.5 is available
Click to expand...
Click to collapse
Ahh maybe, I just hope it's a bad download, I also feel that it's something to do with my phone. Like it's weird that I can't root it even though how many times I tried, (this will will become off topic so i'll stop) Yeah I'll just wait for the 6.5 Btw, can I PM you and ask you something?
sh3nd0 said:
Ahh maybe, I just hope it's a bad download, I also feel that it's something to do with my phone. Like it's weird that I can't root it even though how many times I tried, (this will will become off topic so i'll stop) Yeah I'll just wait for the 6.5 Btw, can I PM you and ask you something?
Click to expand...
Click to collapse
It's not Off-topic at all this is a support thread feel free to talk about all your issues
You can ask me here , but ok you can pm me if you want.
Soufiansky said:
It's not Off-topic at all this is a support thread feel free to talk about all your issues
You can ask me here , but ok you can pm me if you want.
Click to expand...
Click to collapse
Ohh this is not the thread I was following earlier .. Anyway, I'm so confused about this G900L and G900F flashing. Like I have both devices and some other ROMs works on the other which won't work on the other. On my G900L, the issue is I reflashed stock latest firmware, then root CF root and TWRP 3.0.0.0 which is everyone good, but then flashing Revolution v5.3 and Tesltra won't let me boot because of kernel Issue so I need to flash hispasian kernel v7 to make it work but then the issue will be no Wifi. so I flashed Wifi Fix to fix the issue. Now, with Revolution 5.3, the camera won't turn on and just says Camera failed. I already wipe everything and also in camera settings i also wiped still the same. Now on Telstra, the issue is sometimes the Camera just turns black with the UI above and below, I need to reboot the phone or wait for couple of mins or hours to make it work again. I already tried reflashing several times and wiping but the issue persist. I don't know what I did wrong. I followed everything correctly and downloaded the files correctly.
sh3nd0 said:
Ohh this is not the thread I was following earlier .. Anyway, I'm so confused about this G900L and G900F flashing. Like I have both devices and some other ROMs works on the other which won't work on the other. On my G900L, the issue is I reflashed stock latest firmware, then root CF root and TWRP 3.0.0.0 which is everyone good, but then flashing Revolution v5.3 and Tesltra won't let me boot because of kernel Issue so I need to flash hispasian kernel v7 to make it work but then the issue will be no Wifi. so I flashed Wifi Fix to fix the issue. Now, with Revolution 5.3, the camera won't turn on and just says Camera failed. I already wipe everything and also in camera settings i also wiped still the same. Now on Telstra, the issue is sometimes the Camera just turns black with the UI above and below, I need to reboot the phone or wait for couple of mins or hours to make it work again. I already tried reflashing several times and wiping but the issue persist. I don't know what I did wrong. I followed everything correctly and downloaded the files correctly.
Click to expand...
Click to collapse
Yeah for the camera there is a flashable .zip to fix it , you know G900L always have issues because it does not have a kernel to boot 5.1.1 roms , a guy this week came to me with the same issue , so its not just you all korean S5 suffers from this
Soufiansky said:
Yeah for the camera there is a flashable .zip to fix it , you know G900L always have issues because it does not have a kernel to boot 5.1.1 roms , a guy this week came to me with the same issue , so its not just you all korean S5 suffers from this
Click to expand...
Click to collapse
Yeah that would really work, I just have to find that flashable zip.. I already found the wifi fix, if only I could get the fix for camera then it will all be good for the 900L , for now I'm on stock firmware on my 900L because the camera bug is really annoying and I can't capture on the spot moments because sometimes I have to restart my phone just to take a picture..
sh3nd0 said:
Yeah that would really work, I just have to find that flashable zip.. I already found the wifi fix, if only I could get the fix for camera then it will all be good for the 900L , for now I'm on stock firmware on my 900L because the camera bug is really annoying and I can't capture on the spot moments because sometimes I have to restart my phone just to take a picture..
Click to expand...
Click to collapse
The camera fix .zip is on TW revolution thread , look for it you will find it
Soufiansky said:
The camera fix .zip is on TW revolution thread , look for it you will find it
Click to expand...
Click to collapse
I found the Hespasian Kernel v7 with CameraLibs fix but it won't boot the ROM. Error says It couldn't BOOT. XD so maybe that camera lib fix is only for the other variant except Korean variants.
sh3nd0 said:
I found the Hespasian Kernel v7 with CameraLibs fix but it won't boot the ROM. Error says It couldn't BOOT. XD so maybe that camera lib fix is only for the other variant except Korean variants.
Click to expand...
Click to collapse
Damn this is why you should always buy the international variant...
Malbert's kernel is available ! :thumbup:
Sent from my S5 on steroids.
Soufiansky said:
Damn this is why you should always buy the international variant...
Click to expand...
Click to collapse
I guess I have to use my G900F then.. Though I don't quiet get it on why the DarthRom won't boot on my device but the Revolution ROM works well.
First I'm not the original post, and my English is not very wll,so plz be nice? here is the original post link
https://m.weibo.cn/detail/4292884486628928
And here is download link, injoy it
https://mega.nz/#F!ZjJ3iSZR!23Niltn4uLsOK5uRB_AwtQ
This google camera I shared, it support pixel3 night sight. You guys should try it it's so awesome
https://mega.nz/#!FnwmwKbD!FjM8EOnBE1oPDpJWRQbzO8StR-H2VYHw8LXsGCQAg8c
Installation instructions
- Download All the files
- install treble twrp recovery
- Take a backup
- Wipe cache
- Wipe dalvik cache
- wipe system
- wipe data
- flash vendor&PT firmware
- flash treble system.img (download your prefer os,if you don't know what it is then Google it )
- Reboot
- Enjoy!
Thank you catman
But whit out installation instructions , which order , i don't think any one dares. Flashing these files, no matter how ichy we all are trying it, a number of things could easily brik our phone's in a way there's no returning from, so if you could share all you know , it might help , in somebody dare trying it
Edit:
thx
But what is the meaning by this treble, I now I should google it, but these things we can already do, I mean OEM is easy installing, maybe in a different way, but what is new. Easier with treble?
Oh got it
https://www.google.com/amp/s/www.androidauthority.com/project-treble-818225/amp/
Nice if you like stock, but I don't and would never install it, if any aosp is out or custom ROMs available for my device, stock sucks big time.
spoonymoon said:
Thank you catman
But whit out installation instructions , which order , i don't think any one dares. Flashing these files, no matter how ichy we all are trying it, a number of things could easily brik our phone's in a way there's no returning from, so if you could share all you know , it might help , in somebody dare trying it
Click to expand...
Click to collapse
Already post it, and somebody did tried to flash it and it works great , only one problem it did not support Android P
I tried them and it works
Problems i faced.
Home button didnt work
charge led didnt work
couple of other things...
I got aosp, rr, pixelexperience working.
miffymiffy said:
I tried them and it works
Problems i faced.
Home button didnt work
charge led didnt work
couple of other things...
I got aosp, rr, pixelexperience working.
Click to expand...
Click to collapse
Sometimes **** happened but it just started and the original poster says it will keep updating so don't worry about it, BTW did you flash the official or homemade(???)
spoonymoon said:
Thank you catman
But whit out installation instructions , which order , i don't think any one dares. Flashing these files, no matter how ichy we all are trying it, a number of things could easily brik our phone's in a way there's no returning from, so if you could share all you know , it might help , in somebody dare trying it
Edit:
thx
But what is the meaning by this treble, I now I should google it, but these things we can already do, I mean OEM is easy installing, maybe in a different way, but what is new. Easier with treble?
Oh got it
https://www.google.com/amp/s/www.androidauthority.com/project-treble-818225/amp/
Nice if you like stock, but I don't and would never install it, if any aosp is out or custom ROMs available for my device, stock sucks big time.
Click to expand...
Click to collapse
I think the meaning Is about experience, It always good thing to experience new things,and There is alot of customazi os you can choose , like rr los axe aicp............
cartman56 said:
Sometimes **** happened but it just started and the original poster says it will keep updating so don't worry about it, BTW did you flash the official or homemade(???)
Click to expand...
Click to collapse
I did both. Suns one from the weibo link you posted is the one that works.
miffymiffy said:
I did both. Suns one from the weibo link you posted is the one that works.
Click to expand...
Click to collapse
All of them the home button didn't work?
Thx guys
Roms compatible with treble are links in weibo link posted by op?
I might not have looked probably
spoonymoon said:
Thx guys
Roms compatible with treble are links in weibo link posted by op?
I might not have looked probably
Click to expand...
Click to collapse
My English not taht well so I'm not sure what you mean, if you ask about who is the creater, i can tell you that isn't me, i just sharing his works that is all ? and the weibo link is straight to op?
I mean where is links to ROMs?
Its all Chinese... And I'm a bit Rusty there :laugh:
spoonymoon said:
Thx guys
Roms compatible with treble are links in weibo link posted by op?
I might not have looked probably
Click to expand...
Click to collapse
The roms that are compatible are GSI 8.1 roms. Others don't work.
How I got it to work;
Flash twrp with treble support. Reboot to recovery.
Flash both vendor zips, reboot to recovery
Flash U11 treble zip, reboot to recovery
Flash Oreo GSI system image of your liking from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Flash U11 selinux zip. Reboot.
It should boot.
Also, make sure you backup in twrp beforehand as if it's not what you want, you can just restore.
For pixelexperience, I had issues with gapps verification. It wouldn't let me get around it.
spoonymoon said:
I mean where is links to ROMs?
Its all Chinese... And I'm a bit Rusty there :laugh:
Click to expand...
Click to collapse
Search project treble inside XDA
miffymiffy said:
The roms that are compatible are GSI 8.1 roms. Others don't work.
How I got it to work;
Flash twrp with treble support. Reboot to recovery.
Flash both vendor zips, reboot to recovery
Flash U11 treble zip, reboot to recovery
Flash Oreo GSI system image of your liking from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Flash U11 selinux zip. Reboot.
It should boot.
Also, make sure you backup in twrp beforehand as if it's not what you want, you can just restore.
For pixelexperience, I had issues with gapps verification. It wouldn't let me get around it.
Click to expand...
Click to collapse
Thx miffy
Do you mean backup in New twrp, or old, i assume old backups won't work anymore?
And is it right what treple checker says that our device i a device with only one partition, thus only flash a images , with gapps?
And treple check says no treble support, but that is because i didn't flash zips yet surely
And which roms would you recommend?
Are all gsi images compatible with our htc u 11 ?
I'm on rr and not stock, magisk installed, does this matter?
Sorry for all the q but better sure than sorry
Don't work on HTC U11 Dual (A07)
vladislav1611 said:
Don't work on HTC U11 Dual (A07)
Click to expand...
Click to collapse
Having What problems
cartman56 said:
Having What problems
Click to expand...
Click to collapse
After flash the GSI image phone stays on HTC logo. Next problem is that phone can't recognise the internal storage when you try to do something on TWRP. Of course, I flashed the selunix zip on the last step. Tested PixelExpirience and AOSP, Android 8.1, A-only
vladislav1611 said:
After flash the GSI image phone stays on HTC logo. Next problem is that phone can't recognise the internal storage when you try to do something on TWRP. Of course, I flashed the selunix zip on the last step. Tested PixelExpirience and AOSP, Android 8.1, A-only
Click to expand...
Click to collapse
Did you do Clean flash before you flash GSI? and after the flash GSI you should do a FACTORY RESET
cartman56 said:
Did you do Clean flash before you flash GSI? and after the flash GSI you should do a FACTORY RESET
Click to expand...
Click to collapse
The first one i did but the second one no. Thanks. I'll try tomorrow again.
Is anybody interested/tried to install custom GSI Havoc OS ROM?
I browsed around and couldn't find anyone who tried it.
I found some instructions about it, but not sure if our device really supports this...
Links:
Official Havoc OS:https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-havoc-os-t3930030
P.S. am I the only one who still uses V20 in 2019?
this would be great @x86cpu you should definitely check this out!
i dont mind trying it out. But which file should i download?
So i tried to flash arm64-a file and I can see the android logo for sec then, the device boots into fastboot mode..
second screen is working or not?
luitAayush said:
second screen is working or not?
Click to expand...
Click to collapse
Probably not because It hasn't even been tested.
Deadmeat03 said:
i dont mind trying it out. But which file should i download?
So i tried to flash arm64-a file and I can see the android logo for sec then, the device boots into fastboot mode..
Click to expand...
Click to collapse
i95swervin said:
Officially, No the v20 doesn't support GSI's
Theoretically, Yes. I was speaking to a Dev for the device I am currently daily driving and he said that " los 16 is using a treble vendor so a system A GSI should work " I haven't tested this theory simply because I have a ARB1 H918 device and don't feel like bricking.
I am curious about it though.. So anyone on Lineage 16 feel like trying? lol. Or maybe @x86cpu could chime in on this matter.
P.S. I still use my v20 as a media device and still find daily use for it but not as a phone ATM in 2019.
Click to expand...
Click to collapse
Lineage 16 for the V20 doesn't use a Treble /vendor partition. This won't work until/unless that changes.
Hello!
Usually I mainly consult this forum to get unofficial builds of LineageOS or look for support when occasionly something goes wrong. Some time ago I wondered, why it has to be so annoying to install LineageOS (or most of the other custom ROMs). There have been several attempts to create a graphical installer for LineageOS (most famously this one) and some installers for specific ROMs like calyxos. But support for devices is rather limited and hard to extend.
So I decided to give it a try myself and create a new attempt to build a graphical installer for alternative Android ROMs.
Repository: https://github.com/openandroidinstaller-dev/openandroidinstaller
Features:- Graphical installer with instructions.
- onefile executable.
- adb, fastboot, heimdall and some drivers included.
- Works on Linux (mainly tested on Ubuntu 20.04), MacOS (not on ARM, M1, M2) and windows (you might need to install some drivers manually).
- some checks if the selected LineageOS image and recovery works for your device.
- Installation steps are based on config files to add support for new devices.
- written in python
Supported devices:- Currently, the alpha version mainly supports Google, Samsung, Fairphone and Sony devices, but should be fairly easy to extend to other devices.
Alpha version release download:https://github.com/openandroidinstaller-dev/openandroidinstaller/releases
How can you help?All kinds of feedback are useful! Let me know what you think in this thread.
If you have a unused device that supports LineageOS, perhaps you could try out this tool and report your results in this thread! I bought a bunch of different android devices, but more testing on all kinds of devices is needed and very welcome! Also testing the tool on different platforms (windows, macos, etc.) would be super helpful.
Note that:
- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.
- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.
- Read the repository's README for further details!
- This installer is not associated with official LineageOS.
Getting a new phone this week, will give it a shot
SigmundDroid said:
Getting a new phone this week, will give it a shot
Click to expand...
Click to collapse
Thanks a lot! I'm looking forward to your feedback!
What phone are you getting? I might be able to help you with support
FP3. Was hoping it'll arrive today... alas, didn't come, so probably I can check not before the weekend.
Great! I'll make sure, that there is support for the FairPhone 3 on the weekend, but note, that it hasn't been tested yet, since I don't have a FairPhone 3. So I'm super happy about any feedback I can get
If you have questions, let me know!
Devices that should work out of the box now:
VendorDevice NameCodeNameModelsStatusSamsungGalaxy A3 2017a3y17lteSM-A320FLtestedSamsungGalaxy A5 2016a5xelteSM-A510FtestedSamsungGalaxy S7herolteSM-G930FtestedSamsungGalaxy S9starlteunder developmentGooglePixel 3asargosargotestedSonyXperia ZyugaC6603testedSonyXperia Z3z3under developmentFairphoneFairphone 2FP2under developmentFairphoneFairphone 3FP3under developmentMotorolamoto g7 poweroceanunder development
In general, it should be pretty easy to use the tool for all kinds of Samsung, Pixel, Sony Xperia, Fairphone and Motorola devices. Let me know if you need help with your devices.
{
"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"
}
OK, it works with FP3! Awesome! Actually, that might become a nice little helper for flashing LOS!
Ran into some problems:
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Overall very good approach! Well, except for the lack of feedback (errors/progress from console). Is there any logging?
PS: Used it on Debian Bullseye with KDE.
PSPS: Perhaps an overview of the steps would fit in there as well (so one can see past, current and future steps)?
Awesome! Thanks for giving it a try!
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
Click to expand...
Click to collapse
Very good point!
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Click to expand...
Click to collapse
In the next release it will point to the official page. I wasn't aware that this page is not at all related to LOS and not so well perceived in the community as some of the devs pointed out to me. The check is done, to find out if there is an official release of LOS and then recommend the download. There might be a better way to guide users to find an appropriate image for their device, but that was simple.
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
Click to expand...
Click to collapse
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough and stopped after part 1. This should be easy to address by updating the config. It will be fixed in the next release.
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Click to expand...
Click to collapse
That's very true! I'm trying to figure out, what kind of feedback is appropriate to keep people informed, but not scare them. A progress bar for flashing is in the making. Optimally, the installer can also show images of what should be going on on the phone. But that will mostly rely on community contributions for phones I don't own.
Thanks a lot for the detailed feedback! I will try to address most of them in the next release, especially more information and feedback for the user.
PS: Are you using the FP3 as your daily driver now, or would you be open to test the installer again in a few weeks or so?
PPS: I'm thinking about moving away from LOS recovery all together and only support TWRP since it allows for much more automation. What are your thought on that?
__sterby__ said:
official release of LOS
Click to expand...
Click to collapse
Would that link do it?
https://download.lineageos.org/FP3
__sterby__ said:
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough
Click to expand...
Click to collapse
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
__sterby__ said:
what kind of feedback is appropriate to keep people informed, but not scare them
Click to expand...
Click to collapse
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
__sterby__ said:
using the FP3 as your daily driver now
Click to expand...
Click to collapse
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
__sterby__ said:
moving away from LOS recovery all together and only support TWRP
Click to expand...
Click to collapse
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
SigmundDroid said:
Would that link do it?
https://download.lineageos.org/FP3
Click to expand...
Click to collapse
Yes And probably also to the relevant TWRP page soon.
SigmundDroid said:
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
Click to expand...
Click to collapse
No, other phones also require this step. Since the fairphone 2 doesn't require it (as far as I know the bootloader is already unlocked), I assumed that could be similar for the Fairphone 3.
SigmundDroid said:
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Click to expand...
Click to collapse
Thanks for the suggestion, I'm working on an "advanced output mode" that lets you see all the terminal input and output.
SigmundDroid said:
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
Click to expand...
Click to collapse
yeah, I'm thinking about how to integrate this in a useful way. A bit more overview would be nice.
SigmundDroid said:
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
Click to expand...
Click to collapse
Perfect! Thanks a lot, I'm already working on a new release and hopefully there will be much more automation and more user information (and a fully working config for the fairphone 3). I keep you updated!
SigmundDroid said:
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Click to expand...
Click to collapse
So far, it works kind of okay with TWRP I would say, but I'm having weird issues on the Google Pixel with it and wasn't able to find anyone who might know anything about it. Using twrp commands in the adb shell seems to be not so common...
Either way, I would try to get away with just booting into TWRP, wiping and flashing from there. This is an approach that seems to work fine with A/B-partitioned phones as far as I can tell.
SigmundDroid said:
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
Click to expand...
Click to collapse
It's not on the short-term agenda. But definitely something I'm thinking about. I should probably put a proper roadmap on github
Soooo, now there is a new alpha Release
Release Alpha release v.0.2.1 · openandroidinstaller-dev/openandroidinstaller
This is an alpha release of the OpenAndroidInstaller. Linux, MacOS and Windows are supported, but the testing is mainly done on under Ubuntu 20.04. Note, that currently there is no support for ARM-...
github.com
This time mainly visual improvements and more automation. This is mainly achieved by switching recovery support completely to TWRP (currently only booted, only flashed on samsung devices).
There is now an option to get advanced output, printing commands run and terminal output in the tool. This is still early stage and needs a fair amount of improvements, but gives some more hints about whats going on.
Logs are written in the same directory you run the tool in.
...and support for quite some new devices!
@SigmundDroid : Now the support for the Fairphoen 3 should be fixed and TWRP should work A/B devices (tested with google pixel 3a). Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!
Just tried the 2nd version:
+ Nice, comes with log now, good!
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
PS: Shall I drop you the log somewhere?
SigmundDroid said:
Just tried the 2nd version:
Click to expand...
Click to collapse
Great! Thanks a lot!
SigmundDroid said:
+ Nice, comes with log now, good!
Click to expand...
Click to collapse
Thanks! Did you also try the "advanced output" feature?
SigmundDroid said:
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
Click to expand...
Click to collapse
That's a very good catch, I noticed an issue there. I followed this official tutorial from Fairphone: https://support.fairphone.com/hc/en-us/articles/360048646311-Manage-the-bootloader-of-your-FP3-FP3-
And they used `fastboot oem unlock`, which I noticed now doesn't even exist. I fixed it now.
SigmundDroid said:
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
Click to expand...
Click to collapse
Ah, right now, I just boot to TWRP recovery, not flash it for A/B devices, since I was not sure how to best do it for now (without potentially destroying stuff). For Samsung devices it will be flashed.
Do you think this is an issue in general? I might try to add it as a feature for power users, that can also handle the risk a bit better. What do you think?
SigmundDroid said:
PS: Shall I drop you the log somewhere?
Click to expand...
Click to collapse
For now, it's fine and I guess I know whats the issue.
I'm planning another release next week, probably mostly a bugfixing and user-interface release. I will post it here again
Hey there!
Today I released the Version v.0.3.0-alpha of the OpenAndroidInstaller with many improvements and newly supported devices!
The release includes 11 new devices (now 27 officially supported devices):
Motorola moto g7 power (ocean)
Motorola moto g5 (cedric)
Samsung Galaxy Note 9 (crownlte)
Samsung Galaxy Note 10 (d1)
oneplus 6
oneplus 6T
oneplus 7
oneplus 7 Pro
oneplus 7T
oneplus 7T Pro
OnePlus Nord N200
Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!
Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP
SigmundDroid said:
Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP
Click to expand...
Click to collapse
Great! Thanks a lot for testing again!
Looks like the thing is slowly moving to a more stable state. Maybe moving to beta next year
PS: Good point! In the next release I will try to make it clearer. At least you could not use the LOS recovery
__sterby__ said:
will try to make it clearer. At least you could not use the LOS recovery
Click to expand...
Click to collapse
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS
SigmundDroid said:
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS
Click to expand...
Click to collapse
Thanks a lot! Merry Christmas to you as well!
Hey everyone!
I did some work in the last weeks and now the OpenAndroidInstaller is available in alpha version 0.3.1, with improved user experience and newly supported devices.
New features:
new images to guide in the process
steps indicator header
remove step-progressbar and move the header to different column container to keep it attached to the top
pop-up box to explain custom recovery and OS images.
dialog to help finding the android or firmware version
5 New devices (now 32 officially supported devices):
Sony Xperia 10 (kirin)
Sony Xperia 10 Plus (mermaid)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ3 (akatsuki)
Sony Xperia XZ2 (akari)
If you're interested in trying out alternative ROMs on your device, now is the perfect time to give OpenAndroidInstaller a try. Over the holiday season, you might to play with OpenAndroidInstaller on your old or new devices and see what it can do.
Thank you for supporting open source software and giving OpenAndroidInstaller a chance. Happy holidays and happy installing!
PS: There is a brand new, shareable website now! https://openandroidinstaller.org/
Hey you all! I have been quiet for while here, but the work continued!
Now I'm happy to release the first beta release of the OpenAndroidInstaller.
The major new feature is the option to install addons like GApps, MicroG or F-droid with the Installer. Also there are now 52 officially supported devices and more to come!
If you want to try it, I'm happy about all kind of feedback (positive and negative). Have a great day and happy flashing!
Release: https://github.com/openandroidinstaller-dev/openandroidinstaller/releases/tag/v0.4.0-beta
Download: https://openandroidinstaller.org/download.html