This is my first thread of this kind, so bear with me if I'm not formatting it quite right.
I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware. At this point, this is completely untested, as I do not currently have my tablet in a state where I can test it (I'm working on this).
Here is a link to the recovery image on my Google Drive:
twrp-gts7lwifi_BUC6.img
drive.google.com
I will post it to somewhere better once it has been verified as working.
My work was based on what Ian Macdonald did here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
My source code is available here:
TWRP Source
Kernel source
Device tree
I'm finishing a write-up of what I did to create this image now. I'll post a link to that on this thread later today.
Here is my write-up on how I did this.
tales_of_hackery/building_twrp.md at master · bxlentpartyon/tales_of_hackery
Contribute to bxlentpartyon/tales_of_hackery development by creating an account on GitHub.
github.com
I tried to make it as complete as possible, but quite a bit of work went into this, so I'm sure I've left out some details. If you attempt this yourself, please let me know if/where you run into issues and I'll update the document accordingly.
Note that, once I have confirmation that my build process is sound, I'll be happy to try and perform builds for other devices in this family as well, as long as kernel sources are available.
I've submitted a request to Samsung for the sources for the latest kernel for my device (T870XXU2BUF5). I'm not expecting a response until after the weekend, but I _think_ that they're obligated to provide the sources upon request.
bxlentpartyon said:
Note that, once I have confirmation that my build process is sound, I'll be happy to try and perform builds for other devices in this family as well, as long as kernel sources are available.
I've submitted a request to Samsung for the sources for the latest kernel for my device (T870XXU2BUF5). I'm not expecting a response until after the weekend, but I _think_ that they're obligated to provide the sources upon request.
Click to expand...
Click to collapse
when I requested the sources for my T970 it took over a month and I requested it 3 times.
bxlentpartyon said:
This is my first thread of this kind, so bear with me if I'm not formatting it quite right.
I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware. At this point, this is completely untested, as I do not currently have my tablet in a state where I can test it (I'm working on this).
Here is a link to the recovery image on my Google Drive:
twrp-gts7lwifi_BUC6.img
drive.google.com
I will post it to somewhere better once it has been verified as working.
My work was based on what Ian Macdonald did here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
My source code is available here:
TWRP Source
Kernel source
Device tree
I'm finishing a write-up of what I did to create this image now. I'll post a link to that on this thread later today.
Click to expand...
Click to collapse
I doubt that it'll work, I tried it a while ago (I didn't test it myself) with added firmware files, updated kernel and device tree stuff and I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue, your commits are mostly updates for the twrp a11 source and new kernel source, so the differrences from my build and yours are that I have a more custom and upstreamed kernel with firmware but you used the a11 twrp source (which manifest wasn't available for me when I made it).
Appreciate the effort, we do need devs here. But whats the actual point of twrp, when we have ZERO roms to flash.
Bushcat said:
I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue
Click to expand...
Click to collapse
Not sure what issue you're talking about here. The guy whose process I copied didn't seem to have problems, or at least not many significant ones.
If you did this same thing with a "very custom" kernel and were not successful, my instinct would be that the kernel was "too custom." The whole idea behind my method of customizing my kernel was to minimize the differences between what I built, and the kernel that Samsung shipped, which is known to be functional.
bs3pro said:
Appreciate the effort, we do need devs here. But whats the actual point of twrp, when we have ZERO roms to flash.
Click to expand...
Click to collapse
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job
bxlentpartyon said:
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job
Click to expand...
Click to collapse
Keep up the good work! Not complaining, just wish we had a couple devs making aosp. Thanks
bxlentpartyon said:
Not sure what issue you're talking about here. The guy whose process I copied didn't seem to have problems, or at least not many significant ones.
If you did this same thing with a "very custom" kernel and were not successful, my instinct would be that the kernel was "too custom." The whole idea behind my method of customizing my kernel was to minimize the differences between what I built, and the kernel that Samsung shipped, which is known to be functional.
Click to expand...
Click to collapse
There have been many people testing ianmacds build and trying to build twrp for the tab s7 but everybody had this blue screen issue which made the twrp screen unusable but you can use twrp from usb.
Ianmacd and other users tried it with a slightly modified kernel from samsungs source, I wanted to try a differrent kernel because samsungs kernel source can be ****ty sometimes so I tried an upstreamed lineageos samsung sm8250 common kernel (which I'm also using for my galaxy tab s7+ TWRP and PBRP builds and it's working well there) but it had the same issue. The Tab S7+ also has a small display issue in twrp but it's still usable, when hitting some ubttons in twrp you can sometimes see a small flickering stripe at the top. In twrp it's hard to notice but in PBRP this issue was very annoying because it happenned much mnore often and longer, it got very bad when you turn off and on the display in recovery, I was able to lower the glitches with some screen values like timeout but I wasn't able to fix this issue.
{
"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"
}
bxlentpartyon said:
I did this partially as a learning exercise, to familiarize myself with the Android build process. I'm still obviously fairly new to the Android scene, but the biggest piece of TWRP that I hoped to utilize was the backup/restore functionality.
Eventually I'm planning to try and install openSuSE on my tablet natively, and I wanted to be sure that I have solid backups, for when I eventually screw up and trash my device. I've learned through talking with jhill a bit that I'll probably get by just fine with just the stock firmware available to re-flash, but I wasn't entirely positive about that when I started working on this, and I figured I'd already burned the time building the kernel, so I might as well finish the job
Click to expand...
Click to collapse
Welcome to the tab s7/+ dev community, I'm searching for more devs and custom stuff for our devices but sadly we aren't many, I've started trying to make Lineageos for the tab s7+ a while ago (my first from the ground up tree but I maintain ResurrectionRemix official for the OnePlus 6T since january) and I got further in small steps but since I'm stuck at this kernel issue since a month (I don't have much time atm but I'll try harder soon), the kernel doesn't want to load the fstab, I tried los17 and 18, asked many devs about this issue (jimbok77 mentioned a los18 init issue for the galaxy 20 series), this is my first device with dynamic partitions and my last samsung device was a samsung galaxy s5 mini exynos G800F, you can find more about my progress here Interest thread s7+ Lineage os and in the tab s7/+ development telegram chat, and you can find testers at telegram chat by ianmacd.
My plans are to make a working lineageos and then postmarket os, ubuntu touch and jing os.
Mod Edit: TG links removed as per XDA Telegram Chat Rules.
Bushcat said:
There have been many people testing ianmacds build and trying to build twrp for the tab s7 but everybody had this blue screen issue which made the twrp screen unusable but you can use twrp from usb.
Ianmacd and other users tried it with a slightly modified kernel from samsungs source
Click to expand...
Click to collapse
Thanks for the explanation. From what I understood, nobody had really attempted a build for the T870 yet. I was unaware that it has been tried, but nobody has gotten it working. Judging from the fact that the TWRP source has been shown to be functional on the S7+, I'd assume that this is still a kernel issue, but knowing that certainly doesn't help anybody find what the actual issue is, haha.
Bushcat said:
Welcome to the tab s7/+ dev community, I'm searching for more devs and custom stuff for our devices but sadly we aren't many, I've started trying to make Lineageos for the tab s7+ a while ago (my first from the ground up tree but I maintain ResurrectionRemix official for the OnePlus 6T since january) and I got further in small steps but since I'm stuck at this kernel issue since a month (I don't have much time atm but I'll try harder soon), the kernel doesn't want to load the fstab, I tried los17 and 18, asked many devs about this issue (jimbok77 mentioned a los18 init issue for the galaxy 20 series), this is my first device with dynamic partitions and my last samsung device was a samsung galaxy s5 mini exynos G800F, you can find more about my progress here Interest thread s7+ Lineage os and in the tab s7/+ development telegram chat, and you can find testers at telegram chat by ianmacd.
My plans are to make a working lineageos and then postmarket os, ubuntu touch and jing os.
Click to expand...
Click to collapse
The "custom ROMs" side of things is something I don't really have any knowledge about. To be honest, I don't have a ton of interest in going down that road, at least at the moment, as I don't really understand what benefits I would get from a custom ROM. From my point of view, I'm much more interested in getting "plain old Linux" running on the device, as that makes it far more powerful and useful, IMO.
A big part of what I want to do with my device is to run gaming console emulators, and the whole added layer of complexity of needing to write a Java wrapper around an already-functional C program just to get it to run doesn't really appeal to me. Again, this could all be ignorance of the real possibilities on my part, but I'm just trying to give you an idea of where I'm coming from.
Thanks again for the explanation of the current state of TWRP, and the introduction to some of the rest of what's going on out there!
Bushcat said:
I doubt that it'll work, I tried it a while ago (I didn't test it myself) with added firmware files, updated kernel and device tree stuff and I used a very custom upstreamed samsung sm8250 common kernel which I had good experience with but it had the same issue
Click to expand...
Click to collapse
Arrrgh, you were right. I finally spent the time to fully root my tablet and get my TWRP build installed, but the end result was exactly like the screen pic you posted. You can see the top of the screen, but everything else is just blue. Being new to TWRP, I didn't know how to pull the log at the time to see if there were any obvious errors in it, and I've already flashed back to stock recovery at this point.
I'll give this another go sometime later this week, or over the weekend, and see if I can learn anything else.
If anyone has some basic TWRP debugging tips that would be helpful. From what I've seen the number one option is:
abd pull /tmp/recovery.log
But I'm not sure if that is still valid, or if there are other things that can be done.
Scratch some of what I said above. I determined that:
/cache/recovery/last_kernel.log
Contains the log buffer from TWRP booting my custom kernel, and:
/cache/recovery/last_kmsg*
Contain log buffers from regular kernel boots. I'm combing through these looking for any interesting differences now, but there's obviously a lot to comb through, and it takes some effort to determine what is expected to be different due to config differences, and what might actually be important.
At least I've got something interesting to stare at for a little while.
bxlentpartyon said:
Scratch some of what I said above. I determined that:
/cache/recovery/last_kernel.log
Contains the log buffer from TWRP booting my custom kernel, and:
/cache/recovery/last_kmsg*
Contain log buffers from regular kernel boots. I'm combing through these looking for any interesting differences now, but there's obviously a lot to comb through, and it takes some effort to determine what is expected to be different due to config differences, and what might actually be important.
At least I've got something interesting to stare at for a little while.
Click to expand...
Click to collapse
Anything you need help with? Unfortunately I'm only a web developer so I don't think my Pyhton, CSS, or HTML knowledge would help much in the development of custom recovery but if there's anything we can do I'm happy to contribute.
bxlentpartyon said:
I'd assume that this is still a kernel issue, but knowing that certainly doesn't help anybody find what the actual issue is, haha.
Click to expand...
Click to collapse
I put a lot of effort and tried hard to find out the issue source. Mixed and compiled many different dtbos but every attempt gave me exactly the same result. I used almost stock sammy kernel and my highly modified Amnesty build.
Click to expand...
Click to collapse
Btw I am currently using Linux Deploy with Sparkle overlay for graphics acceleration.
Kinda convenient choice if u do not mind chroot environment.
Jerry12798 said:
Anything you need help with? Unfortunately I'm only a web developer so I don't think my Pyhton, CSS, or HTML knowledge would help much in the development of custom recovery but if there's anything we can do I'm happy to contribute.
Click to expand...
Click to collapse
Unfortunately I barely know enough about Android/TWRP to even know what to ask for help with, haha. If you want to pitch in, I'd encourage you to get your feet wet and try to run a TWRP build and see if you can reach the same point that others have gotten to (i.e. blue screen). You can use the guide I posted above to attempt that. I'll be glad to help with any questions you have along the way.
From there, it seems like it's basically anybody's game at this point. Apply whatever knowledge you have to see if you can make progress on the current issue!
bxlentpartyon said:
Unfortunately I barely know enough about Android/TWRP to even know what to ask for help with, haha. If you want to pitch in, I'd encourage you to get your feet wet and try to run a TWRP build and see if you can reach the same point that others have gotten to (i.e. blue screen). You can use the guide I posted above to attempt that. I'll be glad to help with any questions you have along the way.
From there, it seems like it's basically anybody's game at this point. Apply whatever knowledge you have to see if you can make progress on the current issue!
Click to expand...
Click to collapse
Yea I've tried it but blue screened too. I know a few different devices I've messed around with before has had weird screen issues (flickering, off colors, etc) in TWRP.. I don't know if they had the sames issue we are or not but it seems probable.
I put a lot of effort and tried hard to find out the issue source. Mixed and compiled many different dtbos but every attempt gave me exactly the same result. I used almost stock sammy kernel and my highly modified Amnesty build.
Click to expand...
Click to collapse
At this point, I really want to think that the issue has something to do with how we're setting up/driving the display. I'm leaning away from it being an outright problem with the kernel (and definitely don't think it's the device tree), but I do wonder if the information in the kernel logs might help us find the problem.
In comparing logs from stock recovery (where video obviously works) with logs from TWRP, I can see some notably different values getting used for initial backlight/brightness settings, as well as some other differences related to the display.
Now, I don't know that the differences I've spotted actually matter, but the display in the T870 is obviously a different model than the larger one in the T976, where TWRP is functional, so it's certainly something to check at least. For now that's all I've really got, but I'll be digging into this more soon.
Related
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
DemonGloom said:
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
Click to expand...
Click to collapse
As you should remember, Arlic was the only dev of p7320 but unfortunately he disapeared suddenly...
Anyway, I am still satisfied on his rom:
http://forum.xda-developers.com/showthread.php?t=1923371
btw. there are some November's releases of stock roms at sammobile.
It is still 4.0.4 but I wonder if it comtain any improvements over previous builds?
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
pax0r said:
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
Click to expand...
Click to collapse
p7320 - SoC Qualcomm (2x1.5 Ghz, Adreno 220)
p7300/p7310 - Tegra 2
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
I have just made a new kernel, but it is based on ICS.
You can get it here:
Downloads:
https://sourceforge.net/projects/kernel-p7320t-ics/files/
Source:
https://github.com/CL0SeY/kernel_P7320T_ICS
The features so far are:
Interactive CPU governor available for selection (was left out of the stock kernel for some reason). If you want to enable this governer you will need to firstly get ROOT for the tablet, and then install some app to control it, e.g. Voltage Control. If you enable this, it should give you a more responsive tablet, compared to using the default ondemand governer.
Max CPU frequency "UNICPU" bumped to 1512MHz from 1242MHz. This is the maximum frequency that you will see the tablet sitting on at times. If you are concerned about battery usage you can tweak this the maximum frequency value down using using Voltage Control or other apps.
USB charging and notification, as per glitschi667 / pershoot's patch, which was previously in a honeycomb custom kernel: http://forum.xda-developers.com/showthread.php?t=1569122 . The tablet will show as charging when plugged into a PC with enough power, whereas previously you would see the red X over the battery icon.
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
janla said:
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
Click to expand...
Click to collapse
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
CL0SeY said:
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
Click to expand...
Click to collapse
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
CL0SeY said:
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
Click to expand...
Click to collapse
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip (https://drive.google.com/file/d/0B48JIYNc4wvsT2txZS16WGV0MUE/edit?usp=sharing)
GAPPS required: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Procedure:
(This has only been tested moving from a STOCK ICS ROM. Unsure if it will work for Arlic's ROM. If it all goes wrong try from a stock ICS ROM.)
Ensure you have a CWM recovery installed, see http://forum.xda-developers.com/showthread.php?t=1569122
* Copy the zips to your tablet
* Reboot into recovery
* WIPE data
* Install aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
* Install gapps-jb-20121011-signed.zip
* Reboot and enjoy!
Known working:
* Display
* 3G/4G/LTE
* Wifi
* Sound (headphones, speakers)
Known issues:
* Google play store seems to lose its network connection after a while. This seems to be a common problem amongst other ROMs.
* Plenty that we don't know about yet
{
"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"
}
CL0SeY said:
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7520t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
Click to expand...
Click to collapse
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Definitely you should start new tread.
There is a typo in the filename of the rom?
should be p7320 instead p7520.
janla said:
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Click to expand...
Click to collapse
Do you mean about going back to stock after trying it out? I have tried it myself going back to the sammobile OTA image fine.
janla said:
There is a typo in the filename of the rom?
should be p7320 instead p7520.
Click to expand...
Click to collapse
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
CL0SeY said:
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
Click to expand...
Click to collapse
And the file is now named correctly
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
CL0SeY said:
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
Click to expand...
Click to collapse
OK guys, here's a nice little nugget for the weekend.
I've followed the instructions for making a CM10 ROM for the i957 above, and simply changed the mount point and have it working on the P7320.
The ROM (cm-10-20131130-UNOFFICIAL-p7320.zip) should appear in this folder as soon: https://drive.google.com/folderview?id=0B48JIYNc4wvscVpIZkRKZWd4RmM&usp=sharing
I've tested wifi, 4g, and that is about it. Once again flash at your own risk yada yada yada...
MASSIVE thanks to @nrvate for the guide! I would like to see if we can do something potentially with the upgrade scripts to make them generic. between the p7320 and i957. I suspect this ROM will work fine on the i957 with the reverse fix (ie. make it use mm block 26 instead of 28).
Also I will make a proper thread for this work soon enough...
thanks a lot for participating CL0SeY
It is great that we are moving somewhere ...
I have wish to start working on cooking but building house and 2 little children are taking all of my time (with full right
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
CL0SeY said:
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
Click to expand...
Click to collapse
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
_kankea said:
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
Same here, thanks for giving it a go and the feedback . Also, the auto brightness seems to be very unpredictable, I think it's something wrong with the values coming back from the sensor.
I've been bashing my head against a wall trying to get us up to at least cm10.1 without too much luck so far. Compiling is quite a slow process even on an SSD, so it can take a while between fixing build errors.
_kankea said:
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
CL0SeY said:
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
Click to expand...
Click to collapse
Yeah, camera works now \o/
I read from the i957-thread that the boot animation problem is a known issue...
The vibration seems to be a bit powerless...
But still, I have waited for ages that anything newer than ICS appears for this device. Great job, CL0SeY! :good:
EDIT:
Mobile hotspot function (tethering) does not seem to work...
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
jedld said:
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
Click to expand...
Click to collapse
How is this coming along. I see you've been working on it right through last night. Any progress with the RIL?
TopTongueBarry said:
How is this coming along. I see you've been working on it right through last night. Any progress with the RIL?
Click to expand...
Click to collapse
I got rild working, now trying to get wifi up.
Current OMNIRom status for the SM-T285.
1. Phone/LTE Services - OK
2. Graphics (hwcomposer/gralloc) - OK with bugs
3. Wifi - Still need to fix wpa_supplicant issues OK (10/20/2016)
4. Bluetooth - Broken, stock uses a custom bluedroid lib, will need to reverse engineer bluetooth commands
5. Audio - OK
6. Accelerometer - OK
7. GPS - Not Tested
8. USB Services (adb, tethering) - OK
9. Camera - Broken
Will post ROM once I sort these issues out.
Looking forward to this. :good:
I've just switch to porting OMNIRom 6.0 to the SM-T285, screenshots here:
SM-T285 running marshmallow
ril got broken when moving from 5.1.1 unfortunately, so working to get it back on. However there are now no more graphical bugs, the SM-T285 actually runs impressively on the Marshmallow
A release should be happening this week, I hope I beat samsung to Marshmallow with this device
jedld said:
I've just switch to porting OMNIRom 6.0 to the SM-T285, screenshots here:
SM-T285 running marshmallow
ril got broken when moving from 5.1.1 unfortunately, so working to get it back on. However there are now no more graphical bugs, the SM-T285 actually runs impressively on the Marshmallow
A release should be happening this week, I hope I beat samsung to Marshmallow with this device
Click to expand...
Click to collapse
Awesome.
Just curious. Will safety net pass?
venomrat said:
Awesome.
Just curious. Will safety net pass?
Click to expand...
Click to collapse
Haven't tried, however I am led to believe that safetynet fails in general for all custom roms that is not based on stock like CyanogenMod or Omni.
Hello there, your work looks very good so far! Its good to see that someone finally takes care of the Tab A 7.0
Are u planning a T280 Release too?
Greetings
jedld said:
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
Click to expand...
Click to collapse
Quick question, I have very little or no experience about porting a rom. How do you do it and what applications and guide do you use to port a rom? I have a SM-T350 and I'm going to port Cyanogenmod 14. Thanks for the reply, in advance.
ParadoXGodzillA said:
Quick question, I have very little or no experience about porting a rom. How do you do it and what applications and guide do you use to port a rom? I have a SM-T350 and I'm going to port Cyanogenmod 14. Thanks for the reply, in advance.
Click to expand...
Click to collapse
I don not personally have an all in one guide that I am following. There are various sites that provide bits and pieces of it, for CM, they have their own porting guide here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Unfortunately, the guide above is only good for creating an initial setup. To be able to make the rom work on your device, you are probably going to need a bit more, sites like android open source provides a brief overview of how the bits and pieces work at a low level:
https://source.android.com/devices/index.html
I also had to deal with SELinux, and this is the part where there is a lot of lacking tutorials.
Next is mostly device specific. The best case scenario is if your device already has a CM port available (previous version) or if a device with similar hardware has it. If the SM-T350 already has a CM port available somewhere then your job is going to be a bit easier. If not it is going to extremely hard depending on what sort of hardware you are dealing with. There are some hardware manufactures that provide good support like Qualcomm and those that aren't so good at it Spreadtrum *cough*. In my own experience with the SM-T285 there aren't many devices with CM around that sport the same hardware, the best I got going was a Samsung Galaxy Core (core33g) CM port that I found in github after looking really hard. The real challenge is figuring out how things work and what "changes" the specific manufacture did to existing aosp. There are times where you are forced to use the stock (proprietary) libs and attempt to shim(patch functions) them to work.
I already have experience compiling CM from source since I also have a Nexus 5 which has pretty good support. I also have several years experience as an Android Developer as well as prior dev experiences related to Java/C/C++. You should also be familiar with the languages used in building android namely C/C++, Java as well various scripts as well as dealing with linux as there would be times when you need to make modifications to backport/forwardport functions used by proprietary libraries.
jedld said:
I don not personally have an all in one guide that I am following. There are various sites that provide bits and pieces of it, for CM, they have their own porting guide here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Unfortunately, the guide above is only good for creating an initial setup. To be able to make the rom work on your device, you are probably going to need a bit more, sites like android open source provides a brief overview of how the bits and pieces work at a low level:
https://source.android.com/devices/index.html
I also had to deal with SELinux, and this is the part where there is a lot of lacking tutorials.
Next is mostly device specific. The best case scenario is if your device already has a CM port available (previous version) or if a device with similar hardware has it. If the SM-T350 already has a CM port available somewhere then your job is going to be a bit easier. If not it is going to extremely hard depending on what sort of hardware you are dealing with. There are some hardware manufactures that provide good support like Qualcomm and those that aren't so good at it Spreadtrum *cough*. In my own experience with the SM-T285 there aren't many devices with CM around that sport the same hardware, the best I got going was a Samsung Galaxy Core (core33g) CM port that I found in github after looking really hard. The real challenge is figuring out how things work and what "changes" the specific manufacture did to existing aosp. There are times where you are forced to use the stock (proprietary) libs and attempt to shim(patch functions) them to work.
I already have experience compiling CM from source since I also have a Nexus 5 which has pretty good support. I also have several years experience as an Android Developer as well as prior dev experiences related to Java/C/C++. You should also be familiar with the languages used in building android namely C/C++, Java as well various scripts as well as dealing with linux as there would be times when you need to make modifications to backport/forwardport functions used by proprietary libraries.
Click to expand...
Click to collapse
Thanks for the info by the way. Can you add me on XDA-Developers so I can ask you any questions for going through the process of making your own rom? SM-T350 doesn't have any Cyanogenmod but only an EVERVOLV rom that has many bugs. Also do you have a tip or a link for Java/C/C++? I have no experience.
Thanks if you respond back!
Good day lads,
Disclaimer:
Code:
I don't know if you noticed a thread in the Q&A section that was closed by Matt. While I respect Matt's decision to close it, I find it a very relevant topic... The future of LineageOS for the P9 Lite. Please note that I do respect meticulous' wishes to charge for his work because I know how time consuming it is I wish to firmly express that I do not condone this mentality when it comes to Linux based operating systems.
I decided to make this thread with my little Dev knowledge in order to attract more devs who's willing to put in work on a stable device tree for free in spirit of community and for all to enjoy.
I do not have the Lineage source code at the moment but I will start downloading soon, I do know that I will need help and I encourage more devs/beginners to lend a hand for the benefit of us all.
Please, to begin, post links to relevant tarballs/links/downloads for development purposes, device tree and kernels, anything you've worked on so perhaps we can all work together.
Cheers
Sent from my HUAWEI VNS-L31 using Tapatalk
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Ignore it's just a critic custom rom user....[emoji12]
Hipom said:
Ignore it's just a critic custom rom user....[emoji12]
Click to expand...
Click to collapse
My words are razor sharp but honest and realistic.
Sent from my VNS-L21 using Tapatalk
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Open source does not mean free, period.
pilgrim011 said:
On xda, it does mean free, period. People that think that they should be paid for contributing here are not welcome on XDA.
Click to expand...
Click to collapse
you are totally right
Just finish already. If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Also it should be in QA SECTION.
You start xda dev thread when you have something made already. Not just with idea.
lsander said:
If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Click to expand...
Click to collapse
This disussions are undesired here. I know a board where you can discuss that. If you want, feel free to have a look at it. This little Board is very pleased about every enlivenment. Opened a thread over there.
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Updated kernel
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Avsky0 said:
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Click to expand...
Click to collapse
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
dady000 said:
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
Click to expand...
Click to collapse
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Avsky0 said:
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Click to expand...
Click to collapse
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
dady000 said:
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
Click to expand...
Click to collapse
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Avsky0 said:
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Click to expand...
Click to collapse
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
dady000 said:
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
Click to expand...
Click to collapse
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Avsky0 said:
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Click to expand...
Click to collapse
Yeah you're right. I just checked it and I am copying Image instead of Image.gz. Seems like it's only a 'cosmetic' issue because it runs anyways.
Great news guys, my sources now compile with latest Linaro toolchain. The kernel actually barely needed any fixes, but I'm not releasing anything prebuilt yet, since I have no idea what impact on stability my hacks might have.
Screenshot
ndroid1562 said:
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Click to expand...
Click to collapse
Perhaps reading through GitHub commits, checking the code and see whether or not you're really interested. If you're using a Linux distribution which I strongly advise, learn bash scripts first - it's easy and self explanatory and from there you will get basics of directories and calling up files.
Goodluck
Sent from my HUAWEI VNS-L31 using Tapatalk
Has anyone created a lineage rom for the A33? Can't find it.
To be clear, for me this forum is like a maze, i was previously searching for a rom for the galaxy S7 and could not find it anywhere but then a forum member sent me a link to an unofficial build which i installed and it works perfectly, so i really dont care about unofficial builds, i will take anything over the preinstalled google spyware, if you know where to find a lineageos build for the A33 please share it!!
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
ShaDisNX255 said:
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
Click to expand...
Click to collapse
I did not expect lineageos to be available for a very new phone, this is the only phone i can get for free from my provider that's why i asked.
As recovery i could use TWRP, or not?
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Librem5OS said:
As recovery i could use TWRP, or not?
Click to expand...
Click to collapse
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
Librem5OS said:
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Click to expand...
Click to collapse
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
Librem5OS said:
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
Click to expand...
Click to collapse
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
ShaDisNX255 said:
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
Click to expand...
Click to collapse
I am from the EU so i dont have a US phone.
Im not an expert so this whole information is a little more detailed than what i usualy deal with, had to read it twice lol. How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
I also never heared about OneUI, does it or does RayOS (your work) have google services in it or is it google free? I don't necessarly need lineage as my os, anything without google spyware will do the job.
-Thank you for the reply.
Librem5OS said:
How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
Click to expand...
Click to collapse
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
Librem5OS said:
I also never heared about OneUI
Click to expand...
Click to collapse
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
Librem5OS said:
does RayOS (your work) have google services in it or is it google free?
Click to expand...
Click to collapse
I leave the Google apps on, I use them so I don't remove them.
Librem5OS said:
I don't necessarly need lineage as my os, anything without google spyware will do the job.
Click to expand...
Click to collapse
Well then when you look for GSI, search for the term vanilla.
ShaDisNX255 said:
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
I leave the Google apps on, I use them so I don't remove them.
Well then when you look for GSI, search for the term vanilla.
Click to expand...
Click to collapse
Thank you now i know what ill have to look for!
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
This seems to be the generic build you where talking about?
I was just a little confused if i should visit phhs github or xda.
After all his XDA thread says: You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST
So i did that and this is where it takes me https://github.com/phhusson/treble_experimentations/releases/tag/v414
However all the files extensions are .xz i have no idea what that means.
When i flashed lineage it said img.tar if i remember correctly.
{
"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"
}
Whats the difference between the two red marked? one says secure img the other only img?
As they say vanilla these must be the ones without google?
Or should i download these instead? If yes which one? I have no clue what the names stand for. Noticed one says ARM and the other doesnt. However what is the difference between those and what is the difference between all arm versions and all non arm versions?
Librem5OS said:
However all the files extensions are .xz i have no idea what that means.
Click to expand...
Click to collapse
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Librem5OS said:
I was just a little confused if i should visit phhs github or xda.
Click to expand...
Click to collapse
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Librem5OS said:
When i flashed lineage it said img.tar if i remember correctly.
Click to expand...
Click to collapse
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
ShaDisNX255 said:
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
Click to expand...
Click to collapse
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
Librem5OS said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
Click to expand...
Click to collapse
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
Librem5OS said:
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Click to expand...
Click to collapse
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
Librem5OS said:
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
Click to expand...
Click to collapse
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Librem5OS said:
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Click to expand...
Click to collapse
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Librem5OS said:
Is the GSI all in one or are further steps required?
Click to expand...
Click to collapse
Usually GSI have all the same steps. Flashing the system and wiping data
ShaDisNX255 said:
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Usually GSI have all the same steps. Flashing the system and wiping data
Click to expand...
Click to collapse
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right? I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Librem5OS said:
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
Click to expand...
Click to collapse
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
Librem5OS said:
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right?
Click to expand...
Click to collapse
This is correct
Librem5OS said:
I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Click to expand...
Click to collapse
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Librem5OS said:
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Click to expand...
Click to collapse
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
ShaDisNX255 said:
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
This is correct
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
Click to expand...
Click to collapse
My bad you are right the twrp for the "arr" shows the first release back in 2017 so that cant be the new 5g version...
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Either way in theory the GSI for android version 12 should/could be compatible with the A33 since it is as you said a generic build, but even if that would work i obviously need a custom recovery in order to flash the system on the device, kinda surprised me you mentioned telegram, i never used it as im not really into social media. I tought if there is a custom recovery my best bet would be XDA forums.
If there is no custom recovery i guess ill have to wait for a official twrp release, or an unofficial one on XDA.
Librem5OS said:
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
Click to expand...
Click to collapse
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Librem5OS said:
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Click to expand...
Click to collapse
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Librem5OS said:
i obviously need a custom recovery in order to flash the system on the device
Click to expand...
Click to collapse
Correct
Librem5OS said:
kinda surprised me you mentioned telegram, i never used it as im not really into social media.
Click to expand...
Click to collapse
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
Librem5OS said:
I tought if there is a custom recovery my best bet would be XDA forums.
Click to expand...
Click to collapse
That's what we all say of course lol
ShaDisNX255 said:
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Correct
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
That's what we all say of course lol
Click to expand...
Click to collapse
Im having a problem with my old Huawai SCL-L01, this phone is slow and bad (only 1gb ram).
Atleast even when the devices is trash i wanted to install linage on it to atleast have privacy, as long as it's still working why not use it?
So the problem is i have usb debugging and oem unlock both activated, i installed adb fastboot / platformtools on my pc (which i downloaded here https://developer.android.com/studio/releases/platform-tools), i connected the phone to the pc and allowed data transfer over usb debugging by confirming the request which appears on the phone, i entered adb reboot bootloader into cmd.exe on the pc and the phone rebooted into bootloader, i then typed adb flash lineageos_rom.img
As a result instead of flashing the img, the cmd output "waiting for any device".
I dont know what is going wrong, what am i doing false in the process?
I was following the instructions here https://forum.xda-developers.com/t/index-list-of-roms-for-y6-2018.3854167/
Librem5OS said:
then typed adb flash lineageos_rom.img
Click to expand...
Click to collapse
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
ShaDisNX255 said:
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
Click to expand...
Click to collapse
I used: fastboot flash system recovery.img
Librem5OS said:
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
View attachment 5678691
Click to expand...
Click to collapse
Great to meet someone who also uses pagexray.fouanalytics.com
Yeah sourceforge is not trustworthy at all...
I always get confused by sourceforge.net and curseforge.com
One of them is owned by twitch or overwolf which are owned by amazon = bigtech.
Anyways, looking at forum.xda-developers.com makes me worry...
I believe you can use any LineageOS GSI, but you'd need to flash it in a custom recovery such as TWRP while retaining the stock kernel in /boot.