yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] rodken:
Negative - it's all a matter of perspective and preference.
[Android Q&A, Help & Troubleshooting] user0u:
If you don't want to root, you can disable system apps via the ADB command "adb shell pm disable-user --user 0 NameOfPackage" Just be careful not to disable any critical system app.

If you do root, I really like this app manager.
[Android Q&A, Help & Troubleshooting] Davy49:
Thanks for all of the replies to my question, it sure pays to be a member of these great forums. Since I've never tried to root any of my android devices I don't know if it would be possible to root my lenovo android tablet or not.

rodken,

I've went ahead and installed the Shizuku app from the play store, I've already got both the USB debugging and the wireless usb debugging switches turned on in developer options and I've already paired my device with the shizuku application using the six digit number that was shown to me. When I pressed the start button I was taken to a different screen that showed the software was starting and after a few seconds it then returned to the previous screen, now I'm ready for the next step so I can do something with the smart launcher app. At least I'm heading in the right direction, but I'm needing to complete the task I'm wanting to do.
[Android Q&A, Help & Troubleshooting] rodken:
If you pressed the start button for Shizuku and were taken to a different screen that showed the software was starting, but it then returned to the previous screen, it means that Shizuku failed to start.

-- Make sure that you have granted Shizuku all of the required permissions. Go to Settings > Apps & notifications > Advanced > Special app access > Shizuku and make sure that all of the permissions are enabled.

-- Restart your device. This can often fix minor software glitches.

-- Reinstall Shizuku. Uninstall Shizuku from your device and then reinstall it from the Google Play Store or another trusted source.

-- Try using a different version of Shizuku. If you are using the latest version of Shizuku, try using an older version. You can find older versions of Shizuku on the APKMirror website.

In your initial post you stated:

You might be better off trying the ADB command method mentioned by @user0u from post #7.
[General Questions and Answers] MODKID:
hi i just bought O2 xda stealth

please help me, I need to be able to write and read in arabic with my O2 device! and I need to use the internet with arabic font!!!

could you help me?
[General Questions and Answers] orb3000:
Please DO NOT DOUBLE POST, doing it won´t help to be answered faster.

Wait with patience to be answered by a member

In the meantime your reply comes, why don´t you READ the Wiki: http://wiki.xda-developers.com/
[General Questions and Answers] nir36:
posting your questions again and again will result in a ban.

do not do it again.

thank you

Q&A Team
[OnePlus 7T Questions & Answers] Slayer798:
Hi All,

Yesterday I was using my Oneplus 7T in office and suddenly the phone went black screen.

I tried to plug it into power but couldn't wake up the device.

Tried to Long press the power button but nothing happened sadly.

When I try to power it on using the Fastboot it either goes to CrashDump or Simply goes black screen, I am not sure if it goes into EDL Mode or not since I can see it under device manager for Qualcomm Loader but it doesn't recognize in MSME Tool and I honestly don't know how to fix it using MSME Tool and if my data will be lost.

The phone right now goes only into Fastboot Mode and sometimes goes to recovery but sometimes it doesn't.

The bootloader is locked and I have a lot of data on my phone.

Whenever , I try to power it on. It goes to Qualcomm CrashDump Mode with no error message besides that.

I searched XDA threads with people posting similar problems but couldn't find a resolution on it. I am hesitant to give it to service center as I have little to zero faith in people from service center especially here in India.

Will I be able to recover my data using Data Recovery Software like Dr.Phone or Wondershare products (Paid) if I had to Wipe my data and cache ?

I am not sure if the Wiping my data using Recovery will be able to fix the issue.

Please helppppp me !!!!
[OnePlus 7T Questions & Answers] wfred:
Have you checked out this thread? Sounds like pretty much the same problem

Sadly it appears the issue might be a bad motherboard

https://xdaforums.com/t/data-recove...y-goes-into-qualcomm-crash-dump-mode.4505095/
[OnePlus 7T Questions & Answers] Slayer798:
I have checked this thread but I haven't really tried properly all the steps since every step will eventually wipe my data. My device sometime goes into recovery mode but not all the time.

