yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] eagleeyetom:
It's been a while since I bought my last Bluetooth speaker, and we all know how pacey the technology is. A nice piece of tech from a couple of years ago is now a dated tool. Given the above I figured that once again I will check what Tribit has to offer. This time I purchased the Tribit StormBox Micro 2. The name is long and not very informative, but this little guy surprises.

Looks and Durability: The StormBox Micro 2 not only looks good but can take on some rough adventures. With an IP67 rating and a rubberized exterior, it's waterproof, dustproof, and built to withstand whatever you throw at it. This speaker will be your trusty companion on all your escapades.

But wait, there's more! The StormBox Micro 2 boasts a detachable rubber strap that's a game-changer. You can hook it onto your trousers, belt, your bike, or pretty much anything. This nifty feature makes it ultra-portable and ready for action in any situation.

Sound That Makes You Smile: What sets this speaker apart is its impressive sound quality. With 10W of power, it's louder than you'd expect from a speaker this size. Bass-heavy tunes stay crystal clear even when you crank up the volume. From home chill sessions (although it's quite hard to adjust the level, as the speaker is loud in general) to outdoor parties, this pint-sized powerhouse has got you covered.

Pairing and Staying Connected : Bluetooth 5.3 ensures you have a rock-solid connection up to 30 meters away (that's a 100 feet for you, Yanks). Pairing is a breeze, and it stays connected like a champ. Plus, with a USB-C port for charging, it's convenient and future-proof.

Jam On-The-Go: Here's where things get even better. The 3.6V/4700mAh battery isn't just any battery. It powers the speaker for up to 12 hours on a single charge, giving you more music for longer. If it wasn't impressive enough, the quick charging feature gets you back in action in no time.

A Minor Hiccup: Some users experienced an issue with the speaker turning off a second after being turned on. However, a firmware update appears to resolve this issue, ensuring a smoother experience after the update. Tribit offers an app to handle the updates. It's nothing special, but gets the job done.

In a Nutshell: The Tribit StormBox Micro 2 is a portable speaker that blends style with serious audio performance. It's rugged, waterproof, and dustproof, making it your perfect adventure buddy. With its impressive sound, extended battery life, the convenience of the Tribit app, and the versatile rubber strap, it's a winner. The minor hiccup at the start is a small bump in an otherwise smooth ride. If you want a portable speaker that's small in size but big on sound and versatility, the Tribit StormBox Micro 2 is the one to beat. It costs $59 and you can get it on official Tribit's website or at some other retailers, like Amazon.
[Device Reviews and Information] ZG_DEV:
What a great review, thanks, mate :)
[Device Reviews and Information] eagleeyetom:
I'm glad you like it!

Sent from motorola edge 30 neo using ReLabs
[Samsung Galaxy S23 Ultra] p.dixon0:
Does anyone know of any decent, non tempered glass, screen protectors for the S23U that actually cover the entire screen, and not stop 1 or 2mm from each of the edges which is really annoying. And bonus if it doesn't have a cut out for the camera too...
[Samsung Galaxy S23 Ultra] Martin William:
Get a good brand of nano liquid
[Samsung Galaxy S23 Ultra] Beefheart:
Amazon.co.uk

UV tempered glass but ignore the bad reviews, as I said in the other thread the majority of bad reviews for screen protectors are simply people who don't know how to put them on properly.

I've applied one of these to three phones now with no issues, you wouldn't even know they're installed unless you look closely. Follow the instructions and watch the video carefully.

If you insist on non-tempered glass I've heard good things about the official Samsung one.
[Samsung Galaxy S23 Ultra] hand-filer:
I think you're looking for something that doesn't exist. Screen protectors are sized to work with phone cases which require some clearance to prevent contact with the protector.
[Samsung Galaxy S23 Ultra] gsser:
Basically a ripoff version of uv dome glass or spigen. Been using this for couple of weeks/months. Havent got any complaints.

https://a.aliexpress.com/_mLICG9Q

I always use a uv curing glass for any curved screen phones. Never disappointed me.

If you are going to use a uv glue curing glass, you have to be careful and patient while applying these. The end result you are going to get depends on how good you apply these.
[Samsung Galaxy S23 Ultra] hand-filer:
As a recent convert from film to glass, I am in complete agreement.
[Samsung Galaxy S23 Ultra] Gabboxxx:
Hi i use smart devil

Its like hidrogel, but with uv ligth it turns hard, touch like glass .

I found it on aliexpres

View attachment 6033040
[Samsung Galaxy S23 Ultra] Beefheart:
You need to be careful with cheap knock-offs. The protector might go on fine and look great, but if the gel is less premium, it can harden like glass and the protector if it ends up damaged be almost impossible to remove without damaging your screen. There are plenty of videos online showing such removal attempts, it's not a pretty sight.

The one I recommend is linked on one of my previous posts in this thread. You get 3 of them in the pack and they go on absolutely fine providing you follow the instructions, and, whilst they're secure, they come off easily.
[Samsung Galaxy S23 Ultra] muhammadshais:
What about if you want to remove it?? Have you tried removing it I have heard most of these rip offs can't be removed without damaging screen.
[Samsung Galaxy S23 Ultra] hand-filer:
Confirmed removable with zero residue left on screen.

IMBZBK [4+4 Pack] UV for Samsung Galaxy S23
[Samsung Galaxy S23 Ultra] gsser:
Yes i did, it is easily removable as the uv glue becomes somewhat a gelatine film. It doesnt really leave any residue.
[P3400 ROM Development] Addicted2xda:
Hi,

Can some one please from this post tell me two things:

1. How is the performance of Gene? I mean is it good, ok or average?

2. To upgrade the OS by downloading any of the ROMs from this forum, do I need to USPL it (I am planning to by a HTC P3400 which is not hooked to any network - that is I will buy it from a retail outlet and pop in whatever sim I feel like)

Some one reply ASAP please

Thanks
[P3400 ROM Development] ankit360:
@ 9500 what u aspect ?

as u r using k790i the good camera phone the quality of this phone camera is worst why i say worst becoz i also use k790i and addicted of there pics quality
[P3400 ROM Development] Addicted2xda:
Initially while buying the K790i, I thought camera WAS important, I no longer think so. Actually now I dont give a too penny's damn for the camera quality, any way they will never be good as a digi cam. But I was wondering if I should go for Asus P320 or HTC 3400. Becauase P320 comes with WM 6.1, also the price diff is not that much :rolleyes:
[P3400 ROM Development] bitsandpieces:
well, the asus one does hv wm6.1 and also gps, but the screen is smaller.

which is why i would stick to gene as long as u dont need th gps. the performanmce is pretty much ok. once u start tweaking/installing then it is a delight that such a cheap phone could so so much.
[P3400 ROM Development] Addicted2xda:
Thanks for your help. Got My self Gene. For the tweaking part, will wait till I get familiar with it. I am quite confident with Vox, but a total newbie for WM Professional :D
[Google Pixel Fold] fred2546:
SOLVED

I am trying to transfer a video file that I created but it is large, about 6gigs. I've tried usb cable and via Droid Transfer. It does not seem to work. Is it a Pixel, Fold or Android limitation?

And way to do this?

--------------

Used Airdroid

I found a solution using AirDroid. It apparently bypasses some inherent Android limitation or is it the internal sd "card"? What is interesting is that I noticed that I have 3 or 4 other files about that size or larger (my China trip video is 8gigs) already on the Fold. They probably migrated from prior devices.
[OnePlus Open] g96818:
This is primarily for the CPH2551 NA Rom. I do not know if it works for IN and EU models, nor was I able to find out what the IN and EU model numbers are.

I have validated these instructions work for the CPH2551 NA model ONLY, but it's your choice to follow it or not. I'm not responsible if you mess up and flash the wrong software.

CAUTION: For EU/IN models, although the model number is the same as the NA model, the actual rom and OTA files are not the same. You can use this guide to root and you can download your full rom update file from Oxygen Updater or below. Don't use the OTA download from Oxygen Updater since it might not be correct for the version you're updating from. You shouldn't have to restore images before updating, but recommend you do anyways for unrooting purposes.

WARNING: Mostly for NA owners, but also EU owners who have installed the Android 14 IN beta, you now have a IN phone. Don't use NA or EU OTA files from here or Oxygen Updater unless you flash your device back using the full rom.

DISCLAIMER: Not my fault if your phone bricks or breaks.

Spoiler content hidden.

Rules to ask questions:

1. Only CPH2551 related questions allowed.

2. State your device firmware version and region (i.e., 13.2.0.114 - NA).

3. Don't ask for help regarding TWRP or Unbrick in this thread. Ask for help in their threads.

4. Don't complain something isn't working right if you installed anything else besides Magisk Canary.

Phase 0: OPEN your phone.

Phase 1: Unlocking the bootloader (Part 1)

Spoiler content hidden.

Phase 2: Installing drivers

Spoiler content hidden.

Phase 3: Recognizing the phone and unlocking the bootloader (Part 2).

Spoiler content hidden.

Phase 4: Rooting

Spoiler content hidden.

Additional important files to back up after every update.

Spoiler content hidden.

OTA Update Instructions:

Spoiler content hidden.

Boot and OTA download files:

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Unbrick:

https://xdaforums.com/t/unbrick-oneplus-open-using-official-flash-tool-5-6-6-in-edl-mode.4651747/

:coffee:🤗 https://www.buymeacoffee.com/xijingpooh or https://cash.app/$XiJingPooh
[OnePlus Open] ZG_DEV:
Wonderful guide, mate !

Thank you 😊
[OnePlus Open] egandt:
QUICK ANSWER FOR OTHERS: after running fastboot flash unlock, press vol+ once and then power!

E:\Oneplus open\Open>..\fastboot.exe getvar current-slot
current-slot: b
Finished. Total time: 0.028s

E:\Oneplus open\Open>..\fastboot.exe flashing unlock
OKAY [ 0.029s]
Finished. Total time: 0.030s

However nothing happens when I run "fastboot.exe flashing unlock", I waited for 30 minutes, should be instantaneous or near about, obviously fastboot is working based on the command above, but unlock is not returning any error, but not doing anything either. Odd looking fastboot screen as well, not very helpful have no idea what 6-10 means, however looks to me like fastboot is not configured correctly, I'm on .114 having updated the phone.

Edit1: Now in theory I should have to press a physical button, but volume up/down does nothing and power, well reboots.

Edit2: Unable to boot into flashboot using buttons either, I can get to recovery Vol-down+Power but can not boot directly to fastboot execpt via ADB, since the fastboot screen is not what I'd expect, or one that allows me to press any buttons, I'm stuck at this time, and need root to use Swiftbackup to restore so I can mail in my old phone.\

Edit 3 found this means:

已进入Fastboot
长按电源键6〜10秒或重装电池退出
What means
You entered Fastboot
Press and hold power button for 6 - 10 seconds or reload battery to exit

But this makes no sense at all, on a plus open with no battery, and only found one reference to this on the entire web.

Edit4: Ok so press Vol+ once and then power to unlock when on fastboot, even without a screen to view.

E:\Oneplus open\Open>..\fastboot.exe oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.003s]
Finished. Total time: 0.003s

