Develop Bugs

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74

I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!

Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?

bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.

fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.

I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4

Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!

I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app

If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app

I am definitely willing to help in any way I can.

I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...

grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.

Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?

mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.

Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.

JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?

droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source

JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!

Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.

Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

Android&Linux dual boot?

So ... I'd like to dual boot a normal linux on that tab.
My first problem is something like a boot loader that let me select wether to boot android or any other system (with touch capability and timeout ideally).
Some googling around didn't bring anything useful besides "it's highly dependent on the device".
Is there something like that out there? The alternative I thought of is to build something like the Ubuntu Phone boot app, but I have no idea how it works.
The next problem would be hardware support, but I will look at that issue later.
The chroot solution would be a fallback (I have to look deeper into, especially in terms of performance), but I'd prefer to have a real system.

hofmann.christian said:
So ... I'd like to dual boot a normal linux on that tab.
My first problem is something like a boot loader that let me select wether to boot android or any other system (with touch capability and timeout ideally).
Some googling around didn't bring anything useful besides "it's highly dependent on the device".
Is there something like that out there? The alternative I thought of is to build something like the Ubuntu Phone boot app, but I have no idea how it works.
The next problem would be hardware support, but I will look at that issue later.
The chroot solution would be a fallback (I have to look deeper into, especially in terms of performance), but I'd prefer to have a real system.
Click to expand...
Click to collapse
Just to clarify which exact tab s fo you have, you say also you will look into the issue of hardware support later....this is the wrong order im sorry to say and many people will agree its the first thing u shud look at.....for example it has to be taken into account that your using an arm processor and u cant just use any linux distro on any arm processor e.g arm v5 is different architecture to armv7...meaning a new kernal needed that runs your linux and android...you really are going into waters way above even my head...start with porting cynogenmod completely from scratch...look st compiling your first real rom and you will learn A LOT and MAY begin to comprehend what your asking here....not meaning to sound god almighty but honestly this involves a lot of factors.

Well, I am aiming at arch and afaik there should be ARM versions for any relevant CPUs, so this is not that a big deal. GPU and the likes could be way worse.
Also: 8.4", not sure if there are different versions of these besides the storage capacity

hofmann.christian said:
Well, I am aiming at arch and afaik there should be ARM versions for any relevant CPUs, so this is not that a big deal. GPU and the likes could be way worse.
Also: 8.4", not sure if there are different versions of these besides the storage capacity
Click to expand...
Click to collapse
Ok pal all you need to do then is create a kernal that will support both the android 4.4.2 and linux that youve custom built and taylored to your phones specs.
Heres a link to expanded info on linux and arm: http://www.reddit.com/r/linux/comments/2n21i2/can_arm_chip_linux_servers_run_all_software_or/
Heres a link to building kernals : https://source.android.com/source/building-kernels.html
And heres a link to your specs something you WILL need : http://m.gsmarena.com/samsung_galaxy_tab_s_8_4_lte-6435.php
Please keep me updated on this as if you put all the effort in needed then it would a nice self achievement...good luck m8.

pdolton2000 said:
Ok pal all you need to do then is create a kernal that will support both the android 4.4.2 and linux that youve custom built and taylored to your phones specs.
Click to expand...
Click to collapse
I thought about that, too. But that may be especially hard on arch due to regular updates. It still may be possible and I will have a look at it, but I'd prefer multiple kernels to choose from.
Also: Does having one single kernel in any way help with the boot choice problem?

