Related
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
IMPORTANT : Use leaked builds at your own risk
Download
(OP3 OnePlus3Oxygen_16_OTA_073_all_1903190037_c3d5b3a79f9b4895.zip)
(OP3T OnePlus3TOxygen_28_OTA_073_all_1903190038_308835b6760c41bd.zip)
Instructions (Read carefully)
* Flash through TWRP (by @dianlujitao) and do a Factory Reset before boot the device (source)
* Your device will became encrypted during boot (data partition may be corrupted on encrypted devices)
* magisk v18.1 is working
(source)
* Stock recovery will overlap TWRP unless you flash magisk before reboot.
Bugs:
None so far...
Thanks for initial testers:
@Chuck Bartowski
@himsin
Sounds amazing, waiting to see the final version coming out
FSadino said:
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
Click to expand...
Click to collapse
How will I know of I get selected for closed beta testing?? And when will close beta be available for testing
alrd apply hope this early appril can roll out
Closed beta pie for op3/t leaked
helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
Where?
helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
and why do you think that?
abhibnl said:
and why do you think that?
Click to expand...
Click to collapse
Because i download the rom from a leaked link
helderfp said:
Because i download the rom from a leaked link
Click to expand...
Click to collapse
Can you share a link via PM?
abhibnl said:
While I won't ask you to post a leaked build, can you post some SS running that ROM and showing this thread in XDA app to show that you are not just joking around and have actually used the ROM?
Or you can download AIDA64 and post SS from that app.
Click to expand...
Click to collapse
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
jay_snake said:
Where?
Click to expand...
Click to collapse
https://yadi.sk/d/Dj_6zddVg5-yog
Thread cleaned
Link restored
Please see rule 12
XDA has been the place to find leaked builds since there were leaked builds
Thank you for your cooperation
Does it work as a daily driver or still too buggy?
(he said, before inevitably rushing to install it)
helderfp said:
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
Click to expand...
Click to collapse
Appreciate it. I'll find and download it to test it over weekend.
Thanks for the build!
Any way to decrypt?
I tried flashing Magisk (18.1) after flashing the ROM but it didn't work.
I also tried flashing Magisk + Universal DM-Verity ForceEncrypt disabler (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but that gave me a bootloop.
To everyone who will rush to flash it - please don't just download and flash. Make sure you are ready for broken device, storage encryption and decryption errors, and data errors.
Make sure to take a complete backup of internal storage and then attempt to flash it using stock or twrp recovery.
Or you should rather wait til a developer figures out a way to make twrp compatible with its firmware for encryption/decryption errors
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Magisk is working, I'm now using the closed beta with Magisk 18.1.
At first boot Magisk Manager (the application) was not installed and I had to install it manually. Also, Magisk Manager was saying that Magisk was not installed, but a reboot solved it. Now it is working perfectly.
And, if you were responding to me, I'm sorry I wasn't very clear, I wanted to keep the phone decrypted (disabling force encrypt at first boot), but I have failed and I'm using the phone encrypted at the moment.
I just installed it via stock recovery with locked bootloader... Everything is fine..
himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Did you used stock or TWRP recovery?
I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Trippyy Doee said:
I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Click to expand...
Click to collapse
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Badger50 said:
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Click to expand...
Click to collapse
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
Magisk is the only way and there is no twrp
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Is there a working Magisk Canary build that can patch my boot.img?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Like @p70shooter said. There is no other way to root besides magisk, and there is no TWRP as of yet. If rooting with 20.2 didn't work, then try 20.1. You can find it here :good: https://github.com/topjohnwu/Magisk/releases
Trippyy Doee said:
Is there a working Magisk Canary build that can patch my boot.img?
Click to expand...
Click to collapse
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
p70shooter said:
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
Click to expand...
Click to collapse
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Trippyy Doee said:
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Click to expand...
Click to collapse
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Badger50 said:
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Click to expand...
Click to collapse
Yea I was certainly rushing . I used the wrong boot file. Thanks alot. Finally off work so now I get to enjoy rooting my first Pixel phone. ?
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
It's a patch.. it's not useless...
Baron60 said:
It's a patch.. it's not useless...
Click to expand...
Click to collapse
Yes patch as in security patch with some fixes. I understand that. Prolly i stick with mar update since i can't update to april patch. Thanks.
I've tried updating/installing using a vpn. Still no success. Don't know what's wrong...
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Then you can analysis the log
K9998 said:
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
Then you can analysis the log
Click to expand...
Click to collapse
Thanks. I will give it a try.
kxnzxmori said:
Thanks. I will give it a try.
Click to expand...
Click to collapse
No worries,
The typical message you will get if any of three partitions has been modified:
Code:
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
I have a Locked bootloader & I'm having the same problem. Please advise something.
I have the same problem. . i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
I have tried multiple times to install TWRP and every time it seems to get overwritten by stock recovery. I've tried everything I can find online. After successfully flashing recovery.img and sending command "fastboot reboot recovery" or command "fastboot reboot 'recovery.img'" it flashes orange for a fraction of a second then vibrates a second time and shows boot logo screen with orange state warning, then either boots to stock recovery, or it boots to the home screen. One person said he was running into the same issue as I was and was only successful by deleting all the partitions on the device and reflashing it. He doesn't remember the steps he used and I would like to avoid even trying to do that anyway.
My only goal is to obtain root on my device, even if I'm using AOSP, as long as it's AOSP Android 10 v222, however I'm having issues trying to build a version of AOSP for this device without being able to find the binaries for it.
With all that being said, my question is if anyone who has the Blu Bold N1 running with the Android 10 update and working TWRP installed could please dump the rom and send it to me or upload it for me somewhere. There is no way I can dump the rom of my own device because I cannot get TWRP to successfully boot, and Blu does not host the Android 10 iso for this phone anywhere.
Alternatively, if someone could find the binaries for this device or knows how to find them, I could successfully build my image of AOSP and obtain root that way. I would rather be on the stock android that comes with the phone, but if I can't root it then I don't care to move to something else.
On an unrelated note, this is the first time I've ever posted on this forum and I apologize if anything I'm asking for or saying goes against the guidelines.
Hey, I pulled the Android 10 OTA. Can that b of help ?
greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
YESS! I've been using this phone without root for months now, you'd be a lifesaver if you could show me where I can download it.
greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
emooverlord said:
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
Click to expand...
Click to collapse
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
greeneyez15o said:
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
Click to expand...
Click to collapse
I can't seem to get TWRP on it at all, with the boot img or the rom would it not work with magisk?
The 3 files attached are:
boot.bin: The contents of the original 'boot' partition.
boot-stripped.bin: Patched with an empty vbmeta image, to allow custom ROM flashing and the like. Generated by:
Code:
cp boot.bin boot-stripped.bin
avbtool erase_footer --image boot-stripped.bin
avbtool append_vbmeta_image --image boot-stripped.bin --partition-size 33554432 --vbmeta_image /path/to/google-empty-vbmeta.img
boot-magisk.img: Pre-patched with Magisk 23 Canary (23016).
These are all from the November 2021 security patch of A10 on the Bold N1.
Also: you can extract everything off of the live device with https://github.com/bkerler/mtkclient:
Code:
python ./mtk rl <path to backup>
will give you a dump of all of the partitions on the device. (Since 'userdata' is encrypted and the last one, when it gets there, just hit ctrl-C when it gets there and you'll have everything out of the backup.)
irony_delerium said:
These are all from the November 2021 security patch of A10 on the Bold N1.
Click to expand...
Click to collapse
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
GMSS75 said:
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
Click to expand...
Click to collapse
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
irony_delerium said:
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
Click to expand...
Click to collapse
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the boot image?
GMSS75 said:
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the bootee image?
Click to expand...
Click to collapse
I used avbtool on the stock image. Check how I created boot-stripped.bin.
Context:
- using crDroid latest (from late aug. I guess)
- patched boot.img with magisk and pushed it
- everytime I install smali patcher module I end up in bootloops afterwards.
I will obviously look into the smali patcher thread (here on xda), but here's my question:
Question:
How do I get access to the filesystem with TWRP, decrypt it outside or inside, as long as I can remove the offending module for instance?
I read many different threads but it's all bit and pieces here and there and kinda hard to follow, not applicable, talks about different versions, mixes a11 and 12 sometimes...
Anyways, if somebody can point me to some relevant documentation, let me know, I'll read. I have no restriction in terms of erasing the phone over and over, I just need access once a day to SMS in order to log into the office VPN.
well, whatever with getting access to filesystem. Smali patcher hasnt been updated for a few months, dev is apparently not online anymore (hope he's ok), and it doesnt work with A12. Guess I'll have to just wait for that one, stop being an idiot and toy with things I dont master for a while.
But I'd still be happy to educate myself further if somebody replies.
In the meantime... thanks everybody!
There was "unofficial" twrp (also orangefox) which has support decrypt, tou sold take a look around to find it (it was actually from the same dev)
There is a functional TWRP with decryption for Android 12, works well for me. Please ask if i should share it here.
My question is: does anyone know if there is the same functionality ( decryption ) also availabe for Android13 ?#
Thx
hanichl said:
There is a functional TWRP with decryption for Android 12, works well for me. Please ask if i should share it here.
My question is: does anyone know if there is the same functionality ( decryption ) also availabe for Android13 ?#
Thx
Click to expand...
Click to collapse
Ok so I need to find that unofficial one then, or try orangefox. Well. Right now I confirmed that smali patcher doesnt work with 12 anyways, so I'm not gonna bother much but it's good to know. Thanks!
liberteus said:
Ok so I need to find that unofficial one then, or try orangefox. Well. Right now I confirmed that smali patcher doesnt work with 12 anyways, so I'm not gonna bother much but it's good to know. Thanks!
Click to expand...
Click to collapse
See my attachment the posts before, works perfect for me !
hanichl said:
See my attachment the posts before, works perfect for me !
Click to expand...
Click to collapse
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
liberteus said:
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
Click to expand...
Click to collapse
Relying to myself, answered my own Euston by reading your post earlier. Will try it tomorrow! Thanks a lot!
liberteus said:
Smali patcher works for you, or the recovery decrypts filesystem?
Maybe i misunderstood you earlier. Going to read the thread once more. Thanks!
Click to expand...
Click to collapse
when you have installed this twrp, and you boot to recovery ( here: twrp ), you will be asked for your PIN , pass it and your data partition will be accessable from twrp recovery.
So twrp decrypts the partition !
Couldnt wait for tomorrow, had to test it now, flashed it after testing.
Works flawlessly. Not everything works the way I'd like it to work on my new phone, but it's good enough.
Not posting much on xda, but whenever I did, kind ppl like you Hanichi always replied and pointed me in the right direction, or like you did provided just the right file I needed. Dang that place is sweet (pun intended).
Thanks again!