Hi everyone,
Just wanted to let you know 11.2.9.9 is out for T-Mobile! If you know what's in the update, post here!
Thanks,
razercortex
I didn't screenshot the changelog but i think it was bug fixes and security updates but still looks like I'm on the December Android & security updates. I know i didn't see the same changelog as the global version and don't see xpan mode in the camera.
DarthVesh said:
I didn't screenshot the changelog but i think it was bug fixes and security updates but still looks like I'm on the December Android & security updates. I know i didn't see the same changelog as the global version and don't see xpan mode in the camera.
Click to expand...
Click to collapse
Yeah, unfortunately it seems they only updated the Android patch version to December 2021.
razercortex said:
Yeah, unfortunately it seems they only updated the Android patch version to December 2021.
Click to expand...
Click to collapse
boo! i really wanted to try the xpan feature..with the latest delayed updates, i'm really tempted to go back to unlocked cell phones only
I'm getting "installation problem" even after doing "restore images" in Magisk.
Do I have to completely uninstall it?
BTW, here is the update package:
https://android.googleapis.com/packages/ota-api/package/c66c9a73df49523c3468b0de7de76b449cc277c0.zip
Just unlock and do modem fix and go global
Libra420T said:
Just unlock and do modem fix and go global
Click to expand...
Click to collapse
Will I lose T-Mobile specific featuers such as name caller-Id?
vponomarev said:
I'm getting "installation problem" even after doing "restore images" in Magisk.
Do I have to completely uninstall it?
Click to expand...
Click to collapse
It may be helpful to uninstall Magisk, then patch the image again. A screenshot of the issue or details about the error would be helpful.
vponomarev said:
I'm getting "installation problem" even after doing "restore images" in Magisk.
Do I have to completely uninstall it?
Click to expand...
Click to collapse
I completely uninstalled it and tried to update and got same error again waiting for info
tancam said:
I completely uninstalled it and tried to update and got same error again waiting for info
Click to expand...
Click to collapse
For me it looks like boot partition was modified before I created a backup and Magisk created its own.
See this thread: https://forum.xda-developers.com/t/looking-for-v8-8-boot-img-for-tmo.4394211/
vponomarev said:
For me it looks like boot partition was modified before I created a backup and Magisk created its own.
See this thread: https://forum.xda-developers.com/t/looking-for-v8-8-boot-img-for-tmo.4394211/
Click to expand...
Click to collapse
I can't give 8.8 boot.img, but I can supply a 9.9 boot image for you.
vponomarev said:
For me it looks like boot partition was modified before I created a backup and Magisk created its own.
See this thread: https://forum.xda-developers.com/t/looking-for-v8-8-boot-img-for-tmo.4394211/
Click to expand...
Click to collapse
Honestly if know one provides img, just backup and MSM
Libra420T said:
Honestly if know one provides img, just backup and MSM
Click to expand...
Click to collapse
Yeah, that's my backup plan, pun intended
Is userdata partition the only one that I need to backup?
razercortex said:
I can't give 8.8 boot.img, but I can supply a 9.9 boot image for you.
Click to expand...
Click to collapse
Appreciate, but 9.9 will probably not work.
However, if you just updated to 9.9, you may still have 8.8 boot in currently inactive slot.
Well I can attach both boot.imgs, but no guarantees that I still have 8.8.
https://www.mediafire.com/file/0r5h9v4qj3u8r3c/boot_a.img/file is the only boot file I can grab you, both a and b boot.imgs are the same. You can try flashing the boot.img, it shouldn't cause much harm.
vponomarev said:
Appreciate, but 9.9 will probably not work.
However, if you just updated to 9.9, you may still have 8.8 boot in currently inactive slot.
Click to expand...
Click to collapse
I'm taking a look, and the 8.8 and 9.9 boot.imgs look exactly the same. They seem to be the same size, both my boot_a and boot_b.
razercortex said:
I'm taking a look, and the 8.8 and 9.9 boot.imgs look exactly the same. They seem to be the same size, both my boot_a and boot_b.
Click to expand...
Click to collapse
Yeah, the size will be the same. Did you binary compare them or got a checksum, because the contents may be different.
If you could share both, I'd really appreciate that! This may save me from having to MSM my phone and doing backup/restore to get to a good state.
Well I haven't had time to checksum, but the second file uploaded faster than the first, even though it was the same size. That most likely indicates MediaFire identified the images as similar, thus there isn't much difference in boot.img files.
Related
Here's the update.zip for the newest 5.1.1 leak build number D0F8...
https://mega.co.nz/#!iIFSRA5C!Q9KWmi3vdNc_lRN2c4RKA8GFzOsT0L8FYgl1yMg7-L8
http://pasteboard.co/1AOfi4By.png
You can sideload this file via the stock recovery
Code:
adb sideload update.zip
you must use lastest adb binary or it will fail.
Aaaaannd if you find any bugs you can downgrade back to CF6 5.1.1 no problem. I fully tested it Sorry Aou 100%
So, you're saying that the update will only be available for OCG users, not OF6? So, then, it's only an update for OCG -> OF8 ?
Weird.
Edit: NVM, I see what you're doing here. You're taking advantage of the idea that the phone will unpack this update.zip if it's already expecting to try to unpack and install the update.zip for OF6... clever.
Edit2: I'm thinking, perhaps we could create an OCG downgrade TWRP-flashable .zip that forcefully writes the OCG system & kernel to the device. It should be able to to, but I'm not sure that the OCG software would boot on the new OF6 bootloader...
Edit3: @Sunderwear - have you heard anything whether or not this leak includes a new sboot.bin (bootloader) ?
Edit4: Assuming the update.zip is signed properly, is there any reason we couldn't attempt to flash it using the factory/stock "e3" recovery?
Aou said:
So, you're saying that the update will only be available for OCG users, not OF6? So, then, it's only an update for OCG -> OF8 ?
Weird.
Edit: NVM, I see what you're doing here. You're taking advantage of the idea that the phone will unpack this update.zip if it's already expecting to try to unpack and install the update.zip for OF6... clever.
Edit2: I'm thinking, perhaps we could create an OCG downgrade TWRP-flashable .zip that forcefully writes the OCG system & kernel to the device. It should be able to to, but I'm not sure that the OCG software would boot on the new OF6 bootloader...
Edit3: @Sunderwear - have you heard anything whether or not this leak includes a new sboot.bin (bootloader) ?
Edit4: Assuming the update.zip is signed properly, is there any reason we couldn't attempt to flash it using the factory/stock "e3" recovery?
Click to expand...
Click to collapse
yes it comes with a new sboot.bin. and it wont flash the way it is right now because needs to be unpacked first.
here's a link for for what i was able to extract however is not the full thing .
https://mega.co.nz/#!HQlUyaBT!lwlFTQAQzmLZZN1ous8Q6vjoABBb5vMSeTdZx7HmcNg
Sunderwear said:
yes it comes with a new sboot.bin. and it wont flash the way it is right now because needs to be unpacked first.
here's a link for for what i was able to extract however is not the full thing .
https://mega.co.nz/#!HQlUyaBT!lwlFTQAQzmLZZN1ous8Q6vjoABBb5vMSeTdZx7HmcNg
Click to expand...
Click to collapse
Awesome. I took a look at the updater-script.
Best I can tell, it does update the bootloader (bot BOTA0 and BOTA1 with sboot.bin and cm.bin respectively). But it doesn't look like they're updating the revision number, because at the end, they update the system to SYSMAGIC002:
Code:
write_string_partition("/dev/block/platform/15570000.ufs/by-name/SYSTEM", 2000, "SYSMAGIC002", 11) || abort("fail to write secure_sysmgic in system.");
Noteworthy that this appeas to be exclusively an update from OF6 -> OF8, according to the stuff at the top.
Code:
abort("Package expects build fingerprint of samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2COF6:user/release-keys or samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2DOF8:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Edit: The sboot.bin seems to also saying stuff about SYSMAGIC002. And, for the heck of it, I tried to adb-sideload the update.zip from OF6 3e recovery. It fails the signature check.
Aou said:
Awesome. I took a look at the updater-script.
Best I can tell, it does update the bootloader (bot BOTA0 and BOTA1 with sboot.bin and cm.bin respectively). But it doesn't look like they're updating the revision number, because at the end, they update the system to SYSMAGIC002:
Code:
write_string_partition("/dev/block/platform/15570000.ufs/by-name/SYSTEM", 2000, "SYSMAGIC002", 11) || abort("fail to write secure_sysmgic in system.");
Noteworthy that this appeas to be exclusively an update from OF6 -> OF8, according to the stuff at the top.
Code:
abort("Package expects build fingerprint of samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2COF6:user/release-keys or samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2DOF8:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Edit: The sboot.bin seems to also saying stuff about SYSMAGIC002. And, for the heck of it, I tried to adb-sideload the update.zip from OF6 3e recovery. It fails the signature check.
Click to expand...
Click to collapse
yes...need someone with 5.0.2 to try to unpack it..maybe i'll get one by the shop tomorrow.
Sunderwear said:
yes...need someone with 5.0.2 to try to unpack it..maybe i'll get one by the shop tomorrow.
Click to expand...
Click to collapse
Cool, let us know!
- Also, for what it's worth, I created an "OCG downgrade" .zip, which does write the partitions just fine... But the device sticks on the boot logo. Kinda figured it wouldn't work.
Aou said:
Cool, let us know!
- Also, for what it's worth, I created an "OCG downgrade" .zip, which does write the partitions just fine... But the device sticks on the boot logo. Kinda figured it wouldn't work.
Click to expand...
Click to collapse
I got a s6 edge today and yes my trick worked..uploading unpacked update.zip right now..
Sunderwear said:
I got a s6 edge today and yes my trick worked..uploading unpacked update.zip right now..
Click to expand...
Click to collapse
What its new? any change?
fabioplata said:
What its new? any change?
Click to expand...
Click to collapse
you can find out for yourself later.. stability fixes etc..issues with the first 5.1.1 update.
Sunderwear said:
you can find out for yourself later.. stability fixes etc..issues with the first 5.1.1 update.
Click to expand...
Click to collapse
Is multiuser back ?for some reason they removed it from the offical from the last leak
And also is the ram isuue for multasking finally fixed?
frr1 said:
Is multiuser back ?for some reason they removed it from the offical from the last leak
And also is the ram isuue for multasking finally fixed?
Click to expand...
Click to collapse
I just upgraded the phone so cant fully judge..Multi user is still disabled but it's something that can be enabled with any CSC feature changer.
http://pasteboard.co/1AOfi4By.png
Sunderwear said:
I just upgraded the phone so cant fully judge..Multi user is still disabled but it's something that can be enabled with any CSC feature changer.
http://pasteboard.co/1AOfi4By.png
Click to expand...
Click to collapse
Oh ok let us know of mutitaking is better with the new update
Also where do i find a CSC changer?
The screen shot shows DOF8, but the thread title is COF8...?
flarbear said:
The screen shot shows DOF8, but the thread title is COF8...?
Click to expand...
Click to collapse
fixed. Typo...10chars
Raw support in oem camera app?
Sent from my SM-G925T using Tapatalk
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
mikeyinid said:
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
Click to expand...
Click to collapse
Lol
Sent from my SM-G925T using XDA Free mobile app
mikeyinid said:
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
Click to expand...
Click to collapse
Because this time i was prepared..same thing happened with the regular s6 lol .
I'm currently working on a TWRP-flashable OF8 ROM.
I won't bother with the Kernel right away, though. Until the source for OF8 shows up on Samsung's website we won't have root on OF8.
Aou said:
I'm currently working on a TWRP-flashable OF8 ROM.
I won't bother with the Kernel right away, though. Until the source for OF8 shows up on Samsung's website we won't have root on OF8.
Click to expand...
Click to collapse
I havent tested but it should boot with the current custom kernels.
Hi,
Could anybody extract boot.img from OTA experience 8.0 (Pie) before installing it, so patched boot could be generated by Magisk?
I'm using SATV 2015.
Thanks!
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
hardwarechaos said:
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
Click to expand...
Click to collapse
Thanks!
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Hi
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
Just hit the same problem with my 2015 :-/
Regards
Chaos
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
https://forums.geforce.com/default/topic/1158216/shield-tv/shield-experience-upgrade-8-0/
Adds rooting feature preventing incorrect images from being flashed to SHIELD
Hi
sash11 said:
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
Click to expand...
Click to collapse
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
hardwarechaos said:
Hi
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
Click to expand...
Click to collapse
It is a system application now. That's why I could not find it in the list of regular apps. Very weird. nVidia must classify it as such and put in into that category.
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
Same to me, if I boot with magisk_patched, it keeps stuck at nvidia Logo
Guess we have to wait.
Maybe the boot.img of the developer image, once it is released, might work. Or hopefully someone finds a way too root again.
Regards
Chaos
Hi, just a question
Since Nvidia will release an unlocked Full 8.9 developper OTA (hope it'll be soon) , isn't it better to root that than trying on the official "locked" one ?
As for me, since i started rooting my shield, i always did it that way without problems.
Btw i was thinking of trying the same trick as you did but since i hadn't much time ... Anyway you saved my day, thanks
One last thing for those of you who are dev or android enthousiast, i make use of a fantastic Magisk script called xXx No Limits wich i find very neat.
My questions are
* Could such a script be usefull in case of the Shield ?
[Depending, i guess on wich Magisk modules are compatible with the Shield. Is there a list for compatible modules ?
* If worth it Could someone make such a script for the Shield ?
Thanks in advance for giving me clues, have all a great day !
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Hi
TAM1m said:
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Click to expand...
Click to collapse
yes I have it here. Uploading to my gdrive.
Just drop me a PM and i will send you the link.
Regards
Chaos
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
nvm.. i found it
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
elliwigy said:
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
Click to expand...
Click to collapse
The question is if it's the same with boot.img from the dev. rom...that would be bad.
trohn_javolta said:
The question is if it's the same with boot.img from the dev. rom...that would be bad.
Click to expand...
Click to collapse
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
oldpoem said:
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
Click to expand...
Click to collapse
Hmm.. yeah. I now think it's because of android pie not necessarily because of changes from nvidia.
Full recovery images are available for download for Shield Experience 8.0.0
https://developer.nvidia.com/gameworksdownload
Would you mind to share the best solution when you succeed?
Good news, global ROM receives New update today.
Lenovo Z6 Pro.
Ok, so what's new / improvements ?
benjieb said:
Ok, so what's new / improvements ?
Click to expand...
Click to collapse
I don't know, I reinstall the firmware and lose the package, now system update refuse to give me again OTA ;-;
benjieb said:
Ok, so what's new / improvements ?
Click to expand...
Click to collapse
I don't have any idea how to recover my update ota, lenovo is trolling me.
I don't understand what your issue is. But if you missed OTA, is will come again soon.
I think one way to help that is to clear cache of update app. Just google it.
While you are there, once the OTA is downloaded to your phone AND before actually upgrading, it would be good to copy the update file to your PC and share it with others who don't get the OTA.
benjieb said:
I don't understand what your issue is. But if you missed OTA, is will come again soon.
I think one way to help that is to clear cache of update app. Just google it.
While you are there, once the OTA is downloaded to your phone AND before actually upgrading, it would be good to copy the update file to your PC and share it with others who don't get the OTA.
Click to expand...
Click to collapse
I found the solution, I'll repost the fastboot link that alexeei provided.
The overall improvements I've been noticing:
Connection problems that sometimes occurred in my region, are no longer giving.
Battery I noticed is lasting about 45 minutes longer.
PT-BR was basically 100% implemented in every layout.
The 4G connection has been improved.
I also believe that they have made some changes in the kernel, because the way the cores are working, is different gives version 284, ie better, I'll find out if in Benchmark improved anything.
And the audio in dolby atmos, I'm feeling that the audio has improved, it's louder and clearer.
camera haven't tested yet
However this is it: D
Here the link
Thanks for @alexeei
https://androidfilehost.com/?fid=1899786940962594224
hehk1234 said:
Here the link
Thanks for @alexeei
https://androidfilehost.com/?fid=1899786940962594224
Click to expand...
Click to collapse
this fastboot requires open bootloader?
x-geo said:
this fastboot requires open bootloader?
Click to expand...
Click to collapse
yes
alexeei said:
yes
Click to expand...
Click to collapse
And i can close it again after install it?
x-geo said:
And i can close it again after install it?
Click to expand...
Click to collapse
No, it's not neccessary
ok, i'll install it after it charges... this version comes with the new 4D Utouch?
In first Thank's a lot for the file !!!!
But after the flash , my phone don't reboot, hopefully reflash Alexeei Twrp solve my problem, evrithing seem ok now.
More info when more tested the rom
@alexeei, the file you shared is full ROW rom?
If so, when flashing with TWRP over an older version of ROW, will it keep data and apps?
Thanks!
I flash over my 284st the alexeei fastboot rom, but with the fastboot .bat.
And i have keep all my app,data and setting.
But the phone don't work in first attempt, must reflash the twrp for fix boot.
Don't know if this problème is only for me or more general.
My config before flash. Rom 11.0.284st + twrp alexeei + magisk 19.3.
Now everything seem ok and perf is good, except aod still dont work.
benjieb said:
@alexeei, the file you shared is full ROW rom?
If so, when flashing with TWRP over an older version of ROW, will it keep data and apps?
Thanks!
Click to expand...
Click to collapse
yes
---------- Post added at 08:27 PM ---------- Previous post was at 08:24 PM ----------
wlcbtd said:
I flash over my 284st the alexeei fastboot rom, but with the fastboot .bat.
And i have keep all my app,data and setting.
But the phone don't work in first attempt, must reflash the twrp for fix boot.
Don't know if this problème is only for me or more general.
My config before flash. Rom 11.0.284st + twrp alexeei + magisk 19.3.
Now everything seem ok and perf is good, except aod still dont work.
Click to expand...
Click to collapse
You only need flash vbmeta with --disable-verity option, i make it default in installer script in future releases.
Ok , thank's for the info !
How can I install this update?
Brillant !
Do you think it can be flashed over CN rom and keep data and apps?
Also, do you know where to find same type of rom file with latest CN rom?
I want to try latest ROW, but I know I will revert back to CN.
ManCast said:
How can I install this update?
Click to expand...
Click to collapse
See post #30 on these tread
https://forum.xda-developers.com/android/help/rom-lenovo-z6-pro-l78051-qpst-edl-t3947149
, same thing for these update.
But only if you already are in raw rom, update from chinese is untested by now.
If you are having the cannot update issue and have the global variant of the OP9 Pro, you probably had flashed the EU (or other / wrong software version) boot.img.
If your software version is anything other than 11.2, (including 11.2.1.1) you will need to get a boot.img from someone else or pull it from OnePlus website for your software version (once OnePlus gets to adding the OnePlus 9 Pro to their website) for that OOS Software version and can still use the following, but replace steps 3 and 6 with your .img file name.
If your software version is 11.2 and you have a global model, the stock boot.img for global 11.2 is attached.
Simply plug your phone into the computer with USB debugging enabled and trust the computer for the adb connection. Open up command prompt window and make sure you cd [platform tools \ adb directory], a.k.a. change the command prompt directory to your platform tools / adb folder.
Type in the command prompt window: adb reboot bootloader
Once in bootloader, type: fastboot boot 11.2_global_OP9Pro_boot.img
Verify the phone boots
If it boots fine, follow step 2 again then...
Once in bootloader, type: fastboot flash boot 11.2_global_OP9Pro_boot.img
You will now be unrooted and able to update your OP9 Pro to the latest software version, which is currently (as of 4/2/21) 11.2.2.2.
All credit goes to purpleman2k for providing the boot image on 11.2 Global and other diagnosing help.
-----------------------------------------------------------------------------
11.2 Global Boot.img download links:
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io
Filebin | 84b77xbio25j9cfh
Convenient file sharing. Think of it as Pastebin for files. Registration is not required. Large files are supported.
filebin.net
Contact me if links are expired when you try to download.
Prior to this it would download the OTA update but I would have error installing. I'm not unable to download it.
Do you know where the OTA is download is stored so I can manually remove it and try to download it again
do I use this if I want to get back on the global firmware? I flashed the EU to get the latest update as I couldn't get the updates due to my EU boot.img.
Also, do we patch it to get root again?
ahh123 said:
Prior to this it would download the OTA update but I would have error installing. I'm not unable to download it.
Do you know where the OTA is download is stored so I can manually remove it and try to download it again
Click to expand...
Click to collapse
Its a hidden folder in storage. It's under ".ota".
vibrantliker said:
do I use this if I want to get back on the global firmware? I flashed the EU to get the latest update as I couldn't get the updates due to my EU boot.img.
Also, do we patch it to get root again?
Click to expand...
Click to collapse
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
bulletbling said:
Its a hidden folder in storage. It's under ".ota".
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
Click to expand...
Click to collapse
It's not there. When I start up the OTA update, it immediately states it "Couldn't update".
ahh123 said:
It's not there. When I start up the OTA update, it immediately states it "Couldn't update".
Click to expand...
Click to collapse
If it's not there then it's not downloaded.
bulletbling said:
Its a hidden folder in storage. It's under ".ota".
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
Click to expand...
Click to collapse
I'm on 11.2.2.2 BA, but would like to get back to AA 11.2.2.2
vibrantliker said:
I'm on 11.2.2.2 BA, but would like to get back to AA 11.2.2.2
Click to expand...
Click to collapse
Currently that is not possible until OnePlus posts the full system images or a fellow member can get a fresh one and backed up and packed for install.
bulletbling said:
Currently that is not possible until OnePlus posts the full system images or a fellow member can get a fresh one and backed up and packed for install.
Click to expand...
Click to collapse
ok thanks
bulletbling said:
If it's not there then it's not download
Click to expand...
Click to collapse
Makes sense. I'm not sure why it's no longer even able to download the update.
I get an installation error and when I hit resume, it states "couldn't update, installation problem"
ahh123 said:
Makes sense. I'm not sure why it's no longer even able to download the update.
I get an installation error and when I hit resume, it states "couldn't update, installation problem"
Click to expand...
Click to collapse
What software version are you on? And are you rooted?
bulletbling said:
What software version are you on? And are you rooted?
Click to expand...
Click to collapse
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
ahh123 said:
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
Click to expand...
Click to collapse
That boot image is for 11.2., which is not for your 11.2.1.1, that's why.
Standby for upload...
ahh123 said:
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
Click to expand...
Click to collapse
This is either 11.2.1.1 or 11.2.2.2 global boot.img. Sent to me by someone else for testing. Go ahead and try it with above instructions.
boot_wife.img
drive.google.com
If it doesn't work, I have two more for you to try.
bulletbling said:
This is either 11.2.1.1 or 11.2.2.2 global boot.img. Sent to me by someone else for testing. Go ahead and try it with above instructions.
boot_wife.img
drive.google.com
If it doesn't work, I have two more for you to try.
Click to expand...
Click to collapse
Thanks, so that was definitely part of the problem. The OTA now downloads but fails on installation. When I press resume to try again, it restarts the download.
ahh123 said:
Thanks, so that was definitely part of the problem. The OTA now downloads but fails on installation. When I press resume to try again, it restarts the download.
Click to expand...
Click to collapse
Is the .ota folder still empty / not there?
bulletbling said:
Is the .ota folder still empty / not there?
Click to expand...
Click to collapse
Don't see an .ota folder (I do see other hidden folders)
Edit: it's seems like it's installing now, "installing system update." Still fails and no .ota folder
ahh123 said:
Don't see an .ota folder (I do see other hidden folders)
Edit: it's seems like it's installing now, "installing system update." Still fails and no .ota folder
Click to expand...
Click to collapse
If it's still not working, try these boot images:
global_boot.img
drive.google.com
global_boot2.img
drive.google.com
bulletbling said:
If it's still not working, try these boot images:
global_boot.img
drive.google.com
global_boot2.img
drive.google.com
Click to expand...
Click to collapse
It seems like the same issue. Guess I'll just wait for the full download to be available
ahh123 said:
It seems like the same issue. Guess I'll just wait for the full download to be available
Click to expand...
Click to collapse
That's unfortunate. Make a post and see if anyone has the global boot image for 11.2.1.1.
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
nickdagriff said:
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
Click to expand...
Click to collapse
cant root dp2
will cause cash dump everytime
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
Do you know why
encoded
FizzyAps said:
encoded
Click to expand...
Click to collapse
Do you think I should just throw myself off a building?
i mean its beta what did you except lol
I was just hoping to be able to test it and root it like every other open beta.
What about twrp
You cant flash anything at this time
It will cash dump
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Burt Squirtz said:
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Click to expand...
Click to collapse
Yes I tried rooting both and they both end In cash dump
FizzyAps said:
Yes I tried rooting both and they both end In cash dump
Click to expand...
Click to collapse
How did you try though? Install to inactive slot, AND adb? Or just one of the other?
flashed patched img on both slots
FizzyAps said:
flashed patched img on both slots
Click to expand...
Click to collapse
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
ENCODED, NO METHODS WORK....
I rooted successfully with a Chinese tool
It works on both OOS12 and ColorOS12
Burt Squirtz said:
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I used this method to root last night and can confirm it works on OB 1 A12. I did the vbmeta part before flashing boot.img and didn't do the vendor_boot part at all.
https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/ this is the guide I followed.
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
ecera said:
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
Click to expand...
Click to collapse
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
terlynn4 said:
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
Click to expand...
Click to collapse
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
ecera said:
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
Click to expand...
Click to collapse
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
terlynn4 said:
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
Click to expand...
Click to collapse
It probably does boot a bit faster. Like you said that message is an extra few seconds. To me its not really noticeable, maybe to someone else it might be.