hofmann.christian said:
I thought about that, too. But that may be especially hard on arch due to regular updates. It still may be possible and I will have a look at it, but I'd prefer multiple kernels to choose from.
Also: Does having one single kernel in any way help with the boot choice problem?
Click to expand...
Click to collapse
Well without one single kernal you cant boot anything...why go though making a bootloader to something when youve got nothing to boot yet? The bootloader is the easiest part its the rest thats the harder. Heres an example of bootloaders that shows its more than possible.
https://play.google.com/store/apps/...droid&pcampaignid=APPU_3DrCVJj1A8vW7AaIu4HQDQ
And the designer is a member of XDA so i say again you first need to build kernal and linux that are compatible with your hardware....then contact this bloke who made MultiBoot and when he sees all the hard work you put in he will be more than happy to help you i should imagine.
---------- Post added at 12:26 PM ---------- Previous post was at 12:18 PM ----------
pdolton2000 said:
Well without one single kernal you cant boot anything...why go though making a bootloader to something when youve got nothing to boot yet? The bootloader is the easiest part its the rest thats the harder. Heres an example of bootloaders that shows its more than possible.
https://play.google.com/store/apps/...droid&pcampaignid=APPU_3DrCVJj1A8vW7AaIu4HQDQ
And the designer is a member of XDA so i say again you first need to build kernal and linux that are compatible with your hardware....then contact this bloke who made MultiBoot and when he sees all the hard work you put in he will be more than happy to help you i should imagine.
Click to expand...
Click to collapse
EDIT
If you wanted a quick way out of all that i can only suggest emulating linux on android...find an example here:
https://play.google.com/store/apps/...droid&pcampaignid=APPU_FT3CVObxNIOa7gbxwYDACg
Good luck anyway pal hope it goes to plan

It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.

hofmann.christian said:
It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.
Click to expand...
Click to collapse
Haaa whats the chances, i only thought of that last minute, hope it works out man

pdolton2000 said:
Haaa whats the chances, i only thought of that last minute, hope it works out man
Click to expand...
Click to collapse
Well, so I am back at the "I need a boot manager" square just with the information that there is something like this which just doesn't work for now.

hofmann.christian said:
Well, so I am back at the "I need a boot manager" square just with the information that there is something like this which just doesn't work for now.
Click to expand...
Click to collapse
Sorry pal you want a boot manager to run this emulated version of linux? This works by emulating it inside android os? Or have i misunderstood?

pdolton2000 said:
Sorry pal you want a boot manager to run this emulated version of linux? This works by emulating it inside android os? Or have i misunderstood?
Click to expand...
Click to collapse
Who said something about an emulated Version? I want a real full fledged Linux to dual boot on a tablet.

hofmann.christian said:
It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.
Click to expand...
Click to collapse
Misunderstanding thought you were refuring to the edit i made just above this post im quoting in its original place.
Ok so you now no the idea of bootloaders exist and for them to work you need linux and a kernal ie an os otherwise theres nothing for it to boot, you need to compile a compatible kernal and lixux distro together thats going to work with your spec so then someone else can help you with the bootloader that will dual bot both it and android...otherwise your asking somebody to draw a design of a building and predict the levels of the foundations before the land itself exists which cannot be done.
Ive provided you research material in kernal design, the specs of your phone, about how linux and arm work together, ive provided you with a link to a bootloader exactly like what your after made by a member on xda whom u can see links to in the download of it to show that you have a place and a person to ask who specializes in the field once youve created what you want to dual boot with android.
Theres nothing more that can be done pal its all been made very clear.

karthick's cm14.1 is it 4 real?

I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Pd. There a bootable cm13 rom that i'm using to write this :v
I'm sorry if i had a bad engish, i'm a mexican :v

armando121504 said:
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Click to expand...
Click to collapse
Yeah... I have just flashed it, but it has been in a bootloop for 20+ minutes already. Needless to say, this is probably a test/WIP CM14.1 build that @karthick mostwanted is testing for the Galaxy Fame to see if it will work at all. From what I am aware of, later CM ROMs (CM13, 14, and 14.1) will not work as well as they should on this device as it is low-end and doesn't have the RAM or processing power that is required, however, CM13 is fairly usable from what I have tried, but I still find the CM11 (KitKat 4.4.4) ROMs to be the best. Then again, it is always good to keep and eye on and test the latest builds that the developers release, as I have seen some older devices get ROMs which shouldn't work on them because of their hardware, but do, because the developer is able to configure it to make it work.

I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way

karthick mostwanted said:
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
Click to expand...
Click to collapse
Fair enough, but I assumed that since it was publicly available to view and download, then it should be okay to publicly discuss about the development surrounding the ROM/s, but I guess not.
Thank you for the time and effort you put into these builds and the continuation of custom ROM development for this device.

Project Treble

As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance

Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?