Then I ran:

E:\Oneplus open\Open>..\fastboot flash boot_b boot_b.img
Sending 'boot_b' (196608 KB) OKAY [ 4.873s]
Writing 'boot_b' OKAY [ 0.060s]
Finished. Total time: 5.131s

E:\Oneplus open\Open>..\fastboot flash init_boot_b magisk_patched-26302_VhkoG.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.204s]
Writing 'init_boot_b' OKAY [ 0.004s]
Finished. Total time: 0.354s

Finally working root!
[OnePlus Open] g96818:
I'm assuming you have the driver's installed and you don't have the yellow triangle while in fastboot mode.

Why are you using fastboot.exe? There is no .exe in the command.

Did you go into developer options and enable OEM unlocking?

Vol up + power to get out of that fastboot reboot screen.

Vol up + vol down + power to boot the bootloader.

Try this:

fastboot flash unlock

Btw, what did you do to get the 6-10 sec reboot screen? You haven't unlocked your bootloader so you shouldn't see that yet.
[OnePlus Open] egandt:
Note I used: PlayIntegrityFix from PlayIntegrityFix_v9.9 as safetynet-fix-v2.4.0-MOD_2.0 did not pass CTS for me. Otherswise CTS in YASNAC failed.
[OnePlus Open] g96818:
That's fine, but I said mod 1.2 works and the other newer versions don't.

