I've tries latest v65-sdk22 and it doesn't want to install in twrp. Sdk21 version just bootloops or freezes at bootup. Any ideas?
It has its in download. Beta.
Moody66 said:
It has its in download. Beta.
Click to expand...
Click to collapse
not very clear information. please explain?
I'm pretty sure there is no version that is compatible with our HAM2 on Lollipop, yet.
Perhaps we have to modify the build.prop again?
Which reminds me, I still have yet to root my phone.
I have tried the build prop theme changes and about everything I can think of ...both versions for 5.1 hang at boot.
It took forever for xposed to come out for Lollipop because that's when Android made the official jump from Dalvik to ART. Then it appears that certain manufacturers modify the ART runtime on top of that.
It looks like Huawei is one of those companies. Samsung also did it, but they have such a huge fan base that they had a dev that came up with a work around. It's possible that someone will do the same for Huawei eventually, probably for another phone or tablet that could possibly work for us, but I wouldn't hold your breath.
ArkAngel06 said:
It took forever for xposed to come out for Lollipop because that's when Android made the official jump from Dalvik to ART. Then it appears that certain manufacturers modify the ART runtime on top of that.
It looks like Huawei is one of those companies. Samsung also did it, but they have such a huge fan base that they had a dev that came up with a work around. It's possible that someone will do the same for Huawei eventually, probably for another phone or tablet that could possibly work for us, but I wouldn't hold your breath.
Click to expand...
Click to collapse
I looked into it and it will prevent booting. Likely to do with emui. Tom is waiting on kernel source so he can make a stock rom. Xposed will then work. Patience is key.
Stock rom? As in, AOSP? Or what?
ArkAngel06 said:
Stock rom? As in, AOSP? Or what?
Click to expand...
Click to collapse
CyanogenMod, which is close to AOSP.
Anyway, eye candy aside, I think this update is pretty crap. I thought things were supposed to be ironed out in the, uh, beta.
Sent from my MT2L03 using XDA Free mobile app
Anyway, eye candy aside, I think this update is pretty crap. I thought things were supposed to be ironed out in the, uh, beta.
Click to expand...
Click to collapse
I've also noticed that if the headphone jack is removed when some audio is playing, sound does not automatically transfer to the speakers. I really hope Tom will find some time to port CM to the HAM2. Its been 7 months since his github page was last updated !
---------- Post added at 02:41 AM ---------- Previous post was at 02:38 AM ----------
Whilst on the topic of xposed, does anyone share my predilections for Kitkat over Lollipop ? Everything seems to work on Kitkat !!
medwatt said:
I've also noticed that if the headphone jack is removed when some audio is playing, sound does not automatically transfer to the speakers. I really hope Tom will find some time to port CM to the HAM2. Its been 7 months since his github page was last updated !
---------- Post added at 02:41 AM ---------- Previous post was at 02:38 AM ----------
Whilst on the topic of xposed, does anyone share my predilections for Kitkat over Lollipop ? Everything seems to work on Kitkat !!
Click to expand...
Click to collapse
Yes, in fact, I tried to go back, but my internal sd card is broken on anything prior to Lollipop now. So I'm stuck.
Tom was originally going to make KK first. Maybe with the new kernel release he can out something together.
WHat ?
Yes, in fact, I tried to go back, but my internal sd card is broken on anything prior to Lollipop now. So I'm stuck.
Click to expand...
Click to collapse
@ArkAngel06 are you saying that once we update to lollipop we can't go back, or is it that the internal stroage does not get formatted back to the way it was w/ JB ?
TIA Davinci
@ArkAngel06 are you saying that once we update to lollipop we can't go back, or is it that the internal stroage does not get formatted back to the way it was w/ JB ?
TIA Davinci
Click to expand...
Click to collapse
Anyone elses quote/multi quote and other buttons missing on XDA???
Anyways, I tried to do it the lazy way and it doesn't work and it breaks my internal SD card. I tried to do it the official way and install just fails.
You may have better luck.
@medwatt people keep mentioning a KK build....B148 is the only build I ever see prior to b309, but b148 is JB, so what build is KK? I have always been on 4.3 prior to 5.1.
@ArkAngel06
My quote buttons gone as well, I just got caught up on your other thread discussing this all.
Won't the new twrp 2.8.7.3 L take care of this with the new check script?
keep us updated I'm working 16 hrs x 3 days so no real play time.
Tomorrow I might attempt a 4.3 downgrade. Getting real tired of the bugs, and I dearly miss Viper and Xposed. I have root but didn't flash TWRP so hopefully the official way will work.
Today I even did a factory reset but it seems to have made things worse somehow.
Sent from my MT2L03 using XDA Free mobile app
@ArkAngel06
My quote buttons gone as well, I just got caught up on your other thread discussing this all.
Won't the new twrp 2.8.7.3 L take care of this with the new check script?
keep us updated I'm working 16 hrs x 3 days so no real play time.
Click to expand...
Click to collapse
I am using the new unified TWRP, here is what I have tried, with the outcomes.
Use unified TWRP to restore a JB backup I made before LP>>>Won't boot, just boots TWRP over and over.
Use unified TWRP to install Xordos' b148 flashable>>>Boots, but internal SD card is unwritable.
Use old JB version of TWRP to install Xordos' b148 flashable>>>Same as unified TWRP, broken internal SD
I also had a lot trouble doing the official downgrade. Most of the problem was me not reading the instructions, and thinking I just had to throw the b148 dload/update.app on my sdcard, but there is alittle more to it than that. Also, i think you need to have the newest stock recovery installed. I tried it with TWRP installed, obviously it loaded TWRP instead of the stock recovery and failed. I then flashed a stock recovery that I had on my PC, thought it was the new one but I could be wrong, but that also failed. So I just did a full official LP upgrade again with the LP update.app, that gives you all the right stuff and I was then able to do the official downgrade.
I just did that like 5 minutes ago and it appears to be working! So, it looks like its going to be a loooong process going from LP to JB, or vice versa. Wish you could just use TWRP, but I don't think you can.
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Tomorrow I might attempt a 4.3 downgrade. Getting real tired of the bugs, and I dearly miss Viper and Xposed. I have root but didn't flash TWRP so hopefully the official way will work.
Today I even did a factory reset but it seems to have made things worse somehow.
Click to expand...
Click to collapse
You know, Viper works on Lollipop? You have to install busy box, install the viper driver, disable low power audio, and start the app after every reboot, but it works!
Sigh. OK I will get the step daughters CC and make a flashable rom.zip from it. Didn't really want to go back to messing with roms much but it looks like there is a need. Can't do it tonight I have a sick 3 year old. I will tomorrow. Maybe afterwards I can make a flashable L zip to make going back and forth easier. Haven't done the L flash yet... But looks like cake walk. Sadly it will overwrite anything you have on the phone.
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Ark, from what I have looked at xposed will not work with emui lollipop.
You know, Viper works on Lollipop? You have to install busy box, install the viper driver, disable low power audio, and start the app after every reboot, but it works!
Click to expand...
Click to collapse
Do you think the Viper driver will fix my stupid audio cutting out bug? If it will, then maybe I'll stay with 5.1.
Edit: Actually, thanks for reminding me. I hate the whole "start apps on boot manually even though it says start on boot" thing.
Related
PLEASE DO NOT USE THIS POST TO REPORT BUGS!
My work:
Fixed/added to the next build:
AOKP: Hadrware button key function.
DU: Nothing for now.
BAM: Nothing for now(need feedback about the lastest build).
Need to be fixed or repaired
AOKP: nothing.
DU: GPS(I tried an ORIGINAL build for i9300 and didn't work).
OMNI:I decided to build lollipop.
AOSP: all repos has been downloaded.
important update!!!!
I WILL FINISH AOKP FIRST, THEN I'LL BUILD DU, AND A LAST BUILD FOR AOSB, AND THEN LOLLIPOP, AND THEN I'LL SUPPORT ALL THE ROMS TO LOLLIPOP.
PLEASE BE PATIENT
FEEDBACK
I NEED FEEDBACK ABOUT ROOT ON SLOT STOCK
If anyone try the rom on stock tell me please, maybe this is the big problem that my roms have
I have asked this question elsewhere, but I am still unsure of the answers. I have never installed a ROM to my stock slot. I know some people feel it makes the phone run faster, but I haven't seen a need. I honestly haven't found any ROM (ever.... On any phone) that is 100% perfect, so I wouldn't chance messing up my phone.
I have 4 slots available on SafeStrap. 3 are actually "set up". Not truly enough room to create a 4th. But I know, no matter how dreadful a ROM can be, my phone will be usable by booting into the stock side.
---------- Post added at 06:15 PM ---------- Previous post was at 06:09 PM ----------
I don't touch the stock slot at all, except to install Titanium and freeze apps I will NEVER use. (Let's Golf comes to mind...) On ROMs I install, I actually remove apps I don't need or use, rather than freeze them.
For those who do run custom ROMs on stock side, are they much better? What happens if phone doesn't boot? Thanks in advance!
sherri said:
I have asked this question elsewhere, but I am still unsure of the answers. I have never installed a ROM to my stock slot. I know some people feel it makes the phone run faster, but I haven't seen a need. I honestly haven't found any ROM (ever.... On any phone) that is 100% perfect, so I wouldn't chance messing up my phone.
I have 4 slots available on SafeStrap. 3 are actually "set up". Not truly enough room to create a 4th. But I know, no matter how dreadful a ROM can be, my phone will be usable by booting into the stock side.
---------- Post added at 06:15 PM ---------- Previous post was at 06:09 PM ----------
I don't touch the stock slot at all, except to install Titanium and freeze apps I will NEVER use. (Let's Golf comes to mind...) On ROMs I install, I actually remove apps I don't need or use, rather than freeze them.
For those who do run custom ROMs on stock side, are they much better? What happens if phone doesn't boot? Thanks in advance!
Click to expand...
Click to collapse
@sherri at the beginning of my newbie flasher time, I never flashed the stock slot (using bmm and always slot 1). The only reason using stock slot is to get more internal free space.
I cant tell the difference but in several occasion I do feel wind of change in term of ui response.
But always keep in mind to ensure that the stock slot is loaded with ROM before reboot to system. If you were accidentally wipe the stock slot and forget to flash rom in it, you brick your phone.
I have my lesson in hard ways (three times of bricking my xt910)
tonyt. said:
I NEED FEEDBACK ABOUT ROOT ON SLOT STOCK
If anyone try the rom on stock tell me please, maybe this is the big problem that my roms have
Click to expand...
Click to collapse
Okay @tonyt. count me in. I'll test AOKP and DU and report you about root on slot stock
DU UPDATE
TORCH and Bluetooth now fully working, Trying to Fix toggle 3g/2g
Q&A for [ROM] Stock ZV6 Base - Odex & Deodex
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Stock ZV6 Base - Odex & Deodex. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can this be flashed over my current setup?
Yup. And you can restore back if you want. The only thing that sticks is the modem
Again thanks for all the hard work. Really love the work you do.
OK so I made the leap and dirty flashed this over my current setup. Now I'm having issues with gmail fc'ing. So I uninstalled it thinking that may help. So I tried to install it from the play store and it says "incompatible update"??? Now I can't even sideload it as it tells me " application not installed". Any ideas as to why its doing this?
---------- Post added at 12:59 PM ---------- Previous post was at 12:47 PM ----------
OK so something weird just happened... I went into recovery to fix permissions to see if that would help and gmail was somehow reinstalled... Its still not working but weird.
---------- Post added at 01:04 PM ---------- Previous post was at 12:59 PM ----------
Disregard my previous posts. Its working now.
I'm really liking the ZV6 update! The ROM is smooth and no lag noticed. I was able to pick up cell signal quickly. Great Job!
I flashed this ROM, updated PRL/Profile and then flashed Sac 2. How can I verify that the modem stuck?
klarthur said:
I flashed this ROM, updated PRL/Profile and then flashed Sac 2. How can I verify that the modem stuck?
Click to expand...
Click to collapse
Go to Settings>About>Software. There will be 2 lines of numbers for the modem now.
It'll stick as Sacs doesn't include kernel or modem.
engine95 said:
Go to Settings>About>Software. There will be 2 lines of numbers for the modem now.
It'll stick as Sacs doesn't include kernel or modem.
Click to expand...
Click to collapse
I have two lines for Baseband. Would that be the same thing as the modem? Thank you for your time!
klarthur said:
I have two lines for Baseband. Would that be the same thing as the modem? Thank you for your time!
Click to expand...
Click to collapse
You got it.
A couple of questions. I have bump and twrp installed and rooted on zv4, everything else is stock, except the kernel. I flashed the oversharpening fix kernel. Can I apply this zv6 update to my phone without wiping data and keeping the fixed kernel? Also, should I download the odex or deodexed?
bryster126 said:
A couple of questions. I have bump and twrp installed and rooted on zv4, everything else is stock, except the kernel. I flashed the oversharpening fix kernel. Can I apply this zv6 update to my phone without wiping data and keeping the fixed kernel? Also, should I download the odex or deodexed?
Click to expand...
Click to collapse
You can probably dirty flash. But you will lose the kernel.
Obviously my recommendation is to start from scratch as there's enough changes/fixes in this update to give you issues.
On the odexed vs deodexed, you can Google it for a better explanation. But the simple answer is: Deodexed is way easier to Theme. But Odexed is said to run a bit faster/smoother because it caches the apps. If I remember that right.
Really the choice is up to you. If you want to Theme it, then you'll need deodexed.
engine95 said:
You can probably dirty flash. But you will lose the kernel.
Obviously my recommendation is to start from scratch as there's enough changes/fixes in this update to give you issues.
On the odexed vs deodexed, you can Google it for a better explanation. But the simple answer is: Deodexed is way easier to Theme. But Odexed is said to run a bit faster/smoother because it caches the apps. If I remember that right.
Really the choice is up to you. If you want to Theme it, then you'll need deodexed.
Click to expand...
Click to collapse
I dirty flashed the deodexed version and when i booted the phone up, i keep getting com.android.systemui has stopped, and I can't do anything with the phone. Any fix in mind? For reference, my dpi was changed, so that may be the issue, i'm not sure
bryster126 said:
I dirty flashed the deodexed version and when i booted the phone up, i keep getting com.android.systemui has stopped, and I can't do anything with the phone. Any fix in mind? For reference, my dpi was changed, so that may be the issue, i'm not sure
Click to expand...
Click to collapse
Clean install.
If you used an app to change DPI, then that's probably the issue. You need to wipe data also.
If through the build.prop, then it should've been OK.
You might be able to dirty flash the odexed as that's like factory.
Again, were taking about a factory update so it really should be a clean install.
Anyone having issues with Android Wear and ZV6? When connected to my Moto360 I get running sync loop. The only thing I haven't tried is resetting the phone and watch.
Since the update is already signed by LG, we should be able to use flashify if we have stock recovery and rooted. Is that correct? I know that I should bump TWRP, but I was holding off till lollipop. Just looking to do a dirty flash.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
Since the update is already signed by LG, we should be able to use flashify if we have stock recovery and rooted. Is that correct? I know that I should bump TWRP, but I was holding off till lollipop. Just looking to do a dirty flash.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
I know Flashify has had issues in the past with these Roms. That's why I recommend doing it in TWRP.
If you have TWRP already why Bump it again?
Maybe I'm misunderstanding.
Edit. I wouldn't think stock recovery would flash this. It's using bits and pieces of ZV6 but not all of it.
And I think the updater-scipt would make it fail. I may be wrong though.
engine95 said:
I know Flashify has had issues in the past with these Roms. That's why I recommend doing it in TWRP.
If you have TWRP already why Bump it again?
Maybe I'm misunderstanding.
Click to expand...
Click to collapse
I'm stock recovery and rooted. Since I haven't bumped TWRP, I thought I could flashify and avoid the 5 second TWRP delay issue by holding off on a custom recovery until we get the stock rooted version of lollipop. You and autoprime have always given solid advice and as such I will take your suggestion.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
I'm stock recovery and rooted. Since I haven't bumped TWRP, I thought I could flashify and avoid the 5 second TWRP delay issue by holding off on a custom recovery until we get the stock rooted version of lollipop. You and autoprime have always given solid advice and as such I will take your suggestion.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
And again, I'm outta Thanks, so Thank you.
The 5 sec delay I talked about has disappeared for me now. But then I've flash about a million Roms in the last few days.
Others aren't getting the delay at all.
I guess what I'm saying is you don't need to reflash Bump TWRP. It works just fine. Even if you get that slight delay. Eventually it'll go away.
Edit. Get TWRP installed now. Have some fun with whatever Rom you want to try. Personally I'm not expecting Lollipop til next year. If it happens sooner great.
engine95 said:
Get TWRP installed now. Have some fun with whatever Rom you want to try. Personally I'm not expecting Lollipop til next year. If it happens sooner great.
Click to expand...
Click to collapse
I will get TWRP and have some fun when I get back. I'm traveling right now, so I'd rather be at home if something goes awry.
Sent from my LGLS990 using XDA Free mobile app
http://forum.xda-developers.com/sprint-galaxy-s5/development/stock-rom-nkd-android-l-odexed-t2956579
Seems they have a test build overe here for 5.0 what would we have to do to flash this to ours? Anyone tried making it work yet?
It would need to be a ported Rom with the libraries needed for out radio instead.
Afraid you will need to wait until someone makes a custom Rom
I'm about to ditch this S5 t-mobile. It looks like we're not getting the update to lollipop any time soon. It's bull they're getting it everywhere but the SM-G900T version. I may be a little harsh and a cry baby but this is just getting nuts. 4.4.2 just runs like crap force closes apps closing. Even on custom rom that are good roms but there's still issues. Enough is enough time to go to the nexus line. J.S
Sent from my SM-G900T
beachbum40 said:
I'm about to ditch this S5 t-mobile. It looks like we're not getting the update to lollipop any time soon. It's bull they're getting it everywhere but the SM-G900T version. I may be a little harsh and a cry baby but this is just getting nuts. 4.4.2 just runs like crap force closes apps closing. Even on custom rom that are good roms but there's still issues. Enough is enough time to go to the nexus line. J.S
Sent from my SM-G900T
Click to expand...
Click to collapse
I'm glad it's coming. It seems like they are just doing a good qc on it. I'd be more upset if we were not getting it at all.
The CM based lolipop roms are running very well toto
JackieBrown said:
I'm glad it's coming. It seems like they are just doing a good qc on it. I'd be more upset if we were not getting it at all.
The CM based lolipop roms are running very well toto
Click to expand...
Click to collapse
Well that is true I suppose. I'm just impatient?
Sent from my SM-G900T
From what I understand, Samsung's currently testing 5.0 on the T-Mobile, AT&T, and Sprint S5's. They started it about two or three weeks ago.
Supposedly, the Note 4 / Note Edge testing will start next week.
Yeah.
Samsung looks like they are being fairly aggressive to get this update out.
I think this is another way they are trying to compete with Apple devices.
They want their updates to go through as quickly as possible.
I have no desire to update to LP personally, I enjoy the ability to customize everything about my ROM. If I didn't have a rooted phone, or want one, then sure I'd update to LP. No Xposed, and all the annoyances of having TW? No thanks.
stealthee said:
http://forum.xda-developers.com/sprint-galaxy-s5/development/stock-rom-nkd-android-l-odexed-t2956579
Seems they have a test build overe here for 5.0 what would we have to do to flash this to ours? Anyone tried making it work yet?
Click to expand...
Click to collapse
I just saw this post and was surprised that nobody has put up a 5.0 test build. I just put one together based on the G900F Polish 5.0 release. I will upload if someone would like to test it. I have a G900A so can't test for myself.
---------- Post added at 09:42 PM ---------- Previous post was at 09:02 PM ----------
muniz_ri said:
I just saw this post and was surprised that nobody has put up a 5.0 test build. I just put one together based on the G900F Polish 5.0 release. I will upload if someone would like to test it. I have a G900A so can't test for myself.
Click to expand...
Click to collapse
Here is the test build. Use the latest TWRP, perform a full wipe then flash and let everyone know if it boots up. Flash at your own risk!:
G900F_NL2_Stock_Rooted_Test_ROM.zip
Im also stealthee . I will try it out soon as my phone charges here at work.
muniz_ri said:
I just saw this post and was surprised that nobody has put up a 5.0 test build. I just put one together based on the G900F Polish 5.0 release. I will upload if someone would like to test it. I have a G900A so can't test for myself.
---------- Post added at 09:42 PM ---------- Previous post was at 09:02 PM ----------
Here is the test build. Use the latest TWRP, perform a full wipe then flash and let everyone know if it boots up. Flash at your own risk!:
G900F_NL2_Stock_Rooted_Test_ROM.zip
Click to expand...
Click to collapse
you mean to flash it on TMOBILE S5???
Yes and it did not work. It flashed just fine. It just stayed at the galaxy s5 screen and then eventually rebooted itself back into recovery mode. I even tried flashing a 4.4.2 kernel to see if it would boot .
j71rivera said:
Yes and it did not work. It flashed just fine. It just stayed at the galaxy s5 screen and then eventually rebooted itself back into recovery mode. I even tried flashing a 4.4.2 kernel to see if it would boot .
Click to expand...
Click to collapse
Thanks for trying, the Sprint leak requires the 5.0 bootloader in order to boot. I suspect the bootloader is also required with this build Anyway, thanks for testing.
Ive yet to update to the NK2 but that would still be 4.4.2 and not 5. and since 5 is not out it would be impossible to update to the 5.0 BL.
Hello Ladies and Gents,
I threw together a flashable rom based off the newest update for the m9 dev edition.
This runs perfectly on the regular AT&T Variant since they are the same hardware just have minor differences.
Rom Features
-1.32.617.30 base (reverted to the old base because of calling issues)
-Odex'd (not sure why HTC still does it since ART doesn't need it)
-Rooted with SuperSU
-BusyBox
Download
I might do a little cleaning up (removing boot sound and some other stuff) let me know if you'd be interested in that.
Credits and Thanks
@OMJ @Captain_Throwback for the updater script
@clsA for the firmware and system.img that I broke apart for this zip
mine
Awesome! Thanks a ton!
Sent from my HTC One M9 using Tapatalk
How do you flash this? Is this possible to flash with S-on??
This uses a "camera-fix" base - if I flash it to my non-camerafix-ota'ed AT&T M9, will I effectively have a camera-fixed phone and be able to skip the OTA? Or does the OTA fix lower level firmware images of the camera, etc? What would happen if I flashed this on my non-ota'ed 1.32.401.15 phone?
basedboii said:
How do you flash this? Is this possible to flash with S-on??
Click to expand...
Click to collapse
Flash via twrp and you'll be fine, it might give a message about not being able to mount /system but that's a normal thing because the system is read only.
It will work with s-on because its just the system and boot partitions, OTAs won't work on it though obviously.
The North American unlocked and developer editions are the same as our phone just different firmware.
kertong said:
This uses a "camera-fix" base - if I flash it to my non-camerafix-ota'ed AT&T M9, will I effectively have a camera-fixed phone and be able to skip the OTA? Or does the OTA fix lower level firmware images of the camera, etc? What would happen if I flashed this on my non-ota'ed 1.32.401.15 phone?
Click to expand...
Click to collapse
I wouldn't do it, you're asking for bootloops, different software versions
I have the Sky Dragon dev edition -1.32.617.30 based ROM on my AT&T M9 and it works fine. I did make a nandroid backup of my stock ROM just in case it didn't work.
Cool, I tested this on my unit as well.
Like I said it's the same exact hardware, just slightly different firmware
Thanks for your work man!
thoughtlesskyle said:
Hello Ladies and Gents,
I threw together a flashable rom based off the newest update for the m9 dev edition.
This runs perfectly on the regular AT&T Variant since they are the same hardware just have minor differences.
Rom Features
-1.32.617.30 (camera fix) base
-Odex'd (not sure why HTC still does it since ART doesn't need it)
-Rooted with SuperSU
-BusyBox
Additional Changes
-NFC icon removed (if you really want it back Customize/ACC/Default, look for "Show NFC Icon" change from 0 to 1)
Download
I might do a little cleaning up (removing boot sound and some other stuff) let me know if you'd be interested in that.
Credits and Thanks
@OMJ @Captain_Throwback for the updater script
@clsA for the firmware and system.img that I broke apart for this zip
Click to expand...
Click to collapse
Confirmation number: 74993903860206517
mspayde said:
Confirmation number: 74993903860206517
Click to expand...
Click to collapse
What?
Sorry to ask this guys but how did u all get twrp on the m9 att? Every time I tried to flash twrp it gives me errors saying it can't write because system is S-ON?
basedboii said:
Sorry to ask this guys but how did u all get twrp on the m9 att? Every time I tried to flash twrp it gives me errors saying it can't write because system is S-ON?
Click to expand...
Click to collapse
You have to unlock via htc dev, then flash twrp
use the beta version of twrp as well. Then you can make a backup of your stock system .
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
thoughtlesskyle said:
Cool, I tested this on my unit as well.
Like I said it's the same exact hardware, just slightly different firmware
Click to expand...
Click to collapse
Are you able to receive phone calls? I just realized I am not but of course Im on a different ROM, I just want to see if it is the firmware thing or not.
sdotagain said:
use the beta version of twrp as well. Then you can make a backup of your stock system .
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Are you able to receive phone calls? I just realized I am not but of course Im on a different ROM, I just want to see if it is the firmware thing or not.
Click to expand...
Click to collapse
Solid question, I'll have to test when I get home. Is it just fc or doesn't connect
thoughtlesskyle said:
Solid question, I'll have to test when I get home. Is it just fc or doesn't connect
Click to expand...
Click to collapse
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
sdotagain said:
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
Click to expand...
Click to collapse
I'll flip my sim when I get home
sdotagain said:
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
Click to expand...
Click to collapse
Just tested and it works here
thoughtlesskyle said:
Just tested and it works here
Click to expand...
Click to collapse
Cool. I'm gonna flash this one then. Thanks.
Someone needs to check and see if VoLTE works with the Developer Edition, on the M8 it did not work... Just a thought. since ATT builds are differently configured thought id throw that out there for those in a VoLTE area.
I received the 6.0 update tonight. ~788MB download and 20 minute install.
Things I noticed differently:
-Response and fluidity seem better, might be due to it clearing the app cache
-Notification bar is smaller, this is a plus for me
-Messages in the message app are smaller, this is a big plus for me
-Everything LG wise has a more flat material design to it. Looks better than before but still iffy
Will update in the future about the battery usage.
2kool4u526 said:
I received the 6.0 update tonight. ~788MB download and 20 minute install.
Things I noticed differently:
-Response and fluidity seem better, might be due to it clearing the app cache
-Notification bar is smaller, this is a plus for me
-Messages in the message app are smaller, this is a big plus for me
-Everything LG wise has a more flat material design to it. Looks better than before but still iffy
Will update in the future about the battery usage.
Click to expand...
Click to collapse
Where are you located?
mopartonyg said:
Where are you located?
Click to expand...
Click to collapse
Western New York
2kool4u526 said:
Western New York
Click to expand...
Click to collapse
1 of your pics says modified, did you already root it?
Any link kdz ??
Wow... can't believe the VS985 already has official MM coming this quickly. That's so unlike Verizon to get updates out this quickly.
I'm also shocked that VZW released it so early. I'll be waiting for a KDZ so I can upgrade the G3.
Sent from my Nexus 6P using Tapatalk
mopartonyg said:
1 of your pics says modified, did you already root it?
Click to expand...
Click to collapse
Yeah, if you DID root it, how? Curious because I need to keep root for TiBu.
Oh and @snoop5 also posted a link to an article from Android Authority stating the VS985 6.0 is being pushed out.
http://forum.xda-developers.com/verizon-lg-g3/general/verizon-marshmallow-t3298060
Thanks!
Still the same terrible signal and WiFi icons, huh?
Deleted
Sent from my VS985 4G using Tapatalk
mopartonyg said:
1 of your pics says modified, did you already root it?
Click to expand...
Click to collapse
I did not. I was rooted versions ago, that was taken away with the 5.1.1 update, but it kept the 'modified' status.
I can look into root for it. The link Bradg24 posted helps. I'll see if I can get recovery on the phone in an easy way.
bradg24 said:
I have not done it since I am not on stock but found it while searching around
Click to expand...
Click to collapse
Rooting a stock ROM, and having a version of SuperSU that will work on it are two different things. That's not a root method unless you:
1. Already have root/TWRP.
2. Have the new ROM as a flashable zip.
If so, then after flashing the ROM then you can flash SuperSU.zip.
This isn't what people are looking for when they're looking for a "root method".
---------- Post added at 11:30 AM ---------- Previous post was at 11:12 AM ----------
@2kool4u526 can you test the auto brightness on this release? On 35B in a dim room the built-in auto brightness made the screen too dark to be useable, although using Lux Lite from the Play Store rectified that.
Thanks for the info.
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
2kool4u526 said:
I did not. I was rooted versions ago, that was taken away with the 5.1.1 update, but it kept the 'modified' status.
I can look into root for it. The link Bradg24 posted helps. I'll see if I can get recovery on the phone in an easy way.
Click to expand...
Click to collapse
You'll have to get root before you can attempt to install TWRP. Keep in mind if it screws up your boot with a secure boot error, you might not be able to fix it until they release a KDZ for 46A, if 46A's Download Mode doesn't allow flashing older KDZs, just as 35B's didn't.
roirraW "edor" ehT said:
You'll have to get root before you can attempt to install TWRP. Keep in mind if it screws up your boot with a secure boot error, you might not be able to fix it until they release a KDZ for 46A, if 46A's Download Mode doesn't allow flashing older KDZs, just as 35B's didn't.
Click to expand...
Click to collapse
Ah, you beat me to it! LOL
iBolski said:
Ah, you beat me to it! LOL
Click to expand...
Click to collapse
Too bad it's not like Samsung with being able to flash a custom recovery via USB through Odin on a PC, at least that's how it used to be with Samsung before Knox - now I don't know.
I've tried looking into if it's possible to build our own KDZ but I never got anywhere. Since there are tools to extract them there must be a way of building them, although they might contain some kind of manufacturer signature to confirm they're official when flashing them.
Wi-Fi Calling?
Can anyone confirm/deny if this version has any WiFi calling capabilities? I know Verizon rolled out this capability for the S6 and said they were going to update other Android handsets in 2016.
Long shot, but I figured I would put it out there...
do we even have any devs working on stock verizon ports anymore? i thought holyangel and hasbadr stopped working on this device
[indiferenc] said:
do we even have any devs working on stock verizon ports anymore? i thought holyangel and hasbadr stopped working on this device
Click to expand...
Click to collapse
Define "anymore". @hsbadr , @HolyAngel and @xdabbeb all released 35B-based ROMs, and the only one of those three who's phone situation changed since then is @HolyAngel 's.
Before the KDZ is available (or rooting a stock build of the OTA at a minimum) it's too early to find out if anyone will release a ROM based on it. Heck, if no one else did by some miracle, I would, based on what I learned from @hsbadr and @xdabbeb.
Only those three devs might know if they would update their ROMs, and we shouldn't ask them. Either they will or they won't depending on if they feel like it.
(I know you weren't asking them so please don't get upset)
i know hsbadr didn't have the phone anymore when he did 35b.
Really hoping we can get a Jasmine update for MM, I mean maybe someone can make a poll showing how much demand for one there would be?
Yeah idk if I'll be supporting it or not at this time, at the least need kdz or system dump.
Sent from my Nexus 6P using Tapatalk