Related
users of the vk810 are currently prepared to fork over $135+ to the Developer that produces a working L build, doesn't have to be 100%, but it needs to have the basics; data, GPS, wifi, etc... Any takers?
BOUNTY SET TO $135!!
Note: I sold the tablet and am no longer in the bounty. Sorry.
@adrianrom
Contact this guy.
Sent from my iPhone using Tapatalk
EdenGottlieb said:
@adrianrom
Contact this guy.
Click to expand...
Click to collapse
who is that? spelling mistake maybe?
cammiso94 said:
who is that? spelling mistake maybe?
Click to expand...
Click to collapse
He's an xda dev that posted great lollipop rom for v500
Sent from my iPhone using Tapatalk
I'd be willing to donate as well. Getting the tablet free. Should be here tomorrow.
I will add $10 if it has working LTE, Wifi, GPS and Bluetooth.
razgriz8426 said:
I will add $10 if it has working LTE, Wifi, GPS and Bluetooth.
Click to expand...
Click to collapse
All of those things should be covered with the $100, we'll just say that we have the bounty set to $110 or so. Anyone want to put on top? Lets get in touch with a developer to get this rolling!
Do u users have a working kitkat tree?
a2441918 said:
Do u users have a working kitkat tree?
Click to expand...
Click to collapse
we have a semi-working CM11 devicetree/kernel ported from the non-LTE model (LTE data/GPS doesn't work, everything else seems to work)
I'm still trying to understand more about kernel development/porting, just not much time to look at it...
http://forum.xda-developers.com/showthread.php?t=2759270
Why do you want Android 5.0 so bad to the point you want to pay money? I'm mean specifically, what in it is such a big deal that you need it NOW?
Why not just go buy a Google Play Edition if you want Lolipop that bad?
There's more to life than obsessing over having the lastest O/S version
Well a bounty is less than a gpe tablet lol. So there's that.
jazee said:
Why do you want Android 5.0 so bad to the point you want to pay money? I'm mean specifically, what in it is such a big deal that you need it NOW?
Why not just go buy a Google Play Edition if you want Lolipop that bad?
There's more to life than obsessing over having the lastest O/S version
Click to expand...
Click to collapse
users of this great, underestimated beast of a tablet, that for some reason LG dumped some unoptimized garbage on to it, then "replaced" it with tablets with WORSE hardware, are really missing out on what this tablet can do. What it needs is a build that will run perfectly on it. Furthermore if it works half as good as it should, it would be better than what LG is currently doing with it.
Lets get a dev to get 4.4 working with radios, and we'll go from there. We may have to wait for a dev to pick up this device, with that; I am also willing to allow the dev my device as a start.
I'll add 50 to it
I would just like to see CM11 or CM12.. The tablet would run so much better.
It's starting to look like a significant amount of people are buying this tablet with the recent promotions by Verizon. I really hope that a dev can pick this up and see if they can get us a working ROM. I'm in the process of prepping a server to do some of my own ROM builds for the LG G3. Wish we had a working base because I don't have the knowledge to do anything but compile the builds.
Even a custom kernel would be nice so we could boost the CPU back to the 1.7 that the other models run at.
I'll kick in $20 for this. Would be nice to be cm12 or even GPE rom with working data (or not at this point).
I just got this tablet from verizon about 2 weeks ago, I dont consider myself a dev in any shape or form but I have done enough to know what can break my device and what cant, a while back I successfully ported a rom to a cheap Chinese tablet I owned a while back, I am going to look into porting a (hopefully) lollipop rom to our VK810, gonna take me some time and who knows if I will even be successful, just wanted to let everyone know someone is trying..... I will let you know if I make any progress....
Prepare your bounties guys !
Development is in full swing. We'd see some love for developers in coming weeks !
I'm wondering.
Since Samsung as of late have been focused on getting everything pushed to Lollipop, do you think we'll see some opinions about an update, or even rumor?
Maybe the full thing, who knows.
im interested too but...... i dont think its ever going to happen. samsung dont seem interested in the device at all anymore.
Given the cameras never even got KitKat it's very doubtful they will get Lollipop
If you ask this to Samsung, I expect them to say this:
"Galaxy Camera?"
"Isn't that that gimmick we released a couple of years ago?"
"An update to lollipop you say? Whahahahaha!"
"No."
But seriously: It never got past 4.1. I seriously doubt they would even consider this device for an update.
Samsung officialy stopped producing the K Zoom and put it EoL
so, no Lollipop or other updates anymore, even for exploit fixing
confirmed: no update
Galaxy camera 2 has stagefright!
Can we get a cyanogenmod build then ?
cantenna said:
Can we get a cyanogenmod build then ?
Click to expand...
Click to collapse
If you can get a seasoned developer to work on it, sure. I set up a device tree for the GC200 at https://github.com/AWildColin/android_device_samsung_sf2wifi six months ago. I was trying to encourage some development on it (*cough* @Decad3nce *sneeze*) by getting a custom recovery working, but everything I built and flashed resulted in black screens and I never found a way to troubleshoot exactly what was causing that to happen.
Frankly, I'm not an experienced enough developer. Maybe with a lot more free time, I might get some where, but a custom recovery is still a far cry from a stable CyanogenMod ROM. You're welcome to try though. https://wiki.cyanogenmod.org/w/Doc:_porting_intro
mjsztainbok said:
Given the cameras never even got KitKat it's very doubtful they will get Lollipop
Click to expand...
Click to collapse
If I'm not mistaken the GalCam1 and GalCamNX never were upgraded from 4.1, and the GalCamNX was an almost $2000 camera. So no, I don't anticipate that Samsung will upgrade to Lolipop.
AWildColin said:
If you can get a seasoned developer to work on it, sure. I set up a device tree for the GC200 at https://github.com/AWildColin/android_device_samsung_sf2wifi six months ago. I was trying to encourage some development on it (*cough* @Decad3nce *sneeze*) by getting a custom recovery working, but everything I built and flashed resulted in black screens and I never found a way to troubleshoot exactly what was causing that to happen.
Frankly, I'm not an experienced enough developer. Maybe with a lot more free time, I might get some where, but a custom recovery is still a far cry from a stable CyanogenMod ROM. You're welcome to try though. https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
Hi m8, did you ever manage to get a working rom for ekgc-200?
cantenna said:
Hi m8, did you ever manage to get a working rom for ekgc-200?
Click to expand...
Click to collapse
Nope. The device tree is still on Github though if anyone wants to mess around.
we really need a Cyanogenmod rom for this camera desperately.. . what people dont seem to realise or care about for some strange reason, this camera has now a nunber of very serious security vulnerability that samsung has not addressed, it is so bad you should not connect to the internet with it.
im going to try to sell mine. pretty pissed with samsung, they never once realeases any security updtes for this camera!
I, for one, am getting frustrated.
The CM 12.1 nightlies for the XT907 have been deteriorating in stability/"bootability" since August, despite a very good run since their introduction in January up through at least July. The September 26 build is what finally broke my RAZR M (with spontaneous crashes and reboots) enough to drive me back to CM 11.
I don't know when it happened, but something broke the builds even further since then. I tried the Nov. 16 and Nov. 21 builds (both with and without an Open Gapps package, and with a completely wiped internal storage in the Nov. 21 test), and in all attempts the first boot would crash to a black screen after the first "app optimization" - and then crash and reboot again in the middle of the boot animation when it retried.
The RAZR M has missed all three CM 12.X snapshot builds thus far, and to my knowledge there's no evidence that it will ever be stabilized enough for a snapshot - let alone get CM 13 builds when they eventually arrive. This bothers me, but what really has my blood boiling is this: as far as I know, there has been no word whatsoever from the device maintainer(s) on the status of the builds or why the device got no snapshots. I don't even feel sure that someone is (actively) maintaining the device at all.
Look, I know this is all supported by developers' unpaid spare time. I don't mean to put that down. (And I'd gladly start rolling my own builds and trying to fix what's wrong, but I lack two major things: the hardware (you try building AOSP or CM on a single-core Celeron with 2 GB of RAM) and the know-how.) But I feel like we (as RAZR M owners) are being left in limbo, with builds that haven't worked decently well in months, no recent snapshot to fall back on, and no word on the future of the device.
("So get a new phone and stop complaining, asshole." If you were thinking that, here's what I'm thinking: I was going to until I learned that Verizon's gonna tack on another damn monthly fee if I renew my contract to get a new subsidized phone. It's not yet in my budget to shrug that off, and the signals around here are not yet good enough to jump ship for another carrier.)
So, developers: if the device is being phased out or won't be supported, okay. Fine. Please tell us, and I will attempt to move on. If honest support is still on the table (especially CM 13), please tell us, even if it will be a while before us users can see the results.
Please don't leave us hanging.
I'm not completely sure, but I believe the maintainer of Blisspop (which is a fork of CM) stated that the razr m would be getting cm13 eventually. As for the instability problems, yeah they're annoying but you don't have to update. Your best option is to find the last build that works, and stick with it. This device is getting pretty old now, so it isn't unusual for the developer support to start disappearing.
As for your budgeting issue, if you're in the U.S. I just thought it would be helpful to let you know that you actually save money if you aren't on a contract with Verizon. If your contract has already run out you should go to the nearest verizon store and they'll apply a $15 dollar discount for every line that isn't contracted.
The only CM dev for the Razr M was dhacker, and he stopped supporting the Razr HD/M a long time ago, he moved on to the Nexus 6.
Other then dhacker, I know that kabladan was supporting CM for the Razr HD, but I don't know if he's still around or willing to support the Razr M.
I know I haven't been much help, but at this point there probably won't be much support for the Razr M anymore. As the device get older people move on.
Have you tried a Verizon MVNO like Page Plus?
I thought those reboots when finishing the app optimization were my fault somehow, And now I know nobody is maintaining this device, great. It's annoying, cause I can't actually upgrade, the economic situation in my country is really, really bad. I would try to maintain this device, but I'm on the school, and then I'll start the University, so I will not have enough free time, and also, my computer sucks and my internet is incredibly slow. I hope someone starts maintaining this device, or that magically a box with a nexus appears in the door of my house.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
BTW, is Blisspop more stable than pure CM? I'm just getting tired of wipe cache, fix permissions or flash the whole ROM over and over again...
HaggisIV said:
Your best option is to find the last build that works, and stick with it.
Click to expand...
Click to collapse
Ah, but there's the rub. Each nightly is only kept for a week or two, and then it's gone. The last build I had good luck with was made almost three months ago.
HaggisIV said:
I'm not completely sure, but I believe the maintainer of Blisspop (which is a fork of CM) stated that the razr m would be getting cm13 eventually.
Click to expand...
Click to collapse
Good news, then. My fingers are crossed that the builds will be at least as usable as the early CM 12.1 ones were (or at least, as I remember them). Maybe it'll be a reasonable last stand.
ATTACK said:
The only CM dev for the Razr M was dhacker, and he stopped supporting the Razr HD/M a long time ago, he moved on to the Nexus 6.
Other then dhacker, I know that kabladan was supporting CM for the Razr HD, but I don't know if he's still around or willing to support the Razr M.
Click to expand...
Click to collapse
Well, crud. I know that someone is building msm8960 CM11 builds with a CM12 kernel (works on the RAZR M), but I doubt anyone would go out of their way to dual-support when it involves a separate build.
ATTACK said:
I know I haven't been much help, but at this point there probably won't be much support for the Razr M anymore. As the device get older people move on.
Click to expand...
Click to collapse
Yeah, I know. It also depends on the phone's popularity (despite having no official support and being older than the RAZR M, the Galaxy Nexus is STILL getting unofficial AOSP/CM builds from multiple developers, including experimental AOSP builds for Android 6.0). I guess the phone fell off the radar too quickly.
ATTACK said:
Have you tried a Verizon MVNO like Page Plus?
Click to expand...
Click to collapse
Not yet. I'm actually on a relative's family plan, which is a little cheaper for me overall. I'd been planning for a while now to renew my contract and get a subsidized 2014 Moto X, but then yesterday I learned of Verizon's freaking absurd determination to push people off contracts ...
Maybe I'll just save up and buy something decent off Swappa. It's gonna take time no matter what.
trivialPotato said:
I hope someone starts maintaining this device [...]
Click to expand...
Click to collapse
I keep hoping against hope that maybe we could convince someone to put in enough work for a last hurrah - just one snapshot or snapshot-quality build (even an AOSP one). But it may never happen.
trivialPotato said:
BTW, is Blisspop more stable than pure CM? I'm just getting tired of wipe cache, fix permissions or flash the whole ROM over and over again...
Click to expand...
Click to collapse
I tried the October 7 build for about a week, but it kept spontaneously rebooting on me; that was the real last straw that led me to running CM 11. Maybe they fixed that in more recent builds, but I wouldn't get my hopes up.
Strife89 said:
Ah, but there's the rub. Each nightly is only kept for a week or two, and then it's gone. The last build I had good luck with was made almost three months ago.
Good news, then. My fingers are crossed that the builds will be at least as usable as the early CM 12.1 ones were (or at least, as I remember them). Maybe it'll be a reasonable last stand.
Well, crud. I know that someone is building msm8960 CM11 builds with a CM12 kernel (works on the RAZR M), but I doubt anyone would go out of their way to dual-support when it involves a separate build.
Yeah, I know. It also depends on the phone's popularity (despite having no official support and being older than the RAZR M, the Galaxy Nexus is STILL getting unofficial AOSP/CM builds from multiple developers, including experimental AOSP builds for Android 6.0). I guess the phone fell off the radar too quickly.
Not yet. I'm actually on a relative's family plan, which is a little cheaper for me overall. I'd been planning for a while now to renew my contract and get a subsidized 2014 Moto X, but then yesterday I learned of Verizon's freaking absurd determination to push people off contracts ...
Maybe I'll just save up and buy something decent off Swappa. It's gonna take time no matter what.
I keep hoping against hope that maybe we could convince someone to put in enough work for a last hurrah - just one snapshot or snapshot-quality build (even an AOSP one). But it may never happen.
I tried the October 7 build for about a week, but it kept spontaneously rebooting on me; that was the real last straw that led me to running CM 11. Maybe they fixed that in more recent builds, but I wouldn't get my hopes up.
Click to expand...
Click to collapse
The last build that "worked" for me is really old, like 4 months old, and with "worked" I mean booting without problems, right now every nightly boots whenever it wants, and if it boots I get some nice ANR when I open apps like Keep, Look of Disapproval, WhatsApp, etc... I would love a full working AOSP build, unfortunately I can't actually build it with 2gb of ram, a 2ghz dual core processor and a 120gb hard drive...
Have you tried Exodus ??
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
Thanks man, I'll try it, I hope I can use Keep without wait 10 seconds till the SystemUI reboots.
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
Thanks for the suggestion. I tried it last night, but alas: not even eight hours in, I got a dreaded spontaneous reboot (I pulled the phone out of my pocket to send a message, and found it in the middle of the boot animation). I had the exact same apps installed (save for the Gapps package, of course; I used a Micro Open Gapps package) as my CM 11 installation, which has yet to reboot in that way.
Attached is the output of /proc/last_kmsg, which I dumped to the microSD card before restoring my CM 11 image.
Strife89 said:
Thanks for the suggestion. I tried it last night, but alas: not even eight hours in, I got a dreaded spontaneous reboot (I pulled the phone out of my pocket to send a message, and found it in the middle of the boot animation). I had the exact same apps installed (save for the Gapps package, of course; I used a Micro Open Gapps package) as my CM 11 installation, which has yet to reboot in that way.
Attached is the output of /proc/last_kmsg, which I dumped to the microSD card before restoring my CM 11 image.
Click to expand...
Click to collapse
Thats weird, I'll stick with it, its working perfectly fine for me, I only experienced a reboot when started recording the screen, but that happened with CM anyway. I haven't got a single SystemUI reboot, ANR exceptions or anything. I'll check your log to see if I find something, but you should try formatting your sd card (if you have one on it).
beeewell said:
Since I ran into some instability with BlissPop about a month ago, I've tried and have been using Exodus. I keep up with the (every other) nightlies and the ROM is performing well and has been pretty stable for me. It's less customizable and doesn't have nearly as many built-in features as BlissPop, but I'm happy with how it performs. For more info, see link below:
http://forum.xda-developers.com/droid-razr-m/orig-development/rom-team-exodus-xt907-t3135848
Click to expand...
Click to collapse
works fine not given me problems
When I'm back at work I will attempt to build CM13 for xt907 and just see how bad it goes. I'm not opposed to putting some work in, but with holidays coming up I will be traveling and I also have some large projects due for my senior CSCI project. I do think that the RAZR M is probably approaching end of life as far as software support, as sad is that is.
Sent from my XT1095 using Tapatalk
Nifty.
It would be funny out of a note 3, droid turbo, HTC m8, tab4, and tab 2 that my razrm gets marshmallow first.
Looks like my turbo may be getting it very soon as well.
Sent from my XT1254 using XDA Free mobile app
BlissPop
I tried CM12 in June & July and had nothing but instability. BlissPop has been perfect since August (after some minor regressions in July). Personally, I've found that I enjoy BlissPop on the Razr M more than I enjoy CM12 on my tablets. The only issue I have with BlissPop is that if my phone dies the first time I boot up it can't find my SIM card. But a reboot fixes that .
rockon999 said:
I tried CM12 in June & July and had nothing but instability. BlissPop has been perfect since August (after some minor regressions in July). Personally, I've found that I enjoy BlissPop on the Razr M more than I enjoy CM12 on my tablets. The only issue I have with BlissPop is that if my phone dies the first time I boot up it can't find my SIM card. But a reboot fixes that .
Click to expand...
Click to collapse
That happened me with both CM12.1 and Blisspop.
trivialPotato said:
That happened me with both CM12.1 and Blisspop.
Click to expand...
Click to collapse
How about your cm13?
EzraDi said:
How about your cm13?
Click to expand...
Click to collapse
I haven't tried it cause I haven't found any builds for KKBL, and I dont feel like going back to JellyBean. xd
trivialPotato said:
I haven't tried it cause I haven't found any builds for KKBL, and I dont feel like going back to JellyBean. xd
Click to expand...
Click to collapse
I wanna try cm13 too but I find going back to jb very tedious!
Latest CM12.1 Nightly Build Working Fine.
2016-05-23
I have two Droid Razr M’s both running CM12 for about two years. I just tried to downgrade to JBBL so I could try CM13. No luck, had a boot loop after flashing the JBBL recovery. So I RSD’d back to KK and then to my backup of CM12. When I find a CM12 that works real great, (most have been for the last year) I make a backup. My backup is 05/09. I have updated both phones to 06/27 and they are both running great, no data drops and all my Bluetooth stuff works fun. I hope in the future we can upgrade to CM12 with the KK recovery. These legacy phones are great with the bootloader unlocked.
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
tele_jas said:
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
Click to expand...
Click to collapse
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
mhodak said:
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
Click to expand...
Click to collapse
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
xgerryx said:
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
Click to expand...
Click to collapse
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
mhodak said:
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
Click to expand...
Click to collapse
My thoughts are differently, base on the many issues people are running when trying to get back to stock and the fact they there's 2 B20 versions around (B20 Stock & B20_boot) make things a Little harder to do, like for sample,
I have the B20_boot version and as you can see I uploaded a backup with Xposed debloated and Rooted (I can consider that backup/ Custom ROM) but stock B20 can't use that backup as far as I know... I can easily release a flash able zip base on my backup but (Xposed,Debloated,rooted) but I bet only 5% of the user are using b20_boot.
So till find a way or just way till ZTE release a firmware image we are going to be little stuck with just CM which is getting more stable every day/week
xgerryx said:
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
Click to expand...
Click to collapse
First, the Moto X Pure was widely available. It was not shipped out in smaller batches once a month. When it was released, it was available for everyone to purchase. For the Axon 7, the first batch and second small batches of phones sold out during pre-order, and the third batch hasn't even shipped yet. (and it hasn't received a wide release in Europe yet either, think they just had one small batch)
Also, the Moto X Pure had bootloader unlock available at launch. The Axon 7 did not get a bootloader unlock method until August 11th, less than a month ago. (and at this time, there is no bootloader unlock for the European or Chinese models, just the North American model)
And just as a reminder, the Moto X Pure launched in early September. Dev for CM12.1 started in late September. The first custom ROM, an alpha of CM12.1, was released a month later, in the beginning of October.
You're a power user. Can the Moto Z2 Force keep up? Rate this thread to express how "healthy" the development scene is for the Moto Z2 Force. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
its only just begun
Midnight_Rider said:
its only just begun
Click to expand...
Click to collapse
Agreed
Future looks good,!
Considering the US Snapdragon S8/S8+/Note 8 and US carrier LG V30 do not have bootloader unlock yet, the Moto Z2 Force has development potential. The reason I got the Moto Z2 Force was bootloader unlockability with T-Mobile! I was so sick of US Snadragon S8+ bootloader lockdown, I got a 2nd phone that I could actually compile custom kernels for!
Exactly ?
this phone has finally pulled me out of the wood works and i am officially working on this device and no longer am going to lurk on xda. i have been building android for years and want to try to provide more to the community that has given so much to me already. i have a t-mobile unit i do not use and a at&t one i have as my daily driver. im ok with bricking both devices for this to progress forward.
i am working on building a few roms unofficially from a few sources as of now Resurrection remix boots but has far too many bugs to put in the wild. before anyone asks no i am not sharing until i have direct permission and a git setup for the entire build.
Kaesberg said:
this phone has finally pulled me out of the wood works and i am officially working on this device and no longer am going to lurk on xda. i have been building android for years and want to try to provide more to the community that has given so much to me already. i have a t-mobile unit i do not use and a at&t one i have as my daily driver. im ok with bricking both devices for this to progress forward.
i am working on building a few roms unofficially from a few sources as of now Resurrection remix boots but has far too many bugs to put in the wild. before anyone asks no i am not sharing until i have direct permission and a git setup for the entire build.
Click to expand...
Click to collapse
Cool deal bro, welcome to the show lol looking forward to more devs on this device and more roms to play with.
I am getting one of my at&t models replaced so once the rma for it shows up I'm going to try to get a root method on it and will not have to worry about bricking it since it already is getting replaced for the sound issues it has. stay tuned if i make progress i will update everyone.
Kaesberg said:
I am getting one of my at&t models replaced so once the rma for it shows up I'm going to try to get a root method on it and will not have to worry about bricking it since it already is getting replaced for the sound issues it has. stay tuned if i make progress i will update everyone.
Click to expand...
Click to collapse
PM invisiblek. He has a blank flash but requires some trickery to get done. He borked the bootctrl hal and got his device up and running with it.
Uzephi said:
PM invisiblek. He has a blank flash but requires some trickery to get done. He borked the bootctrl hal and got his device up and running with it.
Click to expand...
Click to collapse
awesome thank you i will contact him once my replacement shows up.