I am right now ready to wipe my data because I'm looking to get it recovered using Data Recovery software using paid version of it.

Any suggestions ?
[OnePlus 7T Questions & Answers] wfred:
Sorry, can't help you with that. I've never used any of the data recovery services

Good luck
[Galaxy S6 Q&A, Help & Troubleshooting] S6ROMer:
Any one able to port one ui 2 or one ui 5 to the Samsung S6 (SM-G920F)? If so someone please make a port of one of them. I've already got one Ui 1.0 on it but a newer one Ui would be very nice.
[Samsung Galaxy S23] jntdroid:
Debating the 128gb S23 vs the 256gb. I definitely don't need the storage space. I also don't game much at all. But I do use my phone a lot for the usual stuff... texting, work emails, support tickets, etc. photos, videos of kids' stuff, and so on. I also use the Secure Folder a lot to split up work and personal stuff (which is the main reason I stick with Samsung).

Is there really a noticeable difference between the two in day to day usage? Or any long term differences that are significant? I only ask b/c Best Buy has some good deals on the unlocked 128gb in my region right now that don't apply to the 256gb... TIA!

Apologies if this has been asked before - I tried searching but maybe I missed it.
[Samsung Galaxy S23] :
You essentially get a doubling in read speeds from 2 GB/s to 4 GB/s. But that's completely irrelevant for daily usage. On PCs, where you're loading way more demanding applications, nobody can notice the difference of a 500 MB/s SATA SSD to a NVMe drive, unless they're doing specific stress tests. On a phone? Forget about it, apart from a placebo effect, there will be no difference - the CPU and Android's awful libraries will be bottlenecks for app loading way before storage becomes a concern.
[Samsung Galaxy S23] jntdroid:
Thank you - any battery / longevity concerns? I've read 4.0 is more power efficient... based on what you're saying, it sounds like it would be neglible at best.
[Samsung Galaxy S23] :
This is actually true, though I don't know how much it ends up mattering. But regardless of your choice, I believe you'll have a good time with the battery. I get 6 hours of SoT on my base model S23, and that's incredibly high compared to my similar usage on other smartphones. For reference, my average was 4 hours on my previous phone (Realme) and only 3 hours on my S10.
[Samsung Galaxy S23] nguyenlucky:
CPU and display consume way more battery so UFS 4.0 savings is miniscule at best :cool:
[Samsung Galaxy S23] avipars:
I went with the 256 gb for the faster UFS (even though I rarely take advantage of it), as well as the issue with running out of storage on the 128 GB model and not having micro-sd expansion.

The cost just between the two is significant though. Maybe wait till black-friday&cyber monday for sales
[Android Q&A, Help & Troubleshooting] dah_neria:
Hello, I want to upgrade the operating system of my Samsung A9 2018, I'm looking for Custom ROMs that are compatible with my phone and explanations on how to perform the upgrade. Where can I find the most up-to-date information and a list of supported ROMs for the Samsung A9 2018?" I really don't understand anything about it… But I need a phone with Android 11 and above to develop an app.
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good evening, @dah_neria Welcome to XDA! I hope you'll always get the support you require.

However, prior to your next posting please read besides the XDA Forum Rules all the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] dah_neria:
Ok but can i get any help?
[Google Pixel Fold] none24:
I've always had the general understanding that VZW doesnt allow people to unlock bootloaders for whatever strange reason they might have.

But where im lacking in understanding is what prevents folks like our talented XDA members from finding a workaround to unlocking those bootloaders?

Im more looking for the technical reason its so difficult to figure out how to get around verizon's ball and chain-- is it a security thing? or a thing where people just dont want to invest the resources into figuring it out?
[Google Pixel Fold] rodken:
You can read on Verizon's somewhat poor explanation on the locked bootloader issue.
[Google Pixel Fold] none24:
This helps my understanding some. Ive been stuck wondering why for years has no one here been able to figure out a way around it especially with all the progress android modding has made over the years. Always thought the OEM lock was a security feature baked into the OS and that eventually some genius would figure out how to get through verizon's BS.
[Google Pixel Fold] rodken:
Here is somewhat of a complete list of all the Verizon bloatware that is known to be pre-installed on Verizon devices:

