UPDATE: Axon 7 A2017U Build 29 (MR3)
New OTA update is arriving and looking forward for what bring to the table.
aerospaceman Employee Oct 30, 2016 6:01 PM
Over the next 24 to 72 hours, you can expect our 3rd software update (MR3) to the Axon 7 (A2017U). This update will bring your device to the latest build, B29. This update comes less than one and a half months from the previous one, but the more exciting news is that we're in parallel paths to deploy Nougat as quickly as possible.
Here are the latest updates you will see on B29 (coming from the previous build, B27):
Notification bell is now optional (hooray!)
New application management policy to enhance battery life
Optimized video camera focus on moving objects
Resolved .FLAC file playback issue
Visual Voicemail optimized for dual SIM
Updated fix for Mute Call issue
Other general enhancements
Note: This is an over-the-air (OTA) update. To check availability of an update, click on "Settings -> Updates."
Aside from this update, you can bet on our R&D team being hard at work on Android N. Early tests from your Mod Squad have been very positive and we trust that many of you will also not sleep for the first several days after upgrading. Setting Nougat aside, we remain heads down prioritizing fixes and enhancements for our community. Your constant feedback, both positive and negative, continue to motivate our R&D team. So please don't let up on your interactions with us and each other about the Axon 7. Until the next update, please drop a comment below to add further motivation for your R&D team!
Click to expand...
Click to collapse
-------------------------------------------------------------------------
UPDATE: Axon 7 A2017U Build 29 (MR3) Announcement Link
-------------------------------------------------------------------------
TWRP Flashable Files can be found here : TWRP_A2017U.B29_Bootstack_StockSystem_Files
What's does the " Parallel paths" mean....
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
S8ntsHaz3 said:
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
Click to expand...
Click to collapse
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
DrakenFX said:
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
Click to expand...
Click to collapse
Oh how I hope your right!!!!
Now to wait for the download link
xtermmin said:
Now to wait for the download link
Click to expand...
Click to collapse
It's here!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
It's here!
Click to expand...
Click to collapse
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
jonathan3579 said:
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
Click to expand...
Click to collapse
There's an app in play store to enable it in any device!
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
There's an app in play store to enable it in any device!
Click to expand...
Click to collapse
Oh sweet, thanks. I think I tried it before but it didn't stick after rebooting. Has it changed since then? If so, I'm definitely gonna have to search for it again.
I have the option for the update as well. Waiting as I'm rooted.
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Thanks for looking into a twrp version!
Sent from my ZTE A2017U using Tapatalk
Parallel paths does indeed mean they are simultaneously working on updates and the long awaited Nougaaaattttt update. ZTE has done a good job updating and listening to their customers in the z-forum. Lets hope this plus Official CM and unlock bootloader without breaking warranty will help ZTE be known as a developer friendly Own.
How do we install if we are unlocked bootloader and rooted??
Do we have any idea if flashing U roms on G device works? Would love to get rid of the bell
Here over in europe, i just received for my A2017G an 703mb big B05 Update.(previous B03)
Strange that ours is 703mb big (hope they fix the youtube freeze Problem) and also supports optional notification bell (no info for that in the change log)
Take a look:
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Here is an Mega Mirror for the B29 update. Just in case.
I have simply copied it from its location "data/data/com.zte.zdm/files" where the updater places its OTA files.
https://mega.nz/#!K050XAqT!6EBTgtX13VTdAOiUjiYqeE6jemeOJ2mN8smrrreai6o
MD5: 9a7f45caf459a21a905de0c543748309
If you place the file into that directory. You should be good to go using the inbuild updater.
Dewaynelives said:
How do we install if we are unlocked bootloader and rooted??
Click to expand...
Click to collapse
I was on B27, unlocked bootloader, TWRP recovery, rooted, with changes to /system, and have successfully upgraded to B29 (w/ same modifications). Since I made changes to /system (AdAway, Titanium Backup, AFWall) and wanted a clean slate for everything, I wiped my A7.
If you don't want to factory reset your device and didn't make any changes to /system, you might only have to unroot, restore stock boot.img and stock recovery.img via TWRP (from rczrider's topic linked below), install B29.zip in stock recovery, flash TWRP, then flash root, but I didn't do it personally, so no guarantees.
Anyway, this is what I did. Some of these steps might not have been needed, and probably could have been done differently, but it's what worked for me, and yes I like rebooting:
1. Download the B29 update, DrakenFX's B27 StockSystem zip for TWRP (which also flashes stock boot.img), stock B27 recovery.img from rczrider, and SuperSU 2.65. Put all on microSD.
2. Booted into TWRP and did a factory reset, rebooted back into TWRP and flashed DrakenFX's B27 StockSystem ZIP, rebooted back into TWRP and flashed stock B27 recovery.img, rebooted device.
3. Powered on the device and made sure it booted into OS fine and was still reporting the correct amount of internal storage space. Rebooted into stock recovery and flashed the B29 update.zip from my microSD card. Installed fine, rebooted into OS to made sure it still worked.
4. Rebooted into fastboot, connected to my computer and flashed Unjustified Dev's TWRP via Minimal ADB & Fastboot, booted into TWRP and flashed SuperSU 2.65 from my microSD, let the device reboot itself a couple of times.
I now have B29 with unlocked bootloader, TWRP, and root.
NOTE: Something I noticed when I was going through and disabling system apps: WeShare can't be disabled from the Settings > Apps menu, but can be disabled by opening the app drawer, pressing and holding on it, and dragging it up to "Disable" at the top of the screen.
However, it would probably be easier to just wait for DrakenFX to create custom TWRP install zips for B29.
Related
I'm not sure if this is the right section, but has anyone else received the 5.0.2 update? I got mine about half an hour ago, but I can't find a changelog. These are the changes I've noticed so far:
It's somewhat faster
Apps no longer fail to launch (I'd try to open them before, but they would close immediately, and I'd have to dim the screen before trying to open the app again)
By the way, does "sunlight mode" do anything at all?
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just got this, I haven't loaded it yet, I have Gohma loaded. It will not let me swipe the notification away, Is installing my only option because that kind of messes up getting any other notification.
Just got this but cant find anything new. Sunlight mode was already available via lollipop update. Never used it but i assume if you use low brightness levels a quick swipe will make it brighter and vice versa rather than manually altering the brightness. Not an issue for me as i used mini launcher but they can't assume everyone does
http://www.talkandroid.com/237608-a...o-the-samsung-gear-live-and-the-lg-g-watch-r/
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Apoplectic1 said:
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Click to expand...
Click to collapse
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
dligon said:
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
Click to expand...
Click to collapse
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Apoplectic1 said:
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Click to expand...
Click to collapse
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
prototovsky said:
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
Click to expand...
Click to collapse
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Apoplectic1 said:
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Click to expand...
Click to collapse
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
prototovsky said:
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
Click to expand...
Click to collapse
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Apoplectic1 said:
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Click to expand...
Click to collapse
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
prototovsky said:
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
Click to expand...
Click to collapse
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Apoplectic1 said:
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Click to expand...
Click to collapse
No, but I'll try some things ...
I just tried to flash it using TWRP after completely wiping everything but internal storage, thinking it might need a clean flash, but it gave me an error saying that it was unable to flash due to an error in executing the updater binary.
I'm going to flash the stock recovery on it, wipe the data and caches and see if adb sideloading it is any more effective.
EDIT: It isn't.
Im trying to manually push this update to my watch as well, has anyone figured out any solutions?
I tried flashing update-LWX48P5.0.1-to-LWX49K5.0.2.zip from http://rootjunkysdl.com/?device=LG G Watch&folder=OTA but it errors when I try through TWRP. I went back to stock but I do have an unlocked bootloader, I will try relocking and trying then.
Okay so thats weird, im on 5.0.1 but when i try and flash 5.0.2 from TWRP is errors saying that the device "lge/cm_dory/dory:4.4.2/KVT49L/567135e166:eng/test-keys"
how get it to read as 5.0.1 which I am on?
edit:
Soo, I wound up on 5.0.2 while trying to fix some of the random flashes I was trying to update. I wound up erasing my system.img and it was only booting to recovery, so I did the "back to stock" option from rootjunkys toolkit and it reflashed boot/system etc, and when I booted up to turn dev options back on it looks like it put 5.0.2 back on. So that fixed that
Bugs after LWX49K update
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Hey guys!
Since it seems some of you are a bit confused about all this: Just use THIS tool here (LG G Watch Restore Tool, make sure you use version 9.5), go into fastboot mode (rebooting, when LG logo appears swipe from left upper to lower right corner) over USB and choose the option "6 Restore your G watch to stock".
Voila! Now you're on 5.0.2 with less effort than OTA updating
I discovered this by accident actually. I tried to restore stock so I can OTA update to 5.0.2, then I saw it's a pre-rooted system.img (because root overwrites OTA critical things so it fails) and already suspected it'd be the newest one
danr said:
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Click to expand...
Click to collapse
I was getting a lot of bugs also, but I'm not sure if it is watchmaker or update. Super slow now and notifications are random. I'm uninstalling watchmaker first to check.
going back to stock cause fricking anoying notification...
and some one made a kernel for 5.0.2. a new guy
BOOTLOADER UNLOCK IS REQUIRED FOR THIS TO WORK
STEPS
1. <Mod Edit: Link removed for promoting paid service.>
2. flash stock ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip Firmware in RSD Lite or use my RSD lite for mac or linux use the servicefile.xml in the firmware to keep your data and apps.
2. download and run the batch file in XT1625-Remove-Amazon-Ads-only-keep-apps.zip tool. Just click on the remove-amazon-ads.bat and follow the directions.
3. once device reboots your good to take ota updates or adb sideload the latest ota update
NOTE
ads will not be restored on the device after a ota update until Amazon decides to push something to the device that affects the one app i deleted from the oem.img that displays the ads.
enjoy
Rootjunky out.
RSDLITE NOT WORKING ON WINDOWS 10 CHECK THIS OUT
https://youtu.be/njXQYn53SPc
Donate if you like my work thanks
Wow. Nice. Speechless. You're one awesome person! Thanks for your time and effort. It's very much appreciated.
Hey TOMSGT...thanks for the post. It worked for me, however I'm not receiving the latest OTA update which is called MPJ24.139-48
Apparently from the logs it's to improve call stability.
How can I continue to get updates? Thanks.
pacattack81 said:
Hey TOMSGT...thanks for the post. It worked for me, however I'm not receiving the latest OTA update which is called MPJ24.139-48
Apparently from the logs it's to improve call stability.
How can I continue to get updates? Thanks.
Click to expand...
Click to collapse
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Tomsgt said:
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Click to expand...
Click to collapse
Thanks. I'll keep my eyes posted for the update. My dad just got his phone updated so I wondered. Now I'd only they could fix the phones camera. My pictures come out pretty bad.
Thanks!
Tomsgt said:
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Click to expand...
Click to collapse
Do you think being rooted will effect getting updates? On my nexus 5 after I rooted and installed twrp I wasn't able to get updates anymore.
pacattack81 said:
Do you think being rooted will effect getting updates? On my nexus 5 after I rooted and installed twrp I wasn't able to get updates anymore.
Click to expand...
Click to collapse
Yes root and twrp will cause ota update to fail to install.
Tomsgt said:
Yes root and twrp will cause ota update to fail to install.
Click to expand...
Click to collapse
Other than the update you provided how do I continue to sideload updates? Where there be a place updates will keep getting posted at? Also, when you say sideload the update you provided what do you mean? Can I flash the zip in TWRP or is there another method?
Thanks.
pacattack81 said:
Other than the update you provided how do I continue to sideload updates? Where there be a place updates will keep getting posted at? Also, when you say sideload the update you provided what do you mean? Can I flash the zip in TWRP or is there another method?
Thanks.
Click to expand...
Click to collapse
Well I will keep posting Amazon ota updates on my site as I get them.
Adb sideload is done on stock Android recovery by selecting apply update from adb or apply update from sdcard.
Tomsgt said:
Well I will keep posting Amazon ota updates on my site as I get them.
Adb sideload is done on stock Android recovery by selecting apply update from adb or apply update from sdcard.
Click to expand...
Click to collapse
Since I'm now using TWRP recovery how do I sideload the update? Can I flash the zip in TWRP?
Thank you for the good work.
I already followed your previous instruction on removing amazon. And, now, here you have a newer slightly different way. Can you please help me understand a few things?
1) what are oem.img and ads-removed-only-oem.img? Obviously, they are different from the stock firmware - ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which is bigger than 1GB. oem.img is only 128MB and ads-removed-only-oem.img is 540MB. Is it correct that you started from the stock firmware, and removed all of the Amazon additions, and you ended up with oem.img or ads-removed-only-oem.img? So, your script is not about deleting all the Amazon stuff, but about flashing an image that you came up with after removing all the Amazoz stuff?
2) The reason you need to unlock the bootloader on this instruction is to put the stock firmware on it, right? So, if you were to start from a fresh out of the box Amazon phone, then can you skip step 1 and 2?
3) What are the differences between oem.img and ads-removed-only-oem.img, that keeps OTA working vs not working?
TIA.
chonghak said:
Thank you for the good work.
I already followed your previous instruction on removing amazon. And, now, here you have a newer slightly different way. Can you please help me understand a few things?
1) what are oem.img and ads-removed-only-oem.img? Obviously, they are different from the stock firmware - ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which is bigger than 1GB. oem.img is only 128MB and ads-removed-only-oem.img is 540MB. Is it correct that you started from the stock firmware, and removed all of the Amazon additions, and you ended up with oem.img or ads-removed-only-oem.img? So, your script is not about deleting all the Amazon stuff, but about flashing an image that you came up with after removing all the Amazoz stuff?
2) The reason you need to unlock the bootloader on this instruction is to put the stock firmware on it, right? So, if you were to start from a fresh out of the box Amazon phone, then can you skip step 1 and 2?
3) What are the differences between oem.img and ads-removed-only-oem.img, that keeps OTA working vs not working?
TIA.
Click to expand...
Click to collapse
1. Ads remove only oem.img is just that the stock Amazon OEM.img but I deleted the lock screen ad app from it. This file isn't signed by Motorola and requires a unlocked bootloader to flash.
2. Bootloader I unlock has nothing to do with flashing stock firmware you can do that even with a locked bootloader it's about the edited OEM.img
3. The reason that ota updates still work with the ads removed only OEM.img is because Amazon doesn't check to see if that deleted file is there or not when updating and so the ota update still works.
Hello Tomsgt, thanks for all the help you provide. I already unlocked the bootloader, installed TWRP, installed xposed, removed the unlocked bootloader message, rooted it and have set it up the phone the way I want it, my question is, can I remove the ads on the lock screen with your tutorial without losing everything I've done already. I want to keep the Amazon apps since I do use them since I'm a Prime member I do find them useful but I really thought that the ads will not get to me and bother me but I was wrong, will I have to restart everything if I do that. Another question is that I just received and update MPJ24.139-49 https://goo.gl/photos/7bezpWNyQA4Sdgbb8 (I have MPJ24.139-48 installed) but since I''m rooted and have TWRP I can't update, if you need the update zip, where will I find it or how can I pull the zip. Thanks in advance.
Confirmed this works!
I did as instructed and spammed the check updates. Nothing... until I stuck in a sim (coincidence?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
markazali said:
Confirmed this works!
I did as instructed and spammed the check updates. Nothing... until I stuck in a sim (coincidence?)
Click to expand...
Click to collapse
boom there you go
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
munkyvirus said:
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
Click to expand...
Click to collapse
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Ultim8gamr said:
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Click to expand...
Click to collapse
thats seems to be what everyone is reporting yes. which really sucks too
munkyvirus said:
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
Click to expand...
Click to collapse
Ultim8gamr said:
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Click to expand...
Click to collapse
Doesn't look to be unlockable anymore. I already unlocked mine, but tried re-submitting the request, got an error saying it no longer qualifies.
However, Motorola's list of unlockable devices now says to contact Amazon CS for the Amazon models, so maybe Amazon is setting up their own system to allow BL unlock? Not sure, but at this point, it's better to spend the extra $25 to get the factory-direct version of the phone.
ROM Pyrana 0.9 HTC U12+ 1.53.401.5 DUGL
. Base: 1.53.401.5 DUGL (dual sim)
. Decembrer 2018 Security Patches
. Deodex
. Busybox, zip aligne
. Disable error reporting
. Root with last Magisk! v19.1 (Default) Credit to @topjohnwu
. Optimized and stable
. Renew HTC Wallpaper
. Pyrana Wallpaper
. All apk up to date
. Slver clock
. Weather custom color
Screen:
For the best experience, please make sure you have the latest HTC U12+ firmware installed prior to installing this ROM (Only for Android 8.0. .The part 'vendor will not be flashed, only system. No need for root, it is in Rom directly
From a base 1.53.401.5 imperatively to have the party 'vendor.
At boot time, leave plenty of time to put everything in place and have a good WIFI connection.
Once everything stabilized update Magisk.
Install:
Backup your ful system and data
Copy Pyrana-U12 to external SD
Reboot to recovery TWRP 3.2.3-3 and format partition, data and cach.
And start Install the zip
Filehost https://www.androidfilehost.com/?fid=1395089523397959188
md5: c120131bd005deba27d8ca4e97f0aba6
****************************************
Download Pyrana-U12-0.6-1.34.401.2 stable:
Update 2019/01/13
FILEHOST https://www.androidfilehost.com/?fid=11410963190603905105
MD5: 1bb28a84eb361542f50ca902d5b2561d
Compatible:
DUGL Dual SIM
Install:
It is imperative to start from a 1.30.401.2 base to get the 'vendor' version!
Unlock your device bootloader via > HTC Dev
Backup your ful system and data
Copy Pyrana-U12-0.6 to external or internal SD
Reboot to recovery TWRP and format partition, System, data and cach.
And start Install the zip
When finished restart and wait for initialization (First boot will take approximately 2 or 3 minutes to optimization)
All flash rom is under your responsibility
Accepts no responsibility for:
Any damage to your device
Any loss of data
All my rom are tested several times in complete wipe system and data
BUGS:
Face unlock not work
********* Tuto HtcDev for unlock bootloader *******
https://mega.nz/#!g8pGiIqB!4F1izBcb_d0ohTHQqWYhjimTCM9ievZBaveIvD_GkoU
Nice, I see you was able to make it, like I told you, without vendor partition, congrats!!!!!!!!
JEANRIVERA said:
Nice, I see you was able to make it, like I told you, without vendor partition, congrats!!!!!!!!
Click to expand...
Click to collapse
Hi,
With patience and trick it is possible
nice, hope you will add more features and fix known bugs in near future! thanks
Nice to see you here @Alan-B
Hi,
Unlocking the face is a root problem, for the moment there is no definitive solution!
The Power apk is not mine so I can not change it, it's not legal. In any case the reboot in recovery is problematic! we may not have installed TWRP fixed! and if there is it can be on partition A or B !!
I do not know if it works on Viper? but it is not certain!
Sorry for the bad English ..
Alan-B said:
Hi,
Unlocking the face is a root problem, for the moment there is no definitive solution!
The Power apk is not mine so I can not change it, it's not legal. In any case the reboot in recovery is problematic! we may not have installed TWRP fixed! and if there is it can be on partition A or B !!
I do not know if it works on Viper? but it is not certain!
Sorry for the bad English ..
Click to expand...
Click to collapse
reboot recovery and faceunlock both work on magisk version of the Viper ROM, the faceunlock doesn't work on full ROM but reboot recovery does work on full ROM but is a dirty & complicated hack
JEANRIVERA said:
reboot recovery and faceunlock both work on magisk version of the Viper ROM, the faceunlock doesn't work on full ROM but reboot recovery does work on full ROM but is a dirty & complicated hack
Click to expand...
Click to collapse
Hi,
I just checked ... my TWRP is in patition B and power reboot works in recovery. If in patition A I do not know !!
To unlock the face, I never had it on my U12..
PS: If we have a backup of the data, it can be restored after the flash of my rom (as long as there are no updates to Android system file in this data or there is a risk of conflict!)
Alan-B said:
Hi,
I just checked ... my TWRP is in patition B and power reboot works in recovery. If in patition A I do not know !!
To unlock the face, I never had it on my U12..
PS: If we have a backup of the data, it can be restored after the flash of my rom (as long as there are no updates to Android system file in this data or there is a risk of conflict!)
Click to expand...
Click to collapse
Yep data backup works for the same version of the HTC rom.before flashing new update/rom, it is recommended to restore data first, then update rom then backup data again, in case you play with stuff and you have to restore data again
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
Yep data backup works for the same version of the HTC rom.before flashing new update/rom, it is recommended to restore data first, then update rom then backup data again, in case you play with stuff and you have to restore data again
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hi,
Warning ! if we do not format the data, there may be a problem that the device no longer sees the card sd External after installation of the system! but we can restore data after, there are no problems!
PS: I uninstall all the updates just system in settings / applications, I make a backup of the data, I install my zip and once configured I restore my data.
@Alan-B, any plans to have this work for US Unlocked variant as well? If I am not mistaken we worked together briefly on a device. I want to say it was the U11...
mammothjojo88 said:
@Alan-B, any plans to have this work for US Unlocked variant as well? If I am not mistaken we worked together briefly on a device. I want to say it was the U11...
Click to expand...
Click to collapse
Hi,
The problem with the U12, no way to put AROMA to choose a version! Because of the various partitions on the U12 +. It would be necessary to make an entire rom for each version.
The only solution is to make small changes like Viper but via MAGISK! what I do not do!
I could make a version for US Unlocked, but no way to test it!
Alan-B said:
Hi,
The problem with the U12, no way to put AROMA to choose a version! Because of the various partitions on the U12 +. It would be necessary to make an entire rom for each version.
The only solution is to make small changes like Viper but via MAGISK! what I do not do!
I could make a version for US Unlocked, but no way to test it!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wouldn't be so sure of that..... coming soon from a dev near you.....
JEANRIVERA said:
I wouldn't be so sure of that..... coming soon from a dev near you.....
Click to expand...
Click to collapse
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Alan-B said:
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Click to expand...
Click to collapse
If you are looking for help I'll be more than happy to help, I am willing to learn or at least try to provide any help I can. I don't want to pressure you but I don't mind getting my hands dirty. Let me know
Alan-B said:
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Click to expand...
Click to collapse
I think you misunderstood my intention with this post, AROMA is going to be openly available once it is ready for release, we are still having some issues, but not with AROMA any more, AROMA does run perfectly fine now after some tweaks, the problem is the method of installation, right now it can only be triggered manually from a command line while in recovery, we are looking for a solution for it to be able to flash AROMA zip files just like before.
I did not meant to mock you or make fun of you at all, this is a sharing community and once it is available and working, it will be shared for all of us to use it, we just don't think it is ready for public release yet
I am sorry if my comment make you feel any other way than what was my intention. have a nice day!!!!!!!! :fingers-crossed:
hi,
Hello,
No problems, I just wait if it is posible to have the opportunity to adapt Aroma to have choices for installation. Which served more convenient than an .img file. This will allow to have a zip compatible with the various versions, as I did for the U11 (which unfortunately is broken)
Thanks to you for bringing an interest to my work and thanks to 'mammothjojo88' for your proposal, doing the work is not a problem for me, just having some solutions to make the work easier and make it more efficient and practical.
PS: What I find a little sad is the return can or thank you for my work to which I never had donations! for the HTC10 + of 1200 download for the U11 300 and for the U12 +, 25 on 3 days. On the French Forums where it's very different! and I have many thanks for my rom
Alan-B said:
hi,
Hello,
No problems, I just wait if it is posible to have the opportunity to adapt Aroma to have choices for installation. Which served more convenient than an .img file. This will allow to have a zip compatible with the various versions, as I did for the U11 (which unfortunately is broken)
Thanks to you for bringing an interest to my work and thanks to 'mammothjojo88' for your proposal, doing the work is not a problem for me, just having some solutions to make the work easier and make it more efficient and practical.
Click to expand...
Click to collapse
Aroma will be fully customizable just like before once it is ready, we are still working on the last steps of making aroma work, but once it is done it will be just like on previous devices
Great to hear! I will be more than happy to help with any testing you require. Just let me know
mammothjojo88 said:
Great to hear! I will be more than happy to help with any testing you require. Just let me know
Click to expand...
Click to collapse
Hi,
I'm busy compiling a US Unlock version. I'll post it for testing
Test version for Unlock UHL:
https://www.androidfilehost.com/?fid=1322778262904022930
md5: 9fcc1798f2bed7425b5f79f393f687f1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this inexpensive tablet. Many thanks to @mehanik6 on 4PDA for blazing the trail.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source.
This is unofficial and unsupported, so the usual caveats apply. Since we don't mess with the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5 (Odin tarball)
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Build archives:
Android File Host
Change Log:
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2020-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2020-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0: (2020-11-01)
Initial release based on T290XXS3ATC1 OEM kernel
Fixed MTP support
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
jimbo77 said:
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
Click to expand...
Click to collapse
Yes, I've been requesting this since I got my SM-T290 in mid-October (when it went on sale for $89 at Costco) and Samsung finally posted it on Monday, along with the SM-T500. I'm actually building the custom kernel right now and should have an update for TWRP and a Nexus Stock custom ROM very soon.
UPDATE: Samsung seems to have changed the bootloader in Android 10 so that it won't support custom recovery even if the bootloader is unlocked and we substitute an empty vbmeta.img. This is another one of those Samsung VaultKeeper "features" that I find infuriating.
UGH!! I own both of these tablets (290 and 500) and just rooted the 500. I was hoping there would be some some custom ROMs coming out early next year for the 500.
Well, at least with the SM-T290 we can roll back to the Android 9 bootloader (minimally aboot and vaultkeeper), but that might not be an option with the SM-T500. We'll find out this weekend when I attempt to build TWRP for that newer tablet, which released with Android 10 and dynamic partitions.
The fact that you've been able to root the SM-T500 is promising, since Majisk modifies the recovery partition to do that.
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
sal84x said:
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
Click to expand...
Click to collapse
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Magendanz said:
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Click to expand...
Click to collapse
Oh ok thanks for breaking that down for me, I just was worried it wouldn't be compatible.
I would love to have a Nexus like experience on this thing, the more vanilla and pure Android, the better to me.
Would games on the sd card still play? Thats really my biggest reason as my daughter has already maxed out her space on it.
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember .
Thanks for your help
Quick Note: I just modified the Odin tarball to include legacy aboot and vaultkeeper images so that you can flash this custom recovery on Android 10 OEM firmware releases. The recovery image itself is unchanged.
sal84x said:
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember.
Click to expand...
Click to collapse
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Magendanz said:
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Click to expand...
Click to collapse
Oh ok, i see.
Your Nexus rom for the SM-T510 looks awesome! Also, that Tab A7 tutorial is great.
On your original post, the first 2 downloads you have, the first one, "twrp-3.4.0-0-T290UES3ATC1-20201204.tar.md5 (Odin tarball)" that puts the custom recovery on the phone via ODIN. The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Does your T290 feel more responsive - less laggy with your Nexus rom?
sal84x said:
The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Click to expand...
Click to collapse
Samsung doesn't do flashing via fastboot, so the .img file is really only for incremental updates via TWRP.
sal84x said:
Does your T290 feel more responsive - less laggy with your Nexus rom?
Click to expand...
Click to collapse
I think so, but I might be biased and I haven't had time to run any performance tests. I just posted the first release, though, so you can judge for yourself.
BTW, the $89 Costco deal is back until 12/27.
Quick question, I am having an issue using Smart Switch to make backups for my T500 on my Win10 machine. Seems like it just started and hangs up on applications. Any ideas? Want to install a few Magisk modules but want a back up first.
Magendanz said:
BTW, the $89 Costco deal is back until 12/27.
Click to expand...
Click to collapse
Wow and a free 32GB SD card. Awesome deal! I got mine for $99 from BestBuy with no card.
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
TenSeventy7 said:
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
Click to expand...
Click to collapse
I've been told that it does, but I haven't confirmed it myself because I don't have an SM-T295.
The links seem to be broken?
TenSeventy7 said:
The links seem to be broken?
Click to expand...
Click to collapse
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Magendanz said:
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Click to expand...
Click to collapse
Okay, apparently the forum now forks a thread if you change the title. Bug or feature?
The new thread for TWRP v3.5.0 on the SM-T290 is here.
Any chance to get a working TWRP for latest stock firmware as of now?
Hi All,
I am now on the latest India Android 13 Beta that was just released.
Here is how I flashed while keeping root and unlocked bootloader.
Global to Full EU A08 - Install magisk to inactive slot before rebooting
EU A08 to Full India A10 - Install magisk to inactive slot before rebooting
India A10 to Full India latest Android 13 beta(CPH2413_11_C.10) - Install magisk to inactive slot before rebooting
If I didn't goto the EU rom, I would have just went to the latest India and then to the India Android 13 Beta.
After you flash using local storage while booted into your current Android, BEFORE YOU REBOOT, you have to then goto Magisk app and install Magisk to the "Inactive Slot"
I did not need to do a factory reset either. I read somewhere that if you are going to a newer version when flashing cross regions, you won't have to factory reset. I haven't tried flashing the same full version of a different region, but I don't see why I would need a factory reset in that instance either as long as I am doing the "Full". Though that is yet to be determined.
Also you have to always do the "Full" update when you download it from Oneplus Updater app if you have an unlocked bootloader. It's probably also required if you are just going to be jumping around different region roms...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does doing this method keep your data? Even with doing full update from oxygen updater? Thanks in advance! I will keep a backup either way but I'd like to know.
JPower123 said:
Does doing this method keep your data? Even with doing full update from oxygen updater? Thanks in advance! I will keep a backup either way but I'd like to know.
Click to expand...
Click to collapse
Yes, it kept all my data. No need for a factory reset if you follow what I did.
maamdroid said:
Yes, it kept all my data. No need for a factory reset if you follow what I did.
Click to expand...
Click to collapse
Hey, thank you so much for the reply, however it seems I have gotten myself into a pickle lmao... After downloading the indian A10 firmware from oxygen updater, I went into software update in settings and clicked local update etc... It then said extracting for a while, and after that, it simply said install. I clicked on install, and it restarted my phone to proceed with the update, this caused me to lose root. That is fine with me as I can simply root again before updating to A13, however, is there a way to install without rebooting for next time? or do I install magisk to inactive slot before clicking "install" in settings? Other than this the first update went fine, and my data is perfectly intact.
JPower123 said:
Hey, thank you so much for the reply, however it seems I have gotten myself into a pickle lmao... After downloading the indian A10 firmware from oxygen updater, I went into software update in settings and clicked local update etc... It then said extracting for a while, and after that, it simply said install. I clicked on install, and it restarted my phone to proceed with the update, this caused me to lose root. That is fine with me as I can simply root again before updating to A13, however, is there a way to install without rebooting for next time? or do I install magisk to inactive slot before clicking "install" in settings? Other than this the first update went fine, and my data is perfectly intact.
Click to expand...
Click to collapse
I am using one of the apks to do the local install. I did not have local install in my normal settings. As noted in the OnePlus updater app, below are the links. I used the android 12 one below.
This does the install them tells you to reboot. You ignore that and then do the magisk flash before rebooting. I'm surprised you have local install in your normal settings...see my screenshot below for what I am using.
OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk
maamdroid said:
I am using one of the apks to do the local install. I did not have local install in my normal settings. As noted in the OnePlus updater app, below are the links. I used the android 12 one below.
This does the install them tells you to reboot. You ignore that and then do the magisk flash before rebooting. I'm surprised you have local install in your normal settings...see my screenshot below for what I am using.
OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk
View attachment 5744509
Click to expand...
Click to collapse
Yeah honestly I was kind of surprised too lmao, Im pretty sure that I screwed up a few months ago when trying different roms and ended back up on Indian oxygenos A08. Then after toggling developer options, local update option was there. Anyways I am on android 13 now and it looks amazing! Thanks so much for the help, and I'll be sure to use these apks in the future.
JPower123 said:
Yeah honestly I was kind of surprised too lmao, Im pretty sure that I screwed up a few months ago when trying different roms and ended back up on Indian oxygenos A08. Then after toggling developer options, local update option was there. Anyways I am on android 13 now and it looks amazing! Thanks so much for the help, and I'll be sure to use these apks in the future.
Click to expand...
Click to collapse
Awesome! Glad to have another person on it. You and me are probably at this moment the only two on it that aren't on an India model!
So far, I'm liking it alot!
maamdroid said:
Awesome! Glad to have another person on it. You and me are probably at this moment the only two on it that aren't on an India model!
So far, I'm liking it alot!
Click to expand...
Click to collapse
Yeah i agree, its super smooth, and there have been few bugs. I do notice that swiping away notifications takes a lot of swipe if that makes sense. Also for future reference, I was able to install magisk by booting from the A0.8 patched image, even though it was for android 12, it worked like a charm (direct install), and I am once again rooted on Android 13!
JPower123 said:
Yeah i agree, its super smooth, and there have been few bugs. I do notice that swiping away notifications takes a lot of swipe if that makes sense. Also for future reference, I was able to install magisk by booting from the A0.8 patched image, even though it was for android 12, it worked like a charm (direct install), and I am once again rooted on Android 13!
Click to expand...
Click to collapse
Nice on the root! Glad that worked fine still.
I haven't noticed any issues with swiping away notifications yet. I'll have to pay closer attention.
The search issue when searching for an app and your search not clearing when you come back is quite annoying.
maamdroid said:
Nice on the root! Glad that worked fine still.
I haven't noticed any issues with swiping away notifications yet. I'll have to pay closer attention.
The search issue when searching for an app and your search not clearing when you come back is quite annoying.
Click to expand...
Click to collapse
Yeah the search issue was really annoying, but you can disable "smart search in app drawer" to go back to old search/fix the bug. Also have you had any issues with fingerprint? I cant tell if it got slower, or if I am just trippen... Also I realized the notifications just need an extra swipe/tap to clear all the way.
JPower123 said:
Yeah the search issue was really annoying, but you can disable "smart search in app drawer" to go back to old search/fix the bug. Also have you had any issues with fingerprint? I cant tell if it got slower, or if I am just trippen... Also I realized the notifications just need an extra swipe/tap to clear all the way.
Click to expand...
Click to collapse
Finger print seems fine for me.
Good call on the search, I have now disabled the smart search.
You're right on the notifications, sometimes it seems to need a little extra. Not always though, so maybe it's certain types of notifications...
OxygenOs13 open beta for eu is now live
does fps drop in pubg fixed ?
abdouyakuzataleb said:
does fps drop in pubg fixed ?
Click to expand...
Click to collapse
When do they exactly drop? I have it installed but I don't ever play it. If you give me more specifics I can let you know how it runs on the 13 beta.
try to play on smooth 60 fps and land on bootcamp sanhok
check if fps drops or stable 6
abdouyakuzataleb said:
try to play on smooth 60 fps and land on bootcamp sanhok
check if fps drops or stable 6
Click to expand...
Click to collapse
Hey sorry. I already flashed back to EU android 12 A08 now.
i did qntutu with and without performance mode