Can you get L1 with Netflix?
[OnePlus Open] juancarlos5:
Mod 2.0 it's broken. I confirm it works with mod 1.2 or 1.3zygisk

Safetynet release

View attachment 6027565

Netflix & D+ work with L3
[OnePlus Open] egandt:
I tested a few Magisk Modules:

Pixelify-v2.2, breaks sim manger (keeps crashing), breaks Google Fi, if you do not mind the notification seems fine otherwise

open-fonts: Works fine

safetynet-fix-v2.4.0-MOD_2.0: As stated above did not work for me

PlayIntegrityFix_v9.9: Worked well Got L3 support.
[OnePlus Open] zNiiC:
Everything is working but I can't seem to get Netflix working. First it said the network couldn't connect so I deleted and reinstalled tried the steps but now even after updating in play store or manually with the APK it says it's an outdated version.

Anyone able to get it working? Using safetynet 1.2 (if that matters)
[OnePlus Open] g96818:
Try the steps again. make sure you install the first one. it is completely incompatible, but you need that to trick it.
[OnePlus Open] zNiiC:
So install first, open then force stop through app info then install over? That's what I did twice but I'll try again.

Tried different safetynet versions and this is on 1.2. 2.0 gave and error so I'm not sure if this is supposed to be normal
[OnePlus Open] g96818:
2.0 doesn't work.