Dior DNA said:
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Click to expand...
Click to collapse
indeed and that is what made me think, because aftervall, android is build upon lnnux

Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.

the Doctor said:
[...]Also, it gives literally zero benefit to a custom ROM.[...]
Click to expand...
Click to collapse
I mark these words. Have a nice day.
update
Perhaps there is no functional benefit. But porting seems easier for some devices:
What about :
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
This is the Samsung Galaxy S9 running on AOSP Android Oreo thanks to Project Treble

the Doctor said:
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
Click to expand...
Click to collapse
But it happened ?

cubandanger05 said:
But it happened ?
Click to expand...
Click to collapse
Yup, somebody saw a mountain and decided to climb it. We'll see what comes of it.

Yeah mokee ROM has treble working on the OnePlus One 5T. There's an unused partition that can be created without re-partition in the device and if you install a regular ROM it doesn't see it you install a treble ready ROM and you previously had mokee installed according to the mokee dev it works. It uses the ab style of treble. There is an "a" and "ab" and "a/b" versions from what I read. Mokee is releasing nightlies of their ROM
Haven't tried it on mine pretty happy with the aicp Oreo that I'm running so I can't tell you what bugs it has. Google it XDA has a discussion on mokee and treble with OnePlus 5t

Question Building AOSP for Red Magic 8 Pro

I'm looking to build AOSP for the Red Magic 8 Pro. Has anyone managed to get the proprietary binaries from Nubia or extract it from the stock firmware?
I have tried searching around for these binaries to no avail. If someone has a download link to share I would really appreciate it. I just want a completely stock android experience and don't mind if not everything isn't working.

Do you really want AOSP or Paranoid Android will do as well? In any case, download OTA here, extract payload.bin and use payload-dumper-go. You can use LineageOS instructions for getting binaries from unpacked .omg files.

aaa.bbb111222 said:
Do you really want AOSP or Paranoid Android will do as well? In any case, download OTA here, extract payload.bin and use payload-dumper-go. You can use LineageOS instructions for getting binaries from unpacked .omg files.
Click to expand...
Click to collapse
Have they already released a ROM for this phone? If not, AOSP builds without most Google trash and I block many of their domains in the hosts file just in case. I did finally find a dump here: https://github.com/RandomPush/nubia_nx729j_dump
Appreciate your help though. I'll post my progress here in case anyone is interested. The android developer documentation says proprietary binaries are usually located in a /vendor partition. Going through the dump now and trying to figure out the bare minimum to get a custom ROM booted.
My guesses are anything Qualcomm related for the SoC. I'm unsure of what baseband/radio chips the phone uses, actually it's been pretty tough to find a good spec sheet on it. Most resources that come up on Google only refer to surface level specs and don't go into much detail on the chips themselves.

No, they haven't, but I've seen people working on it. It would be a bit easier to bring up because PA is CLO-based (not AOSP), so the probability of most stuff working is higher. CLO has some Qualcomm-specific patches. Actually, you can probably build QSSI (like GSI but from CLO) without much difficulties, so this might be the way to go.
I'd recommend that you extract those binaries from OTA anyway as they might be updated in the future. Out of the box you probably won't get working vibration.

With the kernel source released, what's so difficult with building LineageOS and stuff?

SevastianXDA said:
With the kernel source released, what's so difficult with building LineageOS and stuff?
Click to expand...
Click to collapse
We need a good unbricking method just to be on the safe side (personally, I'm not very keen on even trying someone else's build, let alone making my own, simply too much risk). Other than that, a lot of time is needed and there are basically zero good instructions. Once again, LOS isn't the best option for 8g2, would be better to go for Paranoid Android. One can theoretically build QSSI image (basically GSI, but for Snapdragons), might be a good idea for now. Still risky tho

aaa.bbb111222 said:
We need a good unbricking method just to be on the safe side (personally, I'm not very keen on even trying someone else's build, let alone making my own, simply too much risk). Other than that, a lot of time is needed and there are basically zero good instructions. Once again, LOS isn't the best option for 8g2, would be better to go for Paranoid Android. One can theoretically build QSSI image (basically GSI, but for Snapdragons), might be a good idea for now. Still risky tho
Click to expand...
Click to collapse
What are the bricking issues here? Usually even if the ROM is f*cked or just something doesn't work you can always flash back to stock through TWRP.

