Related
Today my wife got this device as a gift for Christmas. She asked me to look at it and set it up for her. After about an hour of research I was deeply disappointed by the fact that this device has no ROMs or Kernels and barely supports ROOT. The device is kind of slow for 2013 due to its one core 1GHz processor. But I am sure this issue would be fixed with optimizations from custom ROMs and Kernels. I myself am not an android developer but do some coding in the free time and worked on a few ports of sense for several devices. On this thread I would like to get as many developers possible with the Asus MeMO Pad to communicate and collaborate to develop a working port of CyanogenMod for the device. I will be happy to help anyone interested in this project by doing some work in the free time. I chose CyanogenMod as it is probably the easiest one to compile and is much simpler than its competitors. If we get a successful build of CM then we can move on to developing Kernels and more complex versions of Android. Keep in mind that this is not a request for any particular developer but just an invitation to collaborate and build a working ROM for this tablet. If you are interested in working with me on this project please PM me or comment down below. I will be glad to help as much as I can. Thank you to all of the developers that would be willing to participate in this project.
Sent from my Nexus 4 using xda app-developers app
Im in
I did the AMPC app and mini rom (not a full rom but more mods collection)
How are you skills to decompile img ?? since the guy who did root before is no more...and we should start by doing root for latest FW.
and CWM is also very buggy (build using online kitchen)
Please feel free to PM me
I'd like to but I don't know android coding. I do some basic Java programming if that helps
Sent from my MemoPad
crazykiddo said:
Im in
I did the AMPC app and mini rom (not a full rom but more mods collection)
How are you skills to decompile img ?? since the guy who did root before is no more...and we should start by doing root for latest FW.
and CWM is also very buggy (build using online kitchen)
Please feel free to PM me
Click to expand...
Click to collapse
I will PM you as soon as possible and we can begin on the work. Sorry due to the vacation I am not home and will only be back stating monday.
fundre said:
I'd like to but I don't know android coding. I do some basic Java programming if that helps
Sent from my MemoPad
Click to expand...
Click to collapse
Thank you for you reply also, as of right now I don't see our need for any Java coding, but maybe if we find a need for it I will message you. Thank you once again.
Sent from my Nexus 4 using xda app-developers app
aanonymoushuman said:
I will PM you as soon as possible and we can begin on the work. Sorry due to the vacation I am not home and will only be back stating monday.
Thank you for you reply also, as of right now I don't see our need for any Java coding, but maybe if we find a need for it I will message you. Thank you once again.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hi! I'm the guy that made CWM for this tablet, as well as the one on whos idea the whole root thing is based I'm very glad that someone picked up work on this tablet and is trying to make it better, since I don't have the time and I've lost my patience since ASUS is refusing to co-operate as far as updates and source codes are concerned. You can always PM me with questions as well as all or any info you have and I'm also willing to test builds out. Thanks
nerotNS said:
Hi! I'm the guy that made CWM for this tablet, as well as the one on whos idea the whole root thing is based I'm very glad that someone picked up work on this tablet and is trying to make it better, since I don't have the time and I've lost my patience since ASUS is refusing to co-operate as far as updates and source codes are concerned. You can always PM me with questions as well as all or any info you have and I'm also willing to test builds out. Thanks
Click to expand...
Click to collapse
Hiya @nerotNS, I'm currently new (a noob) at xda-developers forum but since I'm actually getting a memo pad what better way of installing cyanogenmod properly than asking for help. However I couldn't help but to find the source code, and I did. I'm currently still learning so the source code wouldn't be of help to me than it would to you. So that said, heres the source
==> support (dot) asus (dot) com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad&p=28&s=6
(remove spaces and replace '(dot)' with '.')
42java said:
Hiya @nerotNS, I'm currently new (a noob) at xda-developers forum but since I'm actually getting a memo pad what better way of installing cyanogenmod properly than asking for help. However I couldn't help but to find the source code, and I did. I'm currently still learning so the source code wouldn't be of help to me than it would to you. So that said, heres the source
==> support (dot) asus (dot) com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad&p=28&s=6
(remove spaces and replace '(dot)' with '.')
Click to expand...
Click to collapse
Hmm that's the kernel source code, we already have that Though it was in a bit of a strange format, plus I firmly believe that it's outdated as I think ASUS made some changes in the kernels via OTA. Thanks for your tip though,it's good to see that someone's trying to do with this pad
RE: CM Development
Hello, new guy here at XDA, I do not have any knowledge to Linux or Android programming yet I know how to flash and play with recoveries and such things. I am willing to be a tester for this project.
waiting for someone to port this into CM...
source code: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad&p=28&s=6
Cygaeonmod 12 me172v device tree
After months of research and goggleing i have made a me172v device tree and i will upload it on github by 1 st of march
i want someone to test the device tree by building a cygaeonmod 12 rom
i have made a official working recovery using the tree but there are few errors i am working on that
if some body wants to help here s my email adrress [email protected]
its double 'a' DONT GET CONFUSED:laugh:
THIS IS MY SECOND POST ON XDA BY MY NEW USERNAME
SORRY FOR BAD ENGLISH
wait till 1 st of march
Pranav89 said:
After months of research and goggleing i have made a me172v device tree and i will upload it on github by 1 st of march
i want someone to test the device tree by building a cygaeonmod 12 rom
i have made a official working recovery using the tree but there are few errors i am working on that
if some body wants to help here s my email adrress [email protected]
its double 'a' DONT GET CONFUSED:laugh:
THIS IS MY SECOND POST ON XDA BY MY NEW USERNAME
AND HERE'S A LINK FOR GITHUB ME172V RESPORITORY : github.com/Pranavkumar09/android_ASUS_MEMOPAD_ME172V
just add before the url
SORRY FOR BAD ENGLISH
wait till 1 st of march
Click to expand...
Click to collapse
It's a good news... But too bad my memo pad has broken successfully and hard to find the spare part
Sent from my Lenovo_A706 using XDA Premium 4 mobile app
Keep me posted on your progress, I will keep an eye on your github repo.
?
I Too Am Interested
I may be able to lend my tablet for the cause of testing. Just can't brick it.
It's my 7 year old daughter's, so no harm no foul.
I'll look for updates
It could be hard to port on cm, because the chipset is VIA and no similar device successfully ported with this chipset..
Sent from my Lenovo A706_ROW using XDA Premium 4 mobile app
Thanks Bro That Will be a great help
maricopajoe said:
I may be able to lend my tablet for the cause of testing. Just can't brick it.
It's my 7 year old daughter's, so no harm no foul.
I'll look for updates
Actually i bricked my asus bootloader and even adb does not work out and i am just able to make half of it if you could provide me some information about the pad
and i have found a similar device tree from tft300t and tft700t
first i will make a device tree which can make a working recovery basically twrp
guys its an awesome tab but very slow and having cm 12.1 will be great on the tab so please help
Click to expand...
Click to collapse
Pranav89 said:
maricopajoe said:
I may be able to lend my tablet for the cause of testing. Just can't brick it.
It's my 7 year old daughter's, so no harm no foul.
I'll look for updates
Actually i bricked my asus bootloader and even adb does not work out and i am just able to make half of it if you could provide me some information about the pad
and i have found a similar device tree from tft300t and tft700t
first i will make a device tree which can make a working recovery basically twrp
guys its an awesome tab but very slow and having cm 12.1 will be great on the tab so please help
Click to expand...
Click to collapse
What info do you need?
Click to expand...
Click to collapse
CM 12.1 for me172v
My ME172V device tree repo address https://github.com/Pranavkumar09/android_device_asus_me172v
Finally i made it after 1 months hardwork
I wanted someone who has more internet plan atleast 50 gb who can make the cm 12.1 rom as i live in country like India where internet speed sucks it wont work plzzzzzzzzzz guyz
u can even use Docker to build it on windows follow this link http://forum.xda-developers.com/showthread.php?t=2650345 or u can use ubuntu plzzz help me out
if any ones interested u can email me [email protected] for any queries or doubt abt the device tree
It would be a great help
Help
Pranav89 said:
My ME172V device tree repo address https://github.com/Pranavkumar09/android_device_asus_me172v
Finally i made it after 1 months hardwork
I wanted someone who has more internet plan atleast 50 gb who can make the cm 12.1 rom as i live in country like India where internet speed sucks it wont work plzzzzzzzzzz guyz
u can even use Docker to build it on windows follow this link http://forum.xda-developers.com/showthread.php?t=2650345 or u can use ubuntu plzzz help me out
if any ones interested u can email me [email protected] for any queries or doubt abt the device tree
It would be a great help
Click to expand...
Click to collapse
I'm gonna try building it with Docker. Is there still a chance of killing the device bootloader?
Btw I'm a total noob with custom roms so it may take a while + my PC is old
Thank you Darthsternie
Darthsternie said:
I'm gonna try building it with Docker. Is there still a chance of killing the device bootloader?
Btw I'm a total noob with custom roms so it may take a while + my PC is old
Click to expand...
Click to collapse
what do u mean by killing the bootloader????
whats ur system specification like ram processor
plzzzzz ur the last hope for this device
CPU Specs
Pranav89 said:
what do u mean by killing the bootloader????
whats ur system specification like ram processor
plzzzzz ur the last hope for this device
Click to expand...
Click to collapse
I have a AMD Athlon Dualcore 5000B 2,60 GHz with 4 GB RAM
And my 500gb drive died yesterday so I have to buy myself a new drive first
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Flohack said:
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Click to expand...
Click to collapse
Well, that should be the least of your problems!
Option58 said:
Well, that should be the least of your problems!
Click to expand...
Click to collapse
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
I don't own your device. But if that's the case...good luck :good: :fingers-crossed:
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
holysaint1 said:
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
Click to expand...
Click to collapse
Hi,
good to know. We just need to make sure AT&T version does not have too much difference from the international one. Can you dedicate it for testing? It does not need data to be wiped normally, since Ubuntu runs off a container in the data partition but you never know...
I am currently stuck with the GUI and tbh I have no idea when and how this will be resolved. Samsung has done a great job with their GPU and Exynos, but our libhybris part does not want to play with it nicely.
Keep you updated!
BR
Actually I use it as my DD but wouldn't mind testing a few ROMs for the gd of the comm.
Aiite then. Patiently waiting for the update.
I have the international version of S3 GT-i9300. It is currently without a working rom, so I need to find time to see if it will boot with an official rom flashed with odin, it currently has an old clockwork mod recovery installed and a lineage os rom that wont boot..
If I get it working again, then I could dedicate it to testing... I would love to have a phone that was pure linux with phone capabilities... then I would no longer need to use google's linux abomination known as android
Hi,
sorry to say but I stopped now every porting activity, since Canonical dropped Ubuntu Touch and we are struggling on all other frontlines to get the community together for continuing the OS.
There will be no new hardware ports in the near future, which I think will be up to 1 year or 2. By that time, also S-III etc are end of life, since its hard to support multiple generations of smartphones with different kernels properly. Im afraid we are too late...
Anyway, contact me if you want to help in other areas of Ubuntu Touch going UBports community
BR
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
laharl_22 said:
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
Click to expand...
Click to collapse
same here ! I am also trying to find from so long, tried a lot but no luck !!
Please somebody post it
Hi there,
Florian from UBports. The active devices that we support can be found here: https://devices.ubports.com/#/ - that being said, you wont find the Note 2 there as an active device. What happened in the past I can´t say, but currently we have no ETA to work on new devices.
BR Florian
I am on a Asus trio tx201la INTEL x86 tablet on android 4.2 on the tablet part. I researched that The zenfone 5, dell venue 7 and the samsung galaxy tab 3 10.1. All have the same intel atom z2560 cpu soc and some are running Android 7 & even 8 now.
The Galaxy tab 3, zenphone 5 got a lot more attention and thus a lot more custom rom attention. Dell venue and my Trio got little to no attention due to poorer sales.
The galaxy tab 3 has been updated to 7.1.1 see:
http://techbeasts.com/install-android-711-nougat-galaxy-tab-3-101-lineageos-141/
Now How can that help the Trio? I found this tool, but no flash.xml so no luck using it:
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Here is a guide on how to use it: http://www.aryk.tech/2016/04/how-to-flash-stock-firmware-using-intel.html?m=0
This is all NEW as of 2017. So its not been available before this.
The TX201LAF a french tablet version of the TX201LA is in the same boat but it at least it is on 4.4. Its kernel firmware is here: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LAF&p=3&s=587
My big question is with all these roms for x86 atom z2560 & z2580 soc's shouldn't I be able to get an updated rom somehow? I imagine that would involve building a rom myself but if the base soc is the same isnt it possible to build the rom for a different device and use a different kernel source like I linked above? The kernel source has the drivers I need right, for the device to run? Ive heard a lot of people talk about you wont get the touch panel to work or the wifi. I understand that but isnt it all loaded from the kernel source? So basically if I have kernel source and grab an updated rom from lineage 7 for the galaxy tab 10.1 and replace the kernal i'm good to go right? I know there is more to it but really looking for some help here?
Even if I can just get the tx201laf image to load on my tx201la that would be
something, its an update from 4.2 to 4.4. Both devices are identical, so that should make it a lot easier right? Looking for any insight to xda experts can provide.
Hi ! I'm still using my trio so I'm very interested ! Did you succeed ?
Thks a lot
no luck yet
I had hopes that this would turn out to work but you cant use the intel flash tool without a flash.xml which is written for the device. SO that stopped me dead in my tracks.
I recently found this: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466/page37
Hoping this dev will give the tx201la a shot. There is also this: https://forum.xda-developers.com/an...g/tool-multirom-recovery-replacement-t3102395
Do you realize how simular the tx201la is to just about every zenphone made since the newest. IE almost all of those roms would likely boot on our tablet.
??
Any other input?
Come on guys, has everyone moved on to the shinny new toys?
madhits45 said:
Common guys, has everyone moved on to the shinny new toys?
Click to expand...
Click to collapse
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Palm Trees said:
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Click to expand...
Click to collapse
Thanks for the tip. Now I need to find help up-streaming my kernel:
Device info: https://valid.x86.fr/a/wkb2d8
Kernel source: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LA&p=3&s=587
Could really use help doing that.. Total noob & trying to understand all the terminology.
madhits45 said:
Thanks for the tip. Now I need to find help up-streaming my kernel:
Device info: https://valid.x86.fr/a/wkb2d8
Kernel source: http://support.asus.com.cn/Download.aspx?SLanguage=en&m=TX201LA&p=3&s=587
Could really use help doing that.. Total noob & trying to understand all the terminology.
Click to expand...
Click to collapse
Then go here: https://4pda.ru/forum/index.php?showtopic=530541
Palm Trees said:
Best bet https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Click to expand...
Click to collapse
Palm Trees said:
Then go here: https://4pda.ru/forum/index.php?showtopic=530541
Click to expand...
Click to collapse
HOLLY $#%^ PALM TREES!!!!!!
Ok I checked out the Russian thread, which I cant believe I had never found, seriously what search engine do you use? Or are you Russian?
Anyway that lead me to this: https://cs5-3.4pda.to/10031052/20170404_145326.jpg?6c8bd0e99d5f5d5ce8c14e92c456565c
That might not mean much to many but its the TX201LA running the Asus memopad 10 android 4.2.2 and its actually working. So that is a huge deal.
Then I found this: https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
There is a updated rom for the memopad 10. Now I hope I can get this rom to run with slight variations.. Will see..
madhits45 said:
HOLLY $#%^ PALM TREES!!!!!!
Ok I checked out the Russian thread, which I cant believe I had never found, seriously what search engine do you use? Or are you Russian?
Click to expand...
Click to collapse
No problem. I'm not Russian. I use Google mostly. My pride and joy is my memory (lol) :laugh: and I like to help if I can. Saw your thread and simply shared a few resources, I figured were helpful
Hey,
over the last few weeks I've used my Christmas vacation to start working on the Z18 again. However since work is coming up again soon, I won't have that much time (and nerves) for working on this properly until the end of summer probably.
That's why I want to share my codebase with you, so maybe someone can pick up where I left off (and really, it's nothing big I did. I merely set up the device tree and made it compile more or less. It doesn't boot because of avb and I'm not aware of any way around that)
The device tree can be found here. It's still using a prebuilt kernel but I'll work on fixing the kernel source to a compileable state next.
If anyone wants to get involved, help or pick this up, feel free to do so. The community and I are always happy for help.
Explanations of what the next steps would be can be found below.
Again, do not install this unless you want to softbrick! It's not useable at all and will currently fail at boot verification!!
So what's next?
Fixing avb2.0: This isn't an easy task. How I understand, it either needs the official keys or I failed at signing the build with test keys from LineageOS. Either way this is the first step and top priority so the device boots again at least
EDIT: It seems that https://github.com/rockchip-linux/tools/tree/master/linux/Linux_SecurityAVB might be of some use (given that youyim123, the guy who also did the TWRP for Z18 starred this project). However I don't speak Chinese and putting my device in the hands of Google Translate is risky.. so anyone willing to translate, I'm open for DMs or anything
EDIT2: avb is working, so we can move on to breaking our system now (yay)
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Zahidul Hasan said:
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Click to expand...
Click to collapse
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
curtisy said:
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Click to expand...
Click to collapse
Zahidul Hasan said:
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
Click to expand...
Click to collapse
Yeah, that thread, if most of the development threads on the Z18 so far, was made by me. I also mentioned in post #3 that flashing Gapps doesn't seem to be working and I was trying to ask the GApps team for help. I never got an answer though, so I stopped looking into this and instead focused my effort on providing a working Lineage build for everyone. The result of that is this thread here
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
sky104hk said:
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
Click to expand...
Click to collapse
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
curtisy said:
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
Click to expand...
Click to collapse
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
sky104hk said:
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
Click to expand...
Click to collapse
As a quick update for everyone here as well because the discussion has somewhat shifted to the TWRP thread I worked around avb now. I also have a system.img but it's not working as of yet. If you want to get stuck in a boot loop, feel free to ask here and I'll attach the files in the OP for you to try and modify. Without building from source, there's probably not that much you can do though.
Hint: try booting phh-treble GSI first.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
curtisy said:
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
Click to expand...
Click to collapse
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
j1505243 said:
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
Click to expand...
Click to collapse
Awesome. Thank you for the heads up! Might be worth to invest some time in this again then.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
curtisy said:
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Click to expand...
Click to collapse
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
j1505243 said:
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
Click to expand...
Click to collapse
Yeah that's actually the same point I stopped at with Lineage. Got it to boot to the Nubia logo, captured logs and I can see some weird errors. But getting replies on IRC is a pain, especially if I can only be online for 2hrs a day. That's why I had hoped someone would pick this up but to no avail. Guess I'll have to look into it again and experiment.
Thanks for your help so far! If there's any more tips you want to share, I'm always open for them
furiousjay said:
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
Click to expand...
Click to collapse
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
curtisy said:
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
Click to expand...
Click to collapse
Unfortunately I personally don't know somebody who has the skills to support you. I have included a call for support for your project in our review.
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Alando123 said:
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Click to expand...
Click to collapse
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with an assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
First of all, it depends on whether the stock source code is available for your device, if there is no stock source code available to the public(no, I'm not talking about the stock firmware file), then you will not be able to build a custom ROM from source for your device, which means that you won't be able to build anything like LineageOS because setting up the device tree requires the stock source code. No source code=no device tree, no device tree=no LineageOS or AOSP ROMs. Devices that do not have a source code available can only get ROMs if someone chooses to port a ROM from a similar device with similar hardware, that is the only way to get a ROM without stock source code. The stock firmware would be required in order to port a ROM from a similar device, if the stock firmware is not available, you can't port a ROM.
Sent from my LGL84VL using Tapatalk
Droidriven said:
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Alando123 said:
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Click to expand...
Click to collapse
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery such as TWRP(which you'd probably have to build for yourself, which is yet another task to learn in development along with learning to build a ROM, not to mention learning how to get the kernel right) in order to flash a LineageOS custom ROM or any other ROM that is not based on stock, TWRP is easier to learn how to build than a ROM, but still a task in itself. Modified stock ROMs can be customized and flashed without root or custom recovery but they aren't "true" custom ROMs, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Droidriven said:
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery in order to flash a LineageOS custom ROM or any other ROM that is not based on stock. Modified stock ROMs can be customized and flashed, but they aren't custom, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Alando123 said:
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Click to expand...
Click to collapse
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools. I also just stumbled upon the link to the LineageOS page about blobs right before you replied ?
Alando123 said:
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools
Click to expand...
Click to collapse
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Alando123 said:
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Click to expand...
Click to collapse
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Alando123 said:
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Click to expand...
Click to collapse
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't think that any camera app would have helped.. I replaced libcameracustom.so from a different device, and front camera works, but no both cameras have a blue hue on them
I am having problems with building lineageOS for my "Unsupported" Device I have made themed ROMS, Themes for cyanogenmod, Themes for substratum, basic apps for my ROM, and customized recovery and ported ROMS to my device but I need a small headstart to actually "Build" lineageOS for my device. Thats It
Regards
Manav Harsana