As most of you know, the bootloader unlock server for the rest of the world is down and Lenovo is not fixing it and even worse they are not even giving us updates on the issue. This has been going on for 1 month and 10 days now, longer than most of us are willing to wait. A lot of users already sold their phones and bought new ones but for us who decided to stay, we are at the mercy of Lenovo. This is why the petition is started, we want to unlock the bootloader and at least an official statement.
Even if you already unlock your device, please help us, by taking 5 minutes to sign this petition so we can apply pressure on Lenovo. The more the better so please share this post with your friends, family and the internet (Reddit, web forums, etc.)
https://www.change.org/p/lenovo-lenovo-deny-possibility-of-unlocking-phone-s-bootloader
Any help is welcomed.
Personal note :
As a broke student, I can't afford to buy a new phone so this is the only way for me to try to get Lenovo to fix the issue as soon as possible. I really do appreciate any help we receives.
Done ✌
ykcmaster said:
As most of you know, the bootloader unlock server for the rest of the world is down and Lenovo is not fixing it and even worse they are not even giving us updates on the issue. This has been going on for 1 month and 10 days now, longer than most of us are willing to wait. A lot of users already sold their phones and bought new ones but for us who decided to stay, we are at the mercy of Lenovo. This is why the petition is started, we want to unlock the bootloader and at least an official statement.
Even if you already unlock your device, please help us, by taking 5 minutes to sign this petition so we can apply pressure on Lenovo. The more the better so please share this post with your friends, family and the internet (Reddit, web forums, etc.)
https://www.change.org/p/lenovo-lenovo-deny-possibility-of-unlocking-phone-s-bootloader
Any help is welcomed.
Personal note :
As a broke student, I can't afford to buy a new phone so this is the only way for me to try to get Lenovo to fix the issue as soon as possible. I really do appreciate any help we receives.
Click to expand...
Click to collapse
why were u a lazy azz when u had time to unblock ,whose responsibility was it to unblock??
isnt it a unwritten rule or a rule of thumb that mobile enthusiasts or custom ROM lovers to root their phone after 30-40 days of use . there is no way that lenovo is going to keep servers on again ....enough said i done my part have signed up for petition
CHAMUNDA RAM said:
why were u a lazy azz when u had time to unblock ,whose responsibility was it to unblock??
isnt it a unwritten rule or a rule of thumb that mobile enthusiasts or custom ROM lovers to root their phone after 30-40 days of use . there is no way that lenovo is going to keep servers on again ....enough said i done my part have signed up for petition
Click to expand...
Click to collapse
Warranty my friend, not everyone have the money to repair their phone if it breaks. Plus I didnt think of unlocking because there arent many trusted source of rom but since lineageos was released I wanted to unlock it.
Thanks btw
Done
it's online again
tested from Egypt
and finally I'm able to unlock the bootloader
ykcmaster said:
Warranty my friend, not everyone have the money to repair their phone if it breaks. Plus I didnt think of unlocking because there arent many trusted source of rom but since lineageos was released I wanted to unlock it.
Click to expand...
Click to collapse
"Trusted sources of roms"
What's that meant to mean? Subham and firelord have made many stable Oreo roms already
b50corei5 said:
"Trusted sources of roms"
What's that meant to mean? Subham and firelord have made many stable Oreo roms already
Click to expand...
Click to collapse
It meant what it meant. Stable != secure. I am just taking possible security steps. If it was an android expert I would have read the code and compile the roms myself if it wasn't bothersome.
ykcmaster said:
It meant what it meant. Stable != secure. I am just taking possible security steps. If it was an android expert I would have read the code and compile the roms myself if it wasn't bothersome.
Click to expand...
Click to collapse
-_-
Mate, these roms are all 100 percent stable
Why lenovo do that **** bootloader server unblock, it's bad for us it's bad for them, more people who unlock bootloader is less people with warranty.
Maybe someone have a method to force unlock the bootloader, infortunately I can't help mine is already unlocked.
Petition signed, hope it help !
b50corei5 said:
-_-
Mate, these roms are all 100 percent stable
Click to expand...
Click to collapse
Hey, no they are not. Are you claiming that every ROM ever posted on this forum is 100% stable? If so I'd like to see you support your claim.
Silliarse said:
Why lenovo do that **** bootloader server unblock, it's bad for us it's bad for them, more people who unlock bootloader is less people with warranty.
Maybe someone have a method to force unlock the bootloader, infortunately I can't help mine is already unlocked.
Petition signed, hope it help ![/QUOTE
The issue is already fixed
Click to expand...
Click to collapse
ykcmaster said:
Hey, no they are not. Are you claiming that every ROM ever posted on this forum is 100% stable? If so I'd like to see you support your claim.
Click to expand...
Click to collapse
Yes I am.
Los 14.1 is the same if not worse stable then roms from firelord/subham
b50corei5 said:
Yes I am.
Los 14.1 is the same if not worse stable then roms from firelord/subham
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/development/7-1-2-beanstalk-rom-lenovo-p2-t3614921
This rom is in beta not stable. You lose.
oh and just incase, here is the latest rom from subham
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-t3787299
Surprise, surprise, it is beta not stable.
stable != secure
and
there is never a 100% in everything, even if all the roms here are in stable status, it will never achieve 100% stability.
LineageOS 14.1 is better than the rest of the unofficial roms here because
1. The code have been audited.
2. The images are compiled by a trusted source (LineageOS team), unlike the rest of the rom here which is mostly compiled on someone's computer then uploaded to a hosting site.
3. It is stable enough to be an official rom.
ykcmaster said:
https://forum.xda-developers.com/lenovo-p2/development/7-1-2-beanstalk-rom-lenovo-p2-t3614921
This rom is in beta not stable. You lose.
oh and just incase, here is the latest rom from subham
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-t3787299
Surprise, surprise, it is beta not stable.
stable != secure
and
there is never a 100% in everything, even if all the roms here are in stable status, it will never achieve 100% stability.
LineageOS 14.1 is better than the rest of the unofficial roms here because
1. The code have been audited.
2. The images are compiled by a trusted source (LineageOS team), unlike the rest of the rom here which is mostly compiled on someone's computer then uploaded to a hosting site.
3. It is stable enough to be an official rom.
Click to expand...
Click to collapse
Mate, I don't think you get how it works. Beta does not affect stability or not. Everything that works in los 14.1 works in subham/firelords roms.
Point 1 is absolutely bullcrap, I suggest you do some research.
Point 2 is bullcrap too. The thing that complied the rom doesn't affect the rom. Mike compiles on a computer as well. You think he has a supercomputer or what?
Point 3 doesn't matter. Official is just a tag.
b50corei5 said:
Mate, I don't think you get how it works. Beta does not affect stability or not. Everything that works in LOS 14.1 works in subham/firelords ROM.
Point 1 is absolutely bullcrap, I suggest you do some research.
Point 2 is bullcrap too. The thing that complied the ROM doesn't affect the ROM . Mike compiles on a computer as well. You think he has a supercomputer or what? Point 3 doesn't matter. Official is just a tag.
Click to expand...
Click to collapse
The status does mean something. It means that is is not stable enough to have the status stable. How could a buggy software be considered stable?
Point 1 : What do you think Gerrit and Open Source is for? https://wiki.lineageos.org/usinggerrit-howto.html
Point 2 : You missed the point here. It is not what compiles it. It is who. Just because the source is clean doesn't mean the build is clean. Assuming you trust the developer, A lot of the ROM here don't even provide PGP keys for you to check if the ROM is unmodified in transit! How could that be secure? https://android.stackexchange.com/questions/189063/how-can-i-trust-roms
Point 3 : There are requirements to be an official ROM. One of it is be stable enough. https://wiki.lineageos.org/submitting_device.html
Please do some research and have some common sense before you open your mouth.
So far you have not supported your claims that all the ROM on this forum are 100% stable. You can never prove that point because nothing is ever 100% even if all ROM here are stable.
Related
First question does Osprey's hardware support Android O ?
Prob does but we'll prob not be able to have some features
Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too
Our device is in list to get los 15 ie. android O
androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .
Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli
Have faith on our awsome developer we will surely have android O
Well, Android Oreo is out. I really hope that Osprey will get it soon.
https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices
That would be amazing. Let's wait for a developer opinion.
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this
rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA
It's true.
@Razziell left the ship some days ago.
Xiaomi is the devil. Left us with F*CKING BUGGED source codes.
Yeah, that is sad, there is basically no one left for our good old Redmi 4 Prime.
Does anyone knows how @jacoghi is doing ? We haven't see the man in a long time and I would like to know if he is doing well in his life.
Title is misleading. He compiled the ROMs not ported them.
LokaX2 said:
Yeah, that is sad, there is basically no one left for our good old Redmi 4 Prime.
Does anyone knows how @jacoghi is doing ? We haven't see the man in a long time and I would like to know if he is doing well in his life.
Click to expand...
Click to collapse
I believe is everything okay...
psykkuno said:
Title is misleading. He compiled the ROMs not ported them.
Click to expand...
Click to collapse
Whatever, he was a great DEV! <3
thomasginn said:
Whatever, he was a great DEV! <3
Click to expand...
Click to collapse
How can you say that when you use epic rom? Lmao
psykkuno said:
How can you say that when you use epic rom? Lmao
Click to expand...
Click to collapse
ayo, I used his roms xD
thomasginn said:
ayo, I used his roms xD
Click to expand...
Click to collapse
xD
It's really sad
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Blackeyed73 said:
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Click to expand...
Click to collapse
Always though 'bout that. it WAS to be possible, a few differences.
thomasginn said:
It's true.
@Razziell left the ship some days ago.
Xiaomi is the devil. Left us with F*CKING BUGGED source codes.
Click to expand...
Click to collapse
Can you elaborate on what is exactly wrong? Was this done on purpose or...?
Jejking said:
Can you elaborate on what is exactly wrong? Was this done on purpose or...?
Click to expand...
Click to collapse
Xiaomi doesn't release kernel source for building AOSP or CAF based rom, kernel source only work for MIUI at most. Also most proprietary vendor driver not available as sources (only blob). It's pain to build custom rom from Android fork.
Compared to Samsung, Sony, Lenovo, Oneplus etc, almost all abandoned xiaomi devices suffered same fate, the custom rom will always missing something. We were very lucky if we had such a great developer.
My previous device, redmi 1s never get update beyond kitkat, but armani-dev (especially fefifofum) were a great team, they bring mostly stable nougat release (LOS, Mokee, Slim, etc).
dels07 said:
Xiaomi doesn't release kernel source for building AOSP or CAF based rom, kernel source only work for MIUI at most. Also most proprietary vendor driver not available as sources (only blob). It's pain to build custom rom from Android fork.
Compared to Samsung, Sony, Lenovo, Oneplus etc, almost all abandoned xiaomi devices suffered same fate, the custom rom will always missing something. We were very lucky if we had such a great developer.
My previous device, redmi 1s never get update beyond kitkat, but armani-dev (especially fefifofum) were a great team, they bring mostly stable nougat release (LOS, Mokee, Slim, etc).
Click to expand...
Click to collapse
Redmi Note 4X has many ROM's, officially.
There was idea that that device is like ours so we should talk to some devs and use its sources
Blackeyed73 said:
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Click to expand...
Click to collapse
That would be essentially the same proccess we are now. It can be achieved though to use the tree from Mido and modify it for our device. Make a stable tree then compile
Hello. I have a stupid idea, but it might work. What about porting ROM's from Nubia Z11 mini S? It has the same specs(i mean SP625 and Adreno 506).
Please, comment: https://forum.xda-developers.com/redmi-note-4/how-to/developers-help-t3660926
We must show how great we are
gsuzeda said:
Please, comment: https://forum.xda-developers.com/redmi-note-4/how-to/developers-help-t3660926
We must show how great we are
Click to expand...
Click to collapse
great work friend
From RN4 section:
Razziell said:
You do not need to talk about things you do not know. I had problems with the hard drive and only some people from the Russian community helped them to solve. For them, I continue to work. The rest can freely use my source, they are completely working.
Click to expand...
Click to collapse
You have problem with HDD? Why didn't say that in R4P forums, you just say that you want to stop developing because you don't have time to do it. Is that whole reson to stop sharing with R4P community ?
Just be Patient, always belive something wonderful will be happening!
Our Roms kernel are uptodate so no worry please
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.
Hi, I will start making some ROMs for this device but since I do not trust shady bootloader unlocking services I won't be able to test them myself before publishing them. If anyone with a unlocked bootloader is willing to test my future ROMs, I'd be very thankful.
Regards,
XTutorials said:
Hi, I will start making some ROMs for this device but since I do not trust shady bootloader unlocking services I won't be able to test them myself before publishing them. If anyone with a unlocked bootloader is willing to test my future ROMs, I'd be very thankful.
Regards,
Click to expand...
Click to collapse
nice to hear that there is a new developer I would like to test.
MfG eracer
Maybe you and FluFlu should team up? :~
argh9 said:
Maybe you and FluFlu should team up? :~
Click to expand...
Click to collapse
Well, I would be happy to work with anyone because I already built 3 ROMs and all gave me build errors. Maybe it's because I didn't prepare the device tree right, I don't know. I was accustomed to working on a older Huawei device, with far less complicated source code.
@FluFlu
Any interest in helping this chap?
I'm in for testing - CLT-L04 (Canadian-Mexico) all the best.
Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)
if there are too many people using this device
nobodyAtall said:
Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)
Click to expand...
Click to collapse
ETA? XD im kidding.
I have this device as a main, the stock ROM sucks, so I made a fully comited attempt to either fix it or break it flashing ArrowOS, it got bricked unbricked and I managed to install ArrowOS at the end, I still have all the files I used in every step of the way.
Im a n00b but I would really like to learn some more about how phone modding works, I can be your tester if you want.
tell me if youre interested, also, how did you get started in all of this?
I have a secondary device and a sure way to return to a working state after mishaps, so I'd like to be a tester as well.
nobodyAtall said:
Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)
Click to expand...
Click to collapse
I always like to test new things so i can be your tester if you want