Here are the bootloader/radio/vendor images for mmb29p AKA 6.0.1_r8
This is all you want if your running a ROM. If your running stock, you will want to get the images directly from Google. If your not sure, ask your ROM's dev team.
http://www.emccann.net/dho/9-Experimental-physics-lab/angler/angler-mmb29p-images.zip
If your not sure how to flash them:
http://lmgtfy.com/?q=How+to+flash+bootimages+on+android
Bootloader and radio are same as in mmb29m.
EDIT: Vendor is same too..
So I asked in another thread, but what are the steps to update from an unlocked bootloader and rooted mmb29m to mmb29p?
Since this build have the same radio as the last one, this wouldn't fix the LTE acquisition?
blazecap said:
So I asked in another thread, but what are the steps to update from an unlocked bootloader and rooted mmb29m to mmb29p?
Click to expand...
Click to collapse
Just check 10. in this thread: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Does anyone have more information about the stuff which got fixed/added by google?
Regards,
JoKe_42 said:
Just check 10. in this thread: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Does anyone have more information about the stuff which got fixed/added by google?
Regards,
Click to expand...
Click to collapse
According to various websites no bug fixes, enhancements and/or extras have been added. It's purely security vulnerabilities fixed in this update.
dyingearth said:
Since this build have the same radio as the last one, this wouldn't fix the LTE acquisition?
Click to expand...
Click to collapse
The consensus is that the problem lies within the ROM, not the radio. Combine that with the post above, I'd say "no". However, two people have confirmed in another thread that with the new ROM, LTE does acquire after boot (after a two-minute wait).
Michalko5896 said:
Bootloader and radio are same as in mmb29m.
EDIT: Vendor is same too..
Click to expand...
Click to collapse
MD5 is not the same for vendor - is it really the same?
AndyYan said:
MD5 is not the same for vendor - is it really the same?
Click to expand...
Click to collapse
only few edits to match latest AOSP build, no real changes..
In case someone is interested in the security patches:
Code:
Remote Code Execution Vulnerability in Mediaserver CVE-2015-6636 Critical
Elevation of Privilege Vulnerability in misc-sd driver CVE-2015-6637 Critical
Elevation of Privilege Vulnerability in the Imagination Technologies driver CVE-2015-6638 Critical
Elevation of Privilege Vulnerabilities in Trustzone CVE-2015-6639 Critical
Elevation of Privilege Vulnerability in Kernel CVE-2015-6640 Critical
Elevation of Privilege Vulnerability in Bluetooth CVE-2015-6641 High
Information Disclosure Vulnerability in Kernel CVE-2015-6642 High
Elevation of Privilege Vulnerability in Setup Wizard CVE-2015-6643 Moderate
Elevation of Privilege Vulnerability in Wi-Fi CVE-2015-5310 Moderate
Information Disclosure Vulnerability in Bouncy Castle CVE-2015-6644 Moderate
Denial of Service Vulnerability in SyncManager CVE-2015-6645 Moderate
Attack Surface Reduction for Nexus Kernels CVE-2015-6646 Moderate
https://source.android.com/security/bulletin/2016-01-01.html
Regards,
cannot be the same because I got a new security warning after flashing cm13 from today!
question
Guys can you help me out.
Downloaded latest 6.0.1 (MMB29P) (from google web)
Flashed everything (locked back bootloader)
But when I checked about phone>>>build number still "MMB29M"?!?!
Redownloaded again latest Factory image which is 6.0.1 (MMB29P), flashed everything again, still same build number "MMB29M.
It's supposed to be like that ?
Regards:good:
JoKe_42 said:
In case someone is interested in the security patches:
Code:
<snip>
https://source.android.com/security/bulletin/2016-01-01.html
Regards,
Click to expand...
Click to collapse
Thanks for the list. With the voluminous vulnerabilities each month, it's beginning to look like Microsoft products....
snovvman said:
Thanks for the list. With the voluminous vulnerabilities each month, it's beginning to look like Microsoft products....
Click to expand...
Click to collapse
Nope! If it would be a MS product, the vulns would not be found (or a lot less) and not get fixed at all...
JoKe_42 said:
Nope! If it would be a MS product, the vulns would not be found (or a lot less) and not get fixed at all...
Click to expand...
Click to collapse
Nope again. I am certain that there are plenty of unidentified and unresolved vulnerabilities in Android (and Chrome too for that matter). When a product becomes sufficiently complex and feature-rich, its zero-days are unfortunately bound to track.
Imagine all the pre-Lollipop devices out there being unpatched.....
I was under the impression that with root and an unlocked bootloader I wouldn't get these ota's but I received a notification for the January security update this morning. I'm just stock 6.0.1 with xposed.
So now I can't remove the notification from my status bar. Is there no other way to update than using fastboot from a computer?
sandfreak said:
I was under the impression that with root and an unlocked bootloader I wouldn't get these ota's but I received a notification for the January security update this morning. I'm just stock 6.0.1 with xposed.
So now I can't remove the notification from my status bar. Is there no other way to update than using fastboot from a computer?
Click to expand...
Click to collapse
You cannot flash an OTA once you flash a recovery, but it has nothing to do with notifications.
To remove notification just long press on it, hit app info, then remove notifications.
Has anyone tried using Flashify? This vendor image is new, so I'm assuming it won't work properly for the N6P...
Sent from my Nexus 6P using Tapatalk
Izeltokatl said:
Has anyone tried using Flashify? This vendor image is new, so I'm assuming it won't work properly for the N6P...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No clue what Flashify is
And whomever said mmb29p and mmb29m vendor images are the same... No, no they are absolutely not.
DHO said:
No clue what Flashify is
And whomever said mmb29p and mmb29m vendor images are the same... No, no they are absolutely not.
Click to expand...
Click to collapse
the only thing thats different is the fingerprint in the build prop
Related
http://www.androidpolice.com/2014/0...droid-incredible-4g-lte-casio-gzone-commando/
http://support.verizonwireless.com/dam/support/pdf/system_update/droidincredible4glte.pdf
pmcall said:
http://www.androidpolice.com/2014/0...droid-incredible-4g-lte-casio-gzone-commando/
http://support.verizonwireless.com/dam/support/pdf/system_update/droidincredible4glte.pdf
Click to expand...
Click to collapse
pretty interesting ... so next will be: 2.19.605.2 710RD ... which is of course newer than our previous 2.17.605.2, but it doesn't give much hope for the expected JB release (3.16.605.1)
main changes (as per changelog dec-2013): ISIS support, Software Update and Software Repair Tools are now compatible (?? whatever that means!!), reduced power cycling, improved bluetooth clarity and ... security patches added
that's about it. will be interesting if ANY new custom roms are going to be based on the new release (a new Viper? ) ... but i suppose we still won't get any newer kernel, any JB love and/or updated Sense(4.5) ... as nothing of that is listed in the update announcement
EDIT: checked http://support.verizonwireless.com/support/system_update/droidincredible4glte.html for "benefits" (which is already updated to 2.19.605.2) and "instructions" for a hint on the size of the (this time for _real_ new OTA 2013/2014!) ... but as instructions are still based on our prev 2.17.605.2 update with its 155mb size, there isn't _any_ info yet on the size of the upcoming OTA. ........... and it seems that it was just less than 24hrs ago, when the news about the 2.19.605.2 update started to make its round in the net (and on the verizon page).
I run Viper rom and it keeps downloading and trying to install. Is there anyway to stop OTA from happening?
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
update size
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
DanPFW said:
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
Click to expand...
Click to collapse
it's HIGHLY LIKELY that ANY previous rooting method will not be working any more AFTER you agree to the new OTA.
@DanPFW: as for HTC, they had prepared a JB update and send it to Verizon ... it's just that Verizon didn't approve it (for some unknown to us reason!!!) ... even the release-number is known, just the actual ROM has not surfaced (yet?!) to the community.
as for rooting and a new custom-ROM ... it's a great and fun device and fairly easy to root & unlock. just that the fully working custom-roms _with_ HTC Sense are ALL only ICS4.0.4 with Sense4.1. Overclocking is easy and stable and a sweet kernel (from user: jose) is available. the newer JB-based custom-roms with Sense5 or Sense4.5 are all ported from different devices and are only partially working, as camera and bluetooth are _completely broken_ due to non-existing (Sense-kernel) drivers for JB. most ppl here are running either ViperLTE2.2.0 (best ICS with Sense4.1 imho) or some AOSP-based custom roms like CM, PacMan, Avatar etc, which are upto at least JB4.3.1 available and nicely working)
EDIT: I hope someone can capture this new OTA for 2.19.605.2 and provide the file here on xda ... for further "analysis"
new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
dcooterfrog said:
new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
Click to expand...
Click to collapse
thanks for the upload ... i just checked its content, but as it's mainly patchfiles (which i dun know how to apply manually to see what's changed) i can only confirm a couple of things for now:
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
* the actual patch-content size is only 15MB!
* whole new firmware package (32MB) ... incl a slightly newer radio: 1.53.06.1009 (was: 1.53.06.0919)
waiting for some more details about the actual OTA changes from others for now :fingers-crossed:
kimba99 said:
thanks for the upload ... i just checked its content, but as it's mainly patchfiles (which i dun know how to apply manually to see what's changed) i can only confirm a couple of things for now:
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
* the actual patch-content size is only 15MB!
* whole new firmware package (32MB) ... incl a slightly newer radio: 1.53.06.1009 (was: 1.53.06.0919)
waiting for some more details about the actual OTA changes from others for now :fingers-crossed:
Click to expand...
Click to collapse
yah I looked the update script
so the hfirware includes the radio. that mihgt make it worhthteh update IF WE CAN ROOT.
dcooterfrog said:
yah I looked the update script
so the hfirware includes the radio. that mihgt make it worhthteh update IF WE CAN ROOT.
Click to expand...
Click to collapse
yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs ... that's why I said, let's wait for "the specialists" to decompose the OTA and tell the "common ppl" what can be safely applied and what better shouldn't
kimba99 said:
yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs ... that's why I said, let's wait for "the specialists" to decompose the OTA and tell the "common ppl" what can be safely applied and what better shouldn't
Click to expand...
Click to collapse
i know I cant do it. that's why i posted it.
i know that the asserts nt eh script check each file (and odex) for the right hash before applying the patch.
kimba99 said:
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
Click to expand...
Click to collapse
I'm not that stupid. I run the Viper run and keep getting the download for the Verzion OTA. I thought the Viper rom was suppose to stop Vertizon OTA's, but I guess it hasn't. I just deferred it for now. Wait to see what happens with it, and if its worth while.
articzap said:
I'm not that stupid. I run the Viper run and keep getting the download for the Verzion OTA. I thought the Viper rom was suppose to stop Vertizon OTA's, but I guess it hasn't. I just deferred it for now. Wait to see what happens with it, and if its worth while.
Click to expand...
Click to collapse
afaik only ViperLTE2.2.0 removed the real Verizon OTA stuff ... it still is present in Viper2.1.1
kimba99 said:
afaik only ViperLTE2.2.0 removed the real Verizon OTA stuff ... it still is present in Viper2.1.1
Click to expand...
Click to collapse
damn, thanks!! :good:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
j13smiley said:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
Click to expand...
Click to collapse
I'm pretty certain it will mess up the ROM if you run the OTA. Viper 2.2 lets you turn off the check/reminder.
j13smiley said:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
Click to expand...
Click to collapse
you probably wont be able to install it anyway. im pretty sure it needs a stock recovery to install it. if youre running viper youre more than likely running custom recovery.
Correct... I didn't think ota updates would actually install on phones running custom rom / recoveries
to get rid of the notifications... does the old trick of changing your build.prop work? i can just use this...
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
Click to expand...
Click to collapse
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
j13smiley said:
to get rid of the notifications... does the old trick of changing your build.prop work? i can just use this...
<snip>
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
Click to expand...
Click to collapse
I decided to just take this as an opportunity to finally upgrade to Viper 2.2.0. I wasn't looking forward to the full ROM install and the PITA that goes with it. Hooray for Nandroid backups and TiB!
If anyone else it thinking of doing the same, make sure you're using TWRP recovery. (Full Nandroid and full TiB backup first before doing anything!). The Aroma installer appeared to work when installing with a CWM-based recovery, but the phone hung up good upon reboot. I looked at the nice white HTC screen for quite a while :laugh:
There is now a method to update while keeping root. See here
source: http://www.androidpolice.com/2015/0...xy-s4-with-stagefright-patch-and-other-fixes/
this is still 5.0.1 (hence the LRX22C build number) but it fixes the Stagefright vuln as well as other stuff
or it's supposed to fix stagefright... lol. good ol sammy.
anyway, if you want root, don't take this update. be patient.
let the discussion begin!
Hope nobody update this before someone capture it, patience..
Sent from my SCH-I545 using XDA Free mobile app
EdrickMG said:
Hope nobody update this before someone capture it, patience..
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
kauaigs said:
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
Click to expand...
Click to collapse
eh. that didnt really matter.
i have a feeling the conflict with kingroot on oc1 was samsung's auto-updating SELinux stuff. no user intervention, it just runs in the background. although those updates make the samsung keyboard not exploitable. lol.
you have options: root, or have a secure phone. you can't have both.
skepticmisfit said:
eh. that didnt really matter.
i have a feeling the conflict with kingroot on oc1 was samsung's auto-updating SELinux stuff. no user intervention, it just runs in the background. although those updates make the samsung keyboard not exploitable. lol.
you have options: root, or have a secure phone. you can't have both.
Click to expand...
Click to collapse
Ah, ok - thanks. I've been trying to re-root since I had to do an odin restore, but Kingroot is unsuccessful...
kauaigs said:
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
Click to expand...
Click to collapse
LRX22C means nothing here (it just signifies 5.0.1, which is what most people are already running). It's what's at the tail end of the build number that counts - OF1. Reread the thread title, the OP and the linked article.
mike.s said:
LRX22C means nothing here (it just signifies 5.0.1, which is what most people are already running). It's what's at the tail end of the build number that counts - OF1. Reread the thread title, the OP and the linked article.
Click to expand...
Click to collapse
DOH....missed that. Thanks!
What's StageFright?
So being the n00b that I am, just to clarify, there is no functioning root for the Verizon Galaxy S4 with the specs i have (shown in my updated signature) short of using Odin and reloading 4.0?
Sir_Eagle said:
What's StageFright?
Click to expand...
Click to collapse
i'll try and sum it up
it was a security vulnerability discovered by jduck (Josh Drake) and, basically, someone can send you a malformed video through the MMS protocol and basically, malware would leak into your phone through that video message if it automatically downloaded.
the exploit specifically targets a system lib called "libstagefright.so" (clever name, eh?) and that library handles everything related to video playback. i think.
if you're not going to install of1, the best way to patch it right now would be to disable automatic downloading of mms messages through your messaging client. chompSMS has its own dealio with stagefright tho, and i've been using chomp for forever, so, yea.
storo1975 said:
So being the n00b that I am, just to clarify, there is no functioning root for the Verizon Galaxy S4 with the specs i have (shown in my updated signature) short of using Odin and reloading 4.0?
Click to expand...
Click to collapse
uhm
well
if you took oc1 via ota, you could try to root using kingroot desktop, that seems to have mixed results.
if you have the nk4 bootloader, you can downgrade to nc5 and root that using towelroot (easiest method ever)
you can't downgrade to kitkat if you took oc1 via ota
Bren caught the update, but is still uploading it. Hopefully kingroot or something else will get root for others.
Sorry guys phone died while re uploading bout to upload
Bren123 said:
Sorry guys phone died while re uploading bout to upload
Click to expand...
Click to collapse
you're uploading that giant file from your phone???
we have a new legend here
Sent from my SCH-I545 using Tapatalk
Bren123 said:
Sorry guys phone died while re uploading bout to upload
Click to expand...
Click to collapse
Any luck?
i just uploaded of a copy update.zip in the fota folder to google drive here. Is that what is needed?
bangdosa said:
i just uploaded of a copy update.zip in the fota folder to google drive here. Is that what is needed?
Click to expand...
Click to collapse
yup.
good job.
you will be credited for this. not sure if bren uploaded his zip yet but yea this is apparently what the update looks like.
all we need now is some pre-rooted ROMs
Sent from my SCH-I545 using Tapatalk
Hey, can someone cut out JUST the stage fright fix and make it flashable for ROMs?
XxD34THxX said:
Hey, can someone cut out JUST the stage fright fix and make it flashable for ROMs?
Click to expand...
Click to collapse
honestly, you could "fix" stagefright yourself by disabling automatic downloading of mms in your app
or if you use chomp, they already have their own fix in place
Sent from my SCH-I545 using Tapatalk
I just happend to wake up and see a software update getting dl'd...it was already at 60%. I went I went into DEFCON 5 freezing, and disabling and force closing stuff....wheew! Close one!
Theoretically, what would happen if I tried to flash a Nexus 9 5.1.1 image to my Apex TM785CH tablet with Kitkat? I'm 99% sure it would brick although it might just work. If this is not possible, is there any way to get 5.1.1 on my device? Are there any universal Lollipop images? The manufacturer has not released any updates for the device.
Thanks
You would brick. Each device has to have a kernel built just for that device. You could try and make an Aosp based rom if you had kernel source for the device.
zelendel said:
You would brick. Each device has to have a kernel built just for that device. You could try and make an Aosp based rom if you had kernel source for the device.
Click to expand...
Click to collapse
That may be the best option, however I wouldn't know where to start with making a rom. I don't know if this information is worth anything:
Settings -> About Tablet
Model: TM785CH
Android Version: 4.4.2
IFWI Version: F9.EE
Kernel Version: 3.10.20, Mon, June 16 15:15:25 CST 2014
Build Number: V1.00_20140616
Your best bet would be to find out if the OEM released the kernel source. Just hope the device is not a Chinese device.
zelendel said:
Your best bet would be to find out if the OEM released the kernel source. Just hope the device is not a Chinese device.
Click to expand...
Click to collapse
Just contacted the manufacturer TMAX Digital (Apex Digital). If I recall correctly they are based in California. Hopefully they can provide the kernel source or even a legitimate update since there is absolutely no information on the internet about this device.
MTutsock said:
Just contacted the manufacturer TMAX Digital (Apex Digital). If I recall correctly they are based in California. Hopefully they can provide the kernel source or even a legitimate update since there is absolutely no information on the internet about this device.
Click to expand...
Click to collapse
I will research them tomorrow.
zelendel said:
I will research them tomorrow.
Click to expand...
Click to collapse
I'm assuming they'll respond to my email Monday, but in the mean time I cannot find anything else.
MTutsock said:
I'm assuming they'll respond to my email Monday, but in the mean time I cannot find anything else.
Click to expand...
Click to collapse
Everything I have found leads me to think the cali address is there just for show. It seems to be imports from China.
zelendel said:
Everything I have found leads me to think the cali address is there just for show. It seems to be imports from China.
Click to expand...
Click to collapse
So their customer service responded and basically said that the device hardware is only compatible with Android 4.4 and there will be no future updates.
I think this is the end of the road as nobody makes custom roms for this device.
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
I was wondering why there's no Thread for this to talk about.
Info about oriole | LineageOS Wiki
wiki.lineageos.org
HSD-Pilot said:
I was wondering why there's no Thread for this to talk about.
Click to expand...
Click to collapse
Maybe because nobody cares?
Anyone know how I could go about troubleshooting the OTA update failing?
I have a Pixel 6, with official LoS installed per the instructions on the wiki.
It seems to work fine, but after downloading the OTA, the Install/Apply Update step does nothing.
It throws an "Install error" message, but with no details or error code.
I have some experience with flashing devices, but much less with over the air updates.
quirkyjoe said:
Anyone know how I could go about troubleshooting the OTA update failing?
I have a Pixel 6, with official LoS installed per the instructions on the wiki.
It seems to work fine, but after downloading the OTA, the Install/Apply Update step does nothing.
It throws an "Install error" message, but with no details or error code.
I have some experience with flashing devices, but much less with over the air updates.
Click to expand...
Click to collapse
Its only been out for like a month I would download the current FULL version and flash on top of your current build and hope the next ota works on saturday
adm1jtg said:
Its only been out for like a month I would download the current FULL version and flash on top of your current build and hope the next ota works on saturday
Click to expand...
Click to collapse
This did end up fixing it.
At the time I posted it, there were two pending updates, and I manually flashed the first with no change in behavior (still wouldn't update via the built in OTA updater).
Manually flashing the next update did resolve the issue though, so it seems like they may have fixed something in those updates.
Thank you for taking the time to help anyway.
Flashed! With the kernel blue spark is an excellent bunch.
GAPPS - MindTheGapps.
The OTA update installed without problems.The kernel was patched after and flashed blue spark now.
Nice ROM! Thank to Lineage Team)
Hello! Has anyone tried build-myself?
maximusfoa said:
Hello! Has anyone tried build-myself?
Click to expand...
Click to collapse
Yes, I'm almost there I just need to stop Linux from killing the end process (android.pb). Did you have any questions?
For some reason, after the command 'breakfast oriole', can’t find the tree ..
Esim doesn't works for me!
Scan works but not add esim
Jossye said:
Esim doesn't works for me!
Scan works but not add esim
Click to expand...
Click to collapse
GAPPS installed?
Great ROM!