Vcast Media Manager

Verizon Cloud

Samsung Visual Voicemail

VZ Navigator

My Verizon

Verizon Messages

Verizon Security

Verizon Tones

Verizon Wi-Fi Calling

Verizon Digital Secure

Verizon Family Locator

Verizon Protect

Verizon Up

The one that might stand out would be Verizon Security which is a suite of security products and services that Verizon offers to its customers. It's supposed to be designed to protect individuals from a variety of cyber threats, including malware, phishing attacks, and data breaches. The rumor of Verizon remotely accessing customer's devices might hold some truth considering that when a subscriber contacts Verizon Customer Service, they in return are able to gain access to said device remotely to assist with any issues.

Another Verizon Android app that might be pre-installed and provides remote access to consumers' devices to assist with any problems is called Verizon Remote Support. Whether the app is encoded for nefarious reasons remains to be proven.

Spoiler content hidden.
[Google Pixel Fold] none24:
I wonder if the temporary root + a debloat would work if the device was setup offline?

Wishful thinking with such an easy thought-- but man would that be something if it did.
[Google Pixel Fold] none24:
The odd thing too is I have a VZW Pixel Fold but none of those apps are pre-installed from what I see.
[Google Pixel Fold] rodken:
Verizon has been making an effort to reduce the amount of bloatware that is pre-installed on their devices in recent years. In fact, some Verizon devices, such as the Pixel line of phones, come with no bloatware at all.

However, there are still some carrier-variant devices that come or came with bloatware pre-installed - I'm looking at you Verizon OnePlus 8's. Some devices typically belong to Verizon's own brands, such as Motorola and Samsung. Verizon also pre-installs bloatware on some of its prepaid devices.
[Google Pixel Fold] none24:
i wonder then what it is about the OS that makes it so difficult for someone to root it, find a backdoor to the OEM unlock and force enable it if theres no bloatware. in my mind id assume like all other settings-- they can be modified in the buildprop or other places.

maybe its different for developer options
[Google Pixel Fold] rodken:
Usually, whenever an exploit is discovered, it's kept from the masses to prevent folks with loose-lips from sharing the work-around which ensures that the carrier doesn't scramble to patch the exploit.

Most folks would have to reach out under secrecy in order to gain a right to the exploit, e.g., there's an exploit to unlock the bootloader on the Verizon Pixel XL, but one can only reach out to the person who discovered the exploit via a messaging board or by email notwithstanding the fact that the person only communicates in Chinese.

To exploit the vulnerability, users would need to download a modified version of the Pixel XL's bootloader unlocker and flash it to their device. Once the modified bootloader unlocker was installed, users could unlock their bootloader by following the normal steps.

As soon as the exploit was discovered for the Pixel XL in 2017, it was patched by Google in a subsequent security update.

Google patched the vulnerability in the Pixel XL's bootloader unlock mechanism in a security update that was released in 2018. This patch made it impossible to use the exploit to unlock the bootloader of the Pixel XL.
[Google Pixel Fold] none24:
Totally understandable.

This convo has me doing some wild amounts of research (Wish i knew a ton more about Android development)

I came across google's write up of bootloaders/oem locks and i noticed something:

"Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets."

- TLDR: Its essentially saying if the get_unlock_ability is set to to 1 -- then we can unlock... im wondering if a person were to gain temporary root access and altered this in the build prop, would it just enable the setting but leave it grayed out. But ive never heard of anyone altering that setting from build prop so im curious what would happen.
[Google Pixel Fold] rodken:
I'm not sure what would happen if you altered the get_unlock_ability setting in the build prop to 1. It's possible that it would enable the setting but leave it grayed out, as you suggested. However, it's also possible that it would have no effect at all, or that it would cause some unexpected behavior.

