Related
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even know what that is... Thanks a lot for your future answers!
Rozalina340 said:
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even what that is... Thanks a lot for your future answers!
Click to expand...
Click to collapse
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
SlimSnoopOS said:
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
Click to expand...
Click to collapse
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Rozalina340 said:
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Click to expand...
Click to collapse
Not problem, that's why this forum exists!
Sent from my Nexus 5X using Tapatalk
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
am2012 said:
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
Click to expand...
Click to collapse
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
macdabby said:
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
Click to expand...
Click to collapse
I've never used LG's website, but the vendor image is included in each 5X factory image:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Hey everyone
I have an M8 with me. GSM of course. It's S-OFF with an Unlocked bootloader.
Current CID is HTC__001
Current FW is 6.12.401.4
My Radio/baseband right now is 1.29.214500021.12G_20.72.4196t.01_F
Now for no reason at all, I want to convert to Developer Edition.
Questions:
1) Can I flash the Developer Edition RUU and then flash the radio from the .401 firmware to get LTE Band 3 (1800MHz) and Band 20 (800MHz)?
2) Is there a ZIP format RUU available for the Dev Edition? I hate using EXEs.
3) Does Developer need 0P6B120 or can I stay on 0P6B100?
4) Will I get OTAs on Dev Edition if I have a different radio than the Dev one?
1. Haven't seen reports of this exact combination being flashed. But in theory, it should work.
2. Not sure if I've seen zip format. Can't think of a thread, off hand. If I find one, I'll post it here.
3. You need to change to the proper MID (in this case 0P6B120). That goes for any official RUU.
4. Pretty sure that having a different radio will cause OTA to fail.
redpoint73 said:
1. Haven't seen reports of this exact combination being flashed. But in theory, it should work.
2. Not sure if I've seen zip format. Can't think of a thread, off hand. If I find one, I'll post it here.
3. You need to change to the proper MID (in this case 0P6B120). That goes for any official RUU.
4. Pretty sure that having a different radio will cause OTA to fail.
Click to expand...
Click to collapse
Would it be pointless then if I converted?
Considering I'd have to flash OTAs etc manually.
Also, do Dev edition devices get monthly security patches? Because the 401 firmware is on the December 2015 security patch.
And there aren't any new OTAs.
Sent from my Nexus 6
murtaza02 said:
Would it be pointless then if I converted?
Considering I'd have to flash OTAs etc manually.
Click to expand...
Click to collapse
Seems pointless to me, yes. The DE has been getting updated a bit faster than 401, but only by a few weeks (if I remember properly). And they are both pretty much unbranded ROMs.
Once you take OTA updates out of the equation, yes it seems pointless to convert to DE.
murtaza02 said:
Also, do Dev edition devices get monthly security patches? Because the 401 firmware is on the December 2015 security patch.
And there aren't any new OTAs.
Click to expand...
Click to collapse
No, the DE does not get monthly patches. I don't know of any HTC phone that got monthly patches. The last update for DE was last December, also.
redpoint73 said:
Seems pointless to me, yes. The DE has been getting updated a bit faster than 401, but only by a few weeks (if I remember properly). And they are both pretty much unbranded ROMs.
Once you take OTA updates out of the equation, yes it seems pointless to convert to DE.
No, the DE does not get monthly patches. I don't know of any HTC phone that got monthly patches. The last update for DE was last December, also.
Click to expand...
Click to collapse
So the only way to get recent security patches is to flash CM or GPE?
Do Sense based custom ROMs have the latest security patches or are they also stuck on December?
Sent from my Nexus 6
murtaza02 said:
So the only way to get recent security patches is to flash CM or GPE?
Do Sense based custom ROMs have the latest security patches or are they also stuck on December?
Click to expand...
Click to collapse
I'm not even sure GPE gets the monthly patches. Sense versions certainly don't.
Hallo guys & gals, I wanted to ask you guys about monthly Security Patches as Google has made bound all the OEMs to release monthly security patches for their devices. In this regard most of the devices are getting monthly or at least once in a couple of months but my Honor-6x is not getting any OTA update since April 2017.
Do you guys have any idea or does any body have any Honor 6x with a more recent security update patch?
Sent from my BLN-L21 using Tapatalk
talvigi said:
Hallo guys & gals, I wanted to ask you guys about monthly Security Patches as Google has made bound all the OEMs to release monthly security patches for their devices. In this regard most of the devices are getting monthly or at least once in a couple of months but my Honor-6x is not getting any OTA update since April 2017.
Do you guys have any idea or does any body have any Honor 6x with a more recent security update patch?
Sent from my BLN-L21 using Tapatalk
Click to expand...
Click to collapse
Honor 6X is getting updated to latest patches every month, currently it's in August Patch 2017...!!!
Sent from my BLN-L22 using Tapatalk
Every month lol. The best Joke i have read.
Well, it depends on the region, US models are rarely updated (unlike EU and Indian variants)
I saw in your signature that your phone model is BLN-21. Could you check if your build ends with B360? If yes, an update should come out soon but meanwhile you should be able to force it, by going on system update > tap on the 3 dots in the upper right corner > download latest update (if the option isn't there you cannot force it yet)
As you can see in these screenshots, in the 1st system update says that there aren't updates; in the 2nd, the option mentioned above is the first of the list, and finally in the 3rd i can download the update
Whoops i forgot the third screenshot, here it is
Well guys as you can see in my shared screen shot my device is on B361 of update level and the region is actual Pakistan which falls under middle east region. Now I actually created the thread to make it sure, whether my region is getting updates or not?
And thanks, @RedSkull23, I have tried your suggestion but as you see my device is already on B361.
I think my real problem is the update via firmware finder, and that's why my device isn't getting OTA updates. As the below screen shot reveals my device is on B361 but the security patch is 5 April 2017, and it is the time when this update was released and I updated my device through FF, since than I have tried a lot but I couldn't get any OTA update.
Sent from my BLN-L21 using Tapatalk
When I still had my 6x, the patch would come about 10-15 days after Google released it. Couldn't say it's timely, but it indeed come monthly.
Btw, I have a Chinese model 6x.
Monthly in China ? And others can go to hell ?
I had to push B365 after about 3 months after B360. Others don't get it at all.
talvigi said:
And thanks, @RedSkull23, I have tried your suggestion but as you see my device is already on B361.
I think my real problem is the update via firmware finder, and that's why my device isn't getting OTA updates. (...) I updated my device through FF, since than I have tried a lot but I couldn't get any OTA update.
Click to expand...
Click to collapse
Can you check or, do you remember if previous build number matches with the number of your actual build, or if not? If they doesn't match, maybe the FF update you did has moved you on a different build number, and so your software update won't find nothing because that's the latest package of your ACTUAL build, instead of the previous. Personally, i get confused every time that i finish to speak about FF updates because with all that packages stored and selectable, the number of possibilities that could provoke an issue are too much to be hold in mind at the same time
You are absolutely right FF has its very serious pros & cons. And yes, I think I remember the previous build number of my device, it was B360 and I did a full package download and dload upgrade on my device, and I also remember I was too much enthusiastic to find a sulotuion for the FM radio problem, yet in vain.
Sent from my BLN-L21 using Tapatalk
talvigi said:
You are absolutely right FF has its very serious pros & cons. And yes, I think I remember the previous build number of my device, it was B360 and I did a full package download and dload upgrade on my device, and I also remember I was too much enthusiastic to find a sulotuion for the FM radio problem, yet in vain.
Click to expand...
Click to collapse
Lets work on the rooting part in other thread. Will help surely to all queries
In indian variant bln-l22 its akso getting monthly updates
Root privileges
Will I lose my Root access and TWRP Recovery if I update this security patch?
uetfreak said:
Will I lose my Root access and TWRP Recovery if I update this security patch?
Click to expand...
Click to collapse
If update size is 200-300 mb then no, it will have the twrp recovery. Make sure you have stock recovery before trying OTA update
shashank1320 said:
If update size is 200-300 mb then no, it will have the twrp recovery. Make sure you have stock recovery before trying OTA update
Click to expand...
Click to collapse
The update is around 550mb.
uetfreak said:
The update is around 550mb.
Click to expand...
Click to collapse
It may have the recovery then which may replace twrp. Better replace beforehand and then update as ota update will cause issue while boot on rooted phone
New update is coming..!!!
Sent from my BLN-L22 using Tapatalk
Tamil15 said:
New update is coming..!!!
Click to expand...
Click to collapse
Someone just informed me on WhatsApp that b361 is coming for Indian variant..lets see. I will have to unroot it first
shashank1320 said:
Someone just informed me on WhatsApp that b361 is coming for Indian variant..lets see. I will have to unroot it first
Click to expand...
Click to collapse
So back to back update..!??
Sent from my BLN-L22 using Tapatalk
Hi, I'm having trouble sifting through the forum for clear information regarding sideloading One UI 3 beta for my S20+. I have several questions that I haven't found concise answers for and would appreciate some help. Please direct me to the correct threads if I missed something obvious.
Current setup is SM-G986U1 Snapdragon on BTIG firmware.
I want to sideload One UI 3 beta using Odin because the beta registration is always either missing or at max capacity. I know there was an update yesterday, so the latest version may not be available online yet.
Questions:
1. Generally, are full beta images available, or only incremental OTA updates?
2. Can the update be sideloaded without unlocking the bootloader? If it can, does data need to be wiped?
3. Once on the beta, will I receive OTA updates, or will I have to sideload future ones?
4. Has anybody uploaded a beta update zip for my model/fw combo yet? I haven't seen it in the Snapdragon thread, but I may have missed it.
Thanks in advance! And apologies if these questions are commonly asked. I found it difficult to search through the forum.
Cheater912 said:
Hi, I'm having trouble sifting through the forum for clear information regarding sideloading One UI 3 beta for my S20+. I have several questions that I haven't found concise answers for and would appreciate some help. Please direct me to the correct threads if I missed something obvious.
Current setup is SM-G986U1 Snapdragon on BTIG firmware.
I want to sideload One UI 3 beta using Odin because the beta registration is always either missing or at max capacity. I know there was an update yesterday, so the latest version may not be available online yet.
Questions:
1. Generally, are full beta images available, or only incremental OTA updates?
2. Can the update be sideloaded without unlocking the bootloader? If it can, does data need to be wiped?
3. Once on the beta, will I receive OTA updates, or will I have to sideload future ones?
4. Has anybody uploaded a beta update zip for my model/fw combo yet? I haven't seen it in the Snapdragon thread, but I may have missed it.
Thanks in advance! And apologies if these questions are commonly asked. I found it difficult to search through the forum.
Click to expand...
Click to collapse
Search the other threads for it. It is all well explained. In a nutshell, you will have to flash BTIF, and then sideload the beta versions one after another. There isn't an 'image' to flash.
BigE said:
Search the other threads for it. It is all well explained. In a nutshell, you will have to flash BTIF, and then sideload the beta versions one after another. There isn't an 'image' to flash.
Click to expand...
Click to collapse
Thanks. So there's no way to do it without wiping. Maybe they'll open it up again soon...
look in the beta thread....
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...