SevastianXDA said:
What are the bricking issues here? Usually even if the ROM is f*cked or just something doesn't work you can always flash back to stock through TWRP.
Click to expand...
Click to collapse
If only there was a fully working TWRP... Unfortunately, there isn't. Well, kind of. It boots but that's it. And no, sideload simply doesn't work. When I went back to stock on my previous device (1+7 Pro), I had to use MSM Tool. Nothing like that is available for RM8P, ZTE doesn't want to give the tools to us because of bs reasons.

aaa.bbb111222 said:
If only there was a fully working TWRP... Unfortunately, there isn't. Well, kind of. It boots but that's it. And no, sideload simply doesn't work. When I went back to stock on my previous device (1+7 Pro), I had to use MSM Tool. Nothing like that is available for RM8P, ZTE doesn't want to give the tools to us because of bs reasons.
Click to expand...
Click to collapse
Bruuuuhhh, that's stupidd, someone shall reverse engineer the MSM tool to work for the RM8P (sarcasm)

Hmm, as I can see from this post, it seems peeps have managed to actually restore the phone from a full brick..: Post

Edl or its countparts is not a necessity for buiding a custom rom. 1st, a custom rom usually just overwrite the application parts, so in the worst case the user can still restore to factory rom via fastboot commands. 2nd, many manufacturers never release their factory rescue tools (Google, ?) but there are numerous custom roms, even official builds.

Cyanide_zh said:
Edl or its countparts is not a necessity for buiding a custom rom.
Click to expand...
Click to collapse
True, it's more a convenience factor.
Cyanide_zh said:
1st, a custom rom usually just overwrite the application parts, so in the worst case the user can still restore to factory rom via fastboot commands.
Click to expand...
Click to collapse
Or not. In fact, happened to me (Qualcomm crashdump mode or something like that). And if something could go wrong, it will.
Cyanide_zh said:
2nd, many manufacturers never release their factory rescue tools (Google, ?) but there are numerous custom roms, even official builds.
Click to expand...
Click to collapse
Usually those devices have much less ROMs available if any. Just compare 1+9 Pro and 10 Pro.

aaa.bbb111222 said:
less ROMs available if any. Just compare 1+9 Pro
Click to expand...
Click to collapse
Any ROM than the stock would do, just LineageOS would be superb.

SevastianXDA said:
Hmm, as I can see from this post, it seems peeps have managed to actually restore the phone from a full brick..: Post
Click to expand...
Click to collapse
Interesting.. https://romprovider.com/nubia-red-magic-8-pro-plus-firmware-stock-rom/

SevastianXDA said:
Interesting.. https://romprovider.com/nubia-red-magic-8-pro-plus-firmware-stock-rom/
Click to expand...
Click to collapse
sadly, 9008 firmware need pay about 50 USD, But nobody said the package can be used still now.

CrazyMoney said:
sadly, 9008 firmware need pay about 50 USD, But nobody said the package can be used still now.
Click to expand...
Click to collapse
Bruh the custom ROM and modding community is so mid and goofy for the RM8P Literally one of the main things making me go for a Poco F5 instead

Chinese dev made MIUI rom but its only payed with alipay for like 3 dollars. I im waiting when we can pay with paypal to try it looks good.

ibestmoder said:
Chinese dev made MIUI rom but its only payed with alipay for like 3 dollars. I im waiting when we can pay with paypal to try it looks good.
Click to expand...
Click to collapse
Well yeah, but as explained/talked about here, AOSP/LineageOS has to be technically possible

I got the rom maybe extract and check it? Take out alipay security then we can try it

ibestmoder said:
I got the rom maybe extract and check it? Take out alipay security then we can try it
Click to expand...
Click to collapse
Maybe share the ROM file, then we can try finding some way to remove forced payment/crack it (No paid ROMs allowed in XDA forums) and maybe possibly clean it somewhat (Does it even have english as an option?) and we'll finally get ourselves a finally working alternative custom ROM.