I've never heard of anyone altering the get_unlock_ability setting in the build prop, so I can't say for sure what would happen. However, I would caution against doing this, as it could potentially damage your device.
[Google Pixel Fold] rodken:
It is possible to alter the build.prop file without root, but it is not as straightforward as altering it with root.

One way to alter the build.prop file without root is to use a custom recovery image. A custom recovery image is a modified version of the stock recovery image that came with your device. Custom recovery images often have features that allow you to modify the system partition, including the build.prop file.

To use a custom recovery image to alter the build.prop file, you will need to:

-- Install a custom recovery image on your device.

-- Boot your device into recovery mode.

-- Mount the system partition.

-- Navigate to the /system directory.

-- Open the build.prop file in a text editor.

-- Make the desired changes to the file.

-- Save the file.

-- Unmount the system partition.

-- Reboot your device.

Another way to alter the build.prop file without root is to use a 3rd party app. There are a very few 3rd party apps available that allow you to modify system files, including the build.prop file. However, these apps are not always reliable, and they can potentially damage your device if used incorrectly.
[Google Pixel Fold] none24:
This is true in some instances, thats why in my question I was wondering this under the idea that a person gained temporary root access as I see some have.

I've modified settings under build prop in the past and as I saved them they applied right away with no issues. just never anything from Developer Options