Install the first, then, the second, and third.

Not sure how else to help you if that doesn't work, cause that's what I know works for me.

You could try downloading and installing other versions of the app from apkmirror
[OnePlus Open] zNiiC:
Huh yeah I've been doing it that exact way. Guess I'll just mess around with other versions.
[OnePlus Open] centifanto:
Thank you very much @g96818 for this well laid out guide.

I am very experienced/comfortable with rooting all my past devices, but I am have never heard of a `init_boot` before when rooting. Is this a new system structure for Android?

Related to this, with previous phones, if I flashed a patched `boot.img`, I would not be able to uninstall Magisk temporarily with the app before an OTA, since it wouldn't have the stock boot backed up. My normally process is just to boot the patched `boot.img`, and then patch the stock boot from within the Magisk app so it would have the stock boot backed up so I could restore and take OTAs. I noticed in your OTA update section, you have the normal steps to uninstall Magisk but in my experience this wouldn't work if I had flashed a patched boot manually from fastboot. Does your instructions work with this new `init_boot` being flashed as it's a different section of the system from the regular `boot.img`? Hoping you can clear this up for me. 🙂

Also thanks for the Netflix workaround. I've tried in the past to get it to worked on my rooted 1+ devices and never could. Your instructions are the first that actually worked!
[OnePlus Open] g96818:
Init_boot is new. First noticed it on op11, but I think it's selective cause the Nord n30 still uses the boot. Magisk now makes a backup when you patch the init_boot regardless if you're rooted or not. The easiest way to check is to look for the backup in /data or just restore the boot image and see if it gives you and error. If it restored, then just perform a direct install to root again.

This phone won't let you boot the patched init_boot, which is why you need to flash it. It also won't let you boot the kernelsu file. Booting a patched boot file is possible, but does nothing.
[OnePlus Open] oncestruck:
I was totally thrown off too by the unusual looking bootloader but then I opened the phone and was greeted with what I was expecting. unfortunately spent hours to figure that out.
[OnePlus Open] nsmarcus:
I tried this, after updating it still says this app is not compatible with your device. any ideas?
[OnePlus Open] nsmarcus:
I had this same problem, until I realized the normal fastboot menu etc was on the inner display.
[OnePlus Open] g96818:
The first one won't be compatible, but it's important to install it. Idk why, it just works. Make sure you're not clearing the cache or app data. It won't work if you clear the data.
[OnePlus Open] nsmarcus:
Ah nm I missed the second version you have to install first.

So installed first one, incompatible. Force stop, install second one incompatible.

Right, the first one is incompatible, installed that didn't clear cache or data, force stopped netflix. then updated netflix from the play store, and the updated version also says incompatible. Even tried installing the beta version from apk mirror and also still incompatible.
[OnePlus Open] tyracz:
ok so I have rooted oneplus open sitting on .202, i have available .203 incremental update. I go to magisk, remove the image but i get message about "images not existing", I download updater, downloaded .203 inceremental and placed it in main dir. at 99% each time i get "update failed". I even tried to do official syste update, it also fails....any idea what am I doing wrong?
[OnePlus Open] Romans8vs1:
Nevermind.
[OnePlus Open] g96818:
delete your magisk app and install canary. download and patch the .202 init_boot, then try restoring. if that doesn't work, then flash the .202 init_boot the same way you flashed the patched, update and root again.
[OnePlus Open] patrickvh:
Just updated to .203 EU and rooted with the new init_boot.img (magisk_patched-26400_uPOHZ.img).

Also installed the SafetyNet fix (safetynet-fix-v2.4.0-MOD_1.3-Zygisk.zip).

Has anyone else have the problem that no apps can notify on lock screen and on top anymore?

No error, they just do not pop-up anymore.

Tried with banking (Dutch ING), Outlook and WhatsApp.

Thought maybe some power saving setting so changed of lot of them.

Not sure if it is related to the update itself, rooting or SafetyNet fix.

Saw in Google Backup that SafetyNet did change the device name.

Google said I never made a back-up of this device.

Edit: Removing SafetyNet fix (with reboot) did not fix anything. Downgrading to .202 seems not possible. Not with the official tool but the 'OPLocalUpdate_For_Android12_13.apk' fails also with saying the version is older and not safe so not allowed.

