Related
I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.
Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.
Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.
IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.
I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium
JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.
Can you make a patch for stock root.
Thx
Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.
soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.
Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!
Attention themers, I would like to (re)draw your attentions to the VillainTheme system that launched earlier this year.
Full information can be found here: http://forum.xda-developers.com/showthread.php?t=1207017
Basically this is a theme system where you make your theme following the above guidelines and update.zip method and then your theme can theoretically be applied on any phone and on any rom.
This should save you a heck of a lot of time in making different versions for different things, and also means that your theme can be used by a far wider range of people.
Please give a lot of consideration to using this.
When it first launched it had quite an impact, but however since then it seems to have been somewhat forgotten, and new themers have missed it altogether.
I am using this for a long time now
Vertumus said:
I am using this for a long time now
Click to expand...
Click to collapse
Yes I was aware you used it, may I suggest you change your thread name to [VRT] rather than just putting VRT in the general name?
This post was more to let other people know, as far as I can see you are the only person to use this system on their s3 themes.
Lennyuk said:
Yes I was aware you used it, may I suggest you change your thread name to [VRT] rather than just putting VRT in the general name?
This post was more to let other people know, as far as I can see you are the only person to use this system on their s3 themes.
Click to expand...
Click to collapse
I will be the second!
I first realised this existed when I came to the SGS3. This is something that had been missing from the HTC desire world. I don't think anyone there knows about this.
IMHO this is a game changer! Great stuff.
If/when I theme, I will definitely use this.
used it myself when I've "converted" other peoples themes to run on my phone Brilliant and simple system which I never understood why more themers havent used
morphed theme packages are really great and time saving, hoping for the themers to adapt it soon via this template
Excellent work guys...
I'm using your flasher for my Themes for 2-3 days now...
Thanks a lot...
Sent from my Note with Mixed Theme
Thanks for your contribution .
The VillanTheme system is pretty neat. Always liked metamorph and this is similar but at the flashable level.
Does the VillanTheme system back up original assets? The reason I ask is if a user flashes a villantheme that applies changes to 10 image assets. The user then flashes another villantheme that only applies changes to 5 of the 10 images that were just changed. Is the user then faced with a mix of two themes as the second theme didn't touch the other assets from the first theme?
Thanks.
thanks for theme
myn said:
The VillanTheme system is pretty neat. Always liked metamorph and this is similar but at the flashable level.
Does the VillanTheme system back up original assets?.
Click to expand...
Click to collapse
It doesn't yet, but I mentioned adding this ability to the Villain Tools App to the dev and he mentioned he has seen it in scripts so there is hope.
I have problems with the latest version.
gs3 32 gb and I do not use external_SD.
no sd no flash theme ...
thanks
io ho problemi con l'ultima versione.
ho gs3 32 gb e non uso la external_SD.
senza sd non flash del tema...
grazie
Thanks a lot!!! Great job!
Lennyuk said:
Attention themers, I would like to (re)draw your attentions to the VillainTheme system that launched earlier this year.
Full information can be found here: http://forum.xda-developers.com/showthread.php?t=1207017
Basically this is a theme system where you make your theme following the above guidelines and update.zip method and then your theme can theoretically be applied on any phone and on any rom.
This should save you a heck of a lot of time in making different versions for different things, and also means that your theme can be used by a far wider range of people.
Please give a lot of consideration to using this.
When it first launched it had quite an impact, but however since then it seems to have been somewhat forgotten, and new themers have missed it altogether.
Click to expand...
Click to collapse
Heck ya. Great concept. I'll by trying this out for sure. I can't stand updating on EVERY ROM BUILD.
I've been looking for a resolution for a while now and I am still no nearer to sorting out my problem with VRT
I'm using VillianROM 1.1.0 LFB and CWM Touch 6.0.1.0. I do exactly this:
Copy zip from PC to phone storage (not external SD card)
Reboot into Recovery.
Clear Cache partition
Clear Dalvik cache
Flash zip from internal SD
Everything is reported as being successful.
Reboot... nothing changes. This is with Vertumus VRT Jelly Bean Domination (which others report as working fine).
The strange thing is, I already have JB Domination flashed on this exact ROM, yet when I tried a clean install (cleared System, data, cache adn preload, etc, in CWM) and installed VillainROM from CWM, booted, set up, rebooted to recovery and flashed JB Domination, it doesn't work.
So, I have a Nandroid backup where it has worked, but now doing a fresh install it doesn't work. And also, on my Nandroid backup (which I use now daily) it doesn't work at all.
No VRT theme will flash to my phone
EDIT:
I've also tried mounting /system and /data before flashing.
seshmaru.... where are ruuuu?
Excellent work guys...
Any chance to update the scrip to make it compatible with CWM 6.0.1.2?
Work well with new recovery.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Hi all.
I just installed Jandycane 1.7.2 on my KF and it's gorgeous, smooth well done praise/praise/praise. I'd like to get Chrome up and running (a large reason for jellybean on this device). It's known to not function - and I tested again on latest version (see: http://forum.xda-developers.com/showthread.php?t=1811376)
That thread recommends two fixes - 1: uninstall Chrome, wipe dalvik and cache, revert to a previous version of jandycane, install chrome, re-flash latest version. This seems to be the easiest fix, but the links in ROM OP of Jandycane http://forum.xda-developers.com/showthread.php?t=1766829 are all dead (Apparently I'm lucky I got it about 4 hours ago), because goo.im seems to be DOA right now for pretty much everything).
So in regard Fix 1 - does anyone have a hosted copy of Jandycane 1.6 or thereabouts that they can host somewhere until goo.im settles down in a few days?
Regarding that thread's other fix, which itself is referencing a post in the ROM's OT: 2: wipe/wipe/wipe, flash jb-kfire-hashcode-07-13, flash gapps, wipe caches again, install Chrome, dirty-flash Jandycane 1.7.1 (assuming works for 1.7.2).
In regard Fix 2 - I also can't find jb-kfire-hashcode-07-13 anywhere, does anyone have a hosted version of this, a version they can host, etc?
Thanks.
Yes replying to myself. I've been a *LONG* time lurker... need my 10.
MrSchroeder said:
Regarding that thread's other fix, which itself is referencing a post in the ROM's OT: 2: wipe/wipe/wipe, flash jb-kfire-hashcode-07-13, flash gapps, wipe caches again, install Chrome, dirty-flash Jandycane 1.7.1 (assuming works for 1.7.2).
In regard Fix 2 - I also can't find jb-kfire-hashcode-07-13 anywhere, does anyone have a hosted version of this, a version they can host, etc?
Thanks.
Click to expand...
Click to collapse
Let me start off by saying, don't hate on me for replying to myself - yes it's for 10count. But I've been lurking here about 2 years and while I haven't found a need to post much, I do now, between a new Nexus 7, and old Huawei Ascend2, 2x Kindle Fires, and probably soon to be a second Nexus, I have questions damnit!
Now on to the jbkfire-hashcode-07-13 : It was originally posted here http://forum.xda-developers.com/showthread.php?t=1765288 and the link leads to droidhive.com which is showing as a dead GoDaddy site. So... yeah.
Is the whole community being effed with when I need them most? Droidhive and goo.im down at the same time, mediafire and dropbox thresholding downloads or simply freezing accounts for 72 hours over traffic, blah.
Some help would be appreciated so I can get the KFs running well for the wife and kids, and I can go back to playing with my Nexus 7.
Thanks.
Since I have too few posts to join the "[DISCONTINUED] Team Venom presents: ViperDHD 2.3.0 | Sense 4.1 | 4.0.4 | Smooth | OTA" thread I have to post here...
Everyone who uses this ROM knows there's been an OTA update message popping up due to supposedly not legit ROM. Caveat is I know I have legit but I am sure much of my updates & tweaks would break whatever is used to validate. Since it is EOL anyway I had chosen to disable the OTA but it didn't seem to stay off.
Fast forward 2 months & I find my phone dead at a blank screen. Reboot, same. Clear cache & Dalvik, reboot, same. Factory reset, same. So I use Ext4 to make a backup & then restore last months image, working again. Interesting is that the name of image made of the faulty ROM contains "unknown" rather than ViperDHD.
So question is: Is whatever OTA update being offered by TeamViper's server FORCING itself onto DHD's now despite not being correct? I mean from what I read we're not supposed to accept the update because it bricks devices yet we're still being alerted over & over to accept the OTA update.
I find it a bit nervy to have a ROM ***** about not be "legal" (I assume point is anti-kang?) over & over when I know I got my image from the official thread AND then if it did force an update that crashed my phone that would be over the line. Concern here is that I will face the same issue again since it's happened once.
bump
Do I need to post a better description? Figured I'd not be the only one hit by this.
Perhaps most people have moved on from 4.0-based ROMS.
Perhaps but there is activity on the ViperDHD thread, I just lack enough posting rank to post there and figured this port would kill 2 birds one stone so to speak.
Not looking for active development and it was fine the way it was until these bum OTA's started up recently.
tlund said:
Perhaps most people have moved on from 4.0-based ROMS.
Click to expand...
Click to collapse
OK, so no takers & no helpful input? Seem this ROM has more than a few serious issues despite having some great features & what would appear to be a serious developer base for the various "Team Venom" ROMs.
Would be nice if they would make one last update to DISABLE their broken OTA check, flawed anti-kang detection, and some the of "tweaks" that simply don't work like umm... the all CPU tweaks or the backlight that lists crazy values? Funny, click donate in Venom Tweaks, crash the app consistently!
Seems a bit drastic that I now need to dig the file system to try and rip out the hooks that enable the above problem "features".
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.