just reading here (https://source.android.com/docs/core/architecture/bootloader/locking_unlocking) Is giving me ideas to try but i dont wanna ruin my Pixel Fold (I also dont know how to reflash the stock rom yet) and I dont have a P6 or P7 to make the attempt on. I might try with another android phone I have on hand just to see what might happen.

Theoretically the OEM toggle should enable but "should" is always the keyword.
[Google Pixel Fold] krabman:
Mostly true for end users; there are apps which sometimes allow (some) access and guys find exploits from time to time.

You can't change the bootloader lock status from the build.prop anyway so even if you could it wouldn't matter.
[Google Pixel Fold] none24:
You could also extract it from the stock image iirc and edit it that way then flash after repackaging.

Not sure if that will verify in the flashing process but worth a shot
[Google Pixel Fold] rodken:
There are currently no custom recoveries available for the Android 14 Pixel Fold that I know of that is in the wild - maybe one is in development as of this writing considering that the Pixel Fold is a popular device from Google.
[Google Pixel Fold] none24:
Thats what my theory was getting at.

ive been able to alter other settings via BP

The option for the OEM Unlock shows for me in BP. So i was unsure whether it'd toggle it if I set the value to 1 or not.

Im not sure why it wouldnt work? but ive also never tried.
[Google Pixel Fold] krabman:
Some settings can be toggled from there; in other cases it's just reporting the status or state. In other, other cases, there are engineering/test builds which allow some changes to the build.prop that are later removed for pub releases.
[Google Pixel Fold] jhjhjhjhjhjh:
On Verizon bootloader being unlocked,

I would forget about it and never buy a Verizon branded phone.

Verizon pays for the bootloader unlock ability key to be closed source and tied down military armor tight... similar to Samsung in the USA.

I believe if an exploit was even available it would get patched anyways. Some troll would have been leaked it for clout..

The pixel xl that was too many android versions ago.

Just buy the phone straight from google and save the headaches..

Dopamin3 said:

Buying devices from carriers (specifically from AT&T or Verizon) and expecting them to have an unlockable bootloader: https://media.tenor.com/AQz3_zaiD14AAAAM/hysterical-laughter.gif

https://xdaforums.com/t/oem-unlocking-on-a-pixel-7-pro-verizon.4535767/
[Google Pixel Fold] none24:
My post was more geared towards understanding what the technical road block was to finding a way around it. Not really to point fingers at verizon and call them annoying or bad people. Of course people can go buy from other vendors.

Of course it'd get patched, as it was said before. I dont think Verizon would sit by and allow it to remain a thing -- however for newer devices that'd be gold-- even if it did get patched a significant amount of folks would be happier in the time that it isnt patched.

I myself am slowly getting into android development so I wanted to know from a technical aspect what was being blocked (if someone knew the exact thing or where to look at least). Just a spitball convo more or less. But I do agree if people dont want the headache they should go elsewhere.
[Google Pixel Fold] rodken:
+1

I remembered when there was a time when @burduli discovered a method to unlock the 2016 Pixel XL but eventually was met with a security update plugging the exploit which brings me back to another write-up regarding Verizon and Locked Bootloaders.

Interestingly enough, some reverse engineering on this file might create a rabbit hole of 'what if's'.
[Google Pixel Fold] wr3cckl3ss1:
Very nice write-up...And yes...while I went away from the Pixel. I ended up having a wonderful time with the S22 Ultra...S23 Ultra and more Samsung devices. I invite you to check out my GitHub repo. But here's a teaser for you first.

GitHub - wr3cckl3ss/system3: system3, Samsung's worst nightmare for a 3rd time!

system3, Samsung's worst nightmare for a 3rd time! - wr3cckl3ss/system3

github.com
[Google Pixel Fold] none24:
Had to sit down and open my Fold for this haha! I read every bit and this was super informative.

Digging into what wr3cckl3ss1 said it seems like somehow the transactions or calls are all baked into the apks somehow? which I guess gives VZ a reason not to put any bloat on newer pixel devices. I wonder if thats where I need to look or if finding something in the A14 image might do some good also.
[Google Pixel Fold] wr3cckl3ss1:
It is. And once u clear one...here comes the other. It's the same for Samsung devices as well. Now granted...many will jump at the site of some how making the toggle appear. But I hate to say it and I will. OEM Toggle on Samsung devices...is nothing. No matter how much you hope and try....it will not unlock the BL. It is the biggest HOPE to give someone. But it's lies.
[Google Pixel Fold] krabman:
If your time is worth anything at all I'd consider other forms of entertainment. A lot of people have put a lot of time in circumventing the lock and failed. I'm absolutely not trying to diminish your capabilities, it's not a shot at you. I'm only saying your skills, such as they are, may be better utilized elsewhere.
[Google Pixel Fold] wr3cckl3ss1:
Oh I'm not about trying to unlock the BL anymore. Ive gone a different route and. It's been good. Privilege escalation is Samsung is very very rampant. That's all I'm going to say.
[Google Pixel Fold] wr3cckl3ss1:
The one thing in will not say is...Don't give up. The amount of back doors left here and there scatted in AOSP is crazy. And you'll be surprised at how badly coded some of this is. Just by peaking at the CVE board...it's full of logic errors and confused deputies....bypasses etc....if anything...Dirty Page Tale, for those on vulnerable Pixels, would of been nice.
[Google Pixel Fold] simplepinoi177:
My apologies for my WOT (Wall Of Text) that you had to even unfold your device; those that know me are familiar with my unfortunate method. But I appreciate you reading it; especially in the hopes that it gives you some ideas, information, or point to something helpful.

As I said before, I'm not going to hold my breath -- there's about to be a Pixel 8 and more than 15 Pixel smartphones and it hasn't been done yet (most users attribute it to the fact that most devs/hackers that would have a chance at figuring it out simply don't care and just purchase a global non-variant device and leave it at that and leave the work & frustration) -- but I wish you the best of luck; for all of us Verizon customers!
[Google Pixel Fold] krabman:
Exactly. It's seldom been beat in recent times and is usually patched quickly when it is because all version phones, phone home, when they boot.

I'm not saying someone shouldn't try. I can respect having a go at something, taking a big ol swing. I am saying the idea of findibg an exploit don't doesn't jibe with the reality met by the many people who tried already across almost every Verizon phone sold. This being the case you have to ask whether it's the best use of your time. Maybe the answer is yes, you want to take that swing. Maybe not...
[Google Pixel Fold] squidbutt:
I got one from spectrum(from what im told its vzw) and sent it back because i couldnt unlock or even root it..they sent it BACK to me with the bootloader unlocked and OEM unlocking went from off to on but is still greyed out. I called to have them sim unlock it and they said its paid off..but i haveto have it on spectrums service for 60 days or more before they can unlock it. Can anyone help me understandwhy