Edit2: Couple of hours later. Did a factory reset, restored phone from Google backup cloud, Magisk and root where also there already. Did not expect that! Does rooting survive factory reset also or does Google somehow knows how to restore that as well?

Configured Outlook and some other apps. Good news is pop-ups are working for them.

Maybe the SafetyNet fix? Wanted to use that for McDonalds app but before factory resetting it turned out not fixable, McDonalds would always say tampert device. So will not be installing SafetyNet fix and hope when I configured and restored everything, everything works as it should.

Edit3: A few days later and still no problems. Not planning on installing SafetyNet fix so will not know if that was the problem.

If there are other EU users who are on .203 and did install SafetyNet fix, let us know which version. As v2.4.0-MOD_2.0 is newer but does not work as it should.

Come to think of it I did install 2_0, removed it and that's installed 1_3. So also that could be the problem?
[OnePlus Open] FoxyDrew:
I'm on latest .203 as well, rooted. Not having this issue, notifications coming in just fine.

I'm on US firmware though, so could be a EU bug. Also no reason for SafetyNet fix so I never flashed that.
[OnePlus Open] tyracz:
so i got the canary, now when i go to magisk and uninstall imates i get proper notification , i go into local updater again and it failes at 99%. where can i get original .202 init_boot?
[OnePlus Open] g96818:
from the first post
[OnePlus Open] tyracz:
Sorry got a little lost in the threads, ok so I got canary installed, I pulled new .202 init boot from 1st post, i flashed it via CMD. I do not have root anymore, I went to local updater and tried to install the .203 incremental update, it went thru. i pulled new .203 init_boot from 1st post and patched with magisk and copied to SDK folder. restarted phone, placed it in fastboot, loaded new .203 patched init to B partition and BOOOM ! Root and eveyrhting is there on new update ! thank you Sir a LOT for your help !
[OnePlus Open] thesm4rt1:
I had the same issue going from .114 to .202. What worked for me was downloading the FULL .202 and flashing it through the Updater posted in OP. Then, go to Magisk > Install > Install after OTA. Reboot and I was good to go.

Updating from .202 to OTA .203 failed at 99% in Updater until I "uninstalled" Magisk in the app, restoring images. Update installed as expected after that and back to Magisk to Install after OTA before restart.

Latest Play Integrity Fix from AMM works great with even Google Wallet working to pay with (tested) so I'm happy.
[OnePlus Open] paine_one:
Hey, my open shows cph2551, but how I know if it's na/ni/EU/us version?
[OnePlus Open] the_rebel:
If you install Oxygen Updater, it should tell you what ROM version you have
[OnePlus Open] paine_one:
I'll check that later 👍

If my phone is a us model, can I use it in EU too? Or change from to EU rom? Or I should stand to the region my phone has?
[OnePlus Open] patrickvh:
US can have other mobile bands than EU for instance LTE.

I do not know if that is the case for OnePlus Open.

Some phones just have 'all' the bands for US and EU but are missing for i.e. China.

I myself always try to use the correct region firmware.

Cellular frequencies in the United States - Wikipedia

en.wikipedia.org

GSM frequency bands - Wikipedia

en.wikipedia.org
[OnePlus Open] zNiiC:
Does anyone have a patched .203 rom or tutorial to update to that? Or do I need to go to .202 first? I'm a bit confused by the OTA update section in the first post on if I need the full rom or just the boot img?
[OnePlus Open] Veid71:
anyone seen this before? it sounds like i should use something similiar to fastboot flashing unlock b (my current slot) when i try "fastboot flash unlock" then i get the error of "unknown partition 'unlock' error: cannot determine image filename for 'unlock'"
[OnePlus Open] FoxyDrew:
Looks like you need a newer version of fastboot. Grab the "platform-tools" zip directly from Google and work with that.
[OnePlus Open] Veid71:
just gave that a shot, but the same result, should i do fastboot flash unlock b?
[OnePlus Open] g96818:
did you forget to toggle oem unlocking in developer options?
[OnePlus Open] dknight178:
Hi all. I am on the 203 (EU) - the other steps are fine but when I get to "fastboot flashing unlock" - it says OKAY (finished in 0.030s) but when I reboot, there is no reformatting. What am I doing wrong? Thanks
[OnePlus Open] dknight178:
If it helps - aside from my post above, if I try holding the two volume keys + power button when phone is shut down, the phone only reboots.

I've tried factory resetting and entering recovery mode then wiping data to no avail - pls help me unlock my bootloader. thanks