Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section
TechBSwift said:
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section
Click to expand...
Click to collapse
No, I'm not looking for detail, by detail. I'm just asking high level, what is the benefit of an unlocked bootloader and root without custom recovery. At this point is it just a few custom apps?
Actually I'm pretty sure it makes him the coolest cat in town ?
Even if nothing else I'll root just to be able to switch to IOS emojis from those godawful Android emojis. But once recoveries and ROMs come out I'll be back to being a flashaholic.
Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
Custom kernal (elementalX) that enables amongst other things ...
Swipe to wake / sleep feature
High brightness mode .... Excellent when outdoors
Root... Gives ability to use apps that otherwise don't work, eg skvolex Call recorder
Thank you everyone. I really appreciate the explanation.
Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.
jasoraso said:
Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.
Click to expand...
Click to collapse
You could always root your phone, add the build.prop setting, and then unroot.
skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
Thanks! As I was typing my reply, I actually thought about doing that. Perhaps the next elemntal kernel update, I'll do that. I don't often tether - usually its when I'm in the car with my kids on a trip and they want to stream some netflix to their chromebooks, and I'm usually driving, and trying to get my wife to do the network switching workaround while I'm driving will be a challenge.
wolfu11 said:
I haven't been impressed with a custom rom in a long time.
Click to expand...
Click to collapse
Same here dude...same here. Towards the end of KitKat was an amazing time for ROMs especially when talking about Slim ROMs and Paranoid Android. I haven't even rooted anything since Lollipop. I just don't have a need for it anymore.
I'll give you an obvious reason to unlock your bootloader right now.
If you wait too long and the exploits are patched out (which google apparently said they will be) then when custom recovery is released for Pixel XL you probably SOL.
If you sit there for a while refusing update waiting for TWRP, why not root now and disable the update notification?
And mods are already out. Look at my notification bar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel XL using Tapatalk
skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.
Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo
oneandroidnut said:
Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo
Click to expand...
Click to collapse
Thanks for your feedback! I am now unlocked and rooted!
marcjc said:
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.
Click to expand...
Click to collapse
Just to update anyone who may be interested. I rooted, made my changes, then unrooted, rebooted a whole bunch of times and my changes survived unrooting and rebooting.
Kc0r8y said:
Thanks for your feedback! I am now unlocked and rooted!
Click to expand...
Click to collapse
Don't forget custom kernels to increase the speed of the 821 CPU. Out of the box, the CPU is clocked down to the 820 level. With a little over clocking we can experience the full potential of the 821.
Thread cleaned.
Folks, keep the thread on topic and post in accordance with the forum rules you agreed to when you joined XDA.
Cheers,
Magnum_Enforcer
FSM
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP AND SUPPORT
DESCRIPTION OF THIS THREAD
Back in 2011 I sat down and wondered what I could do to help a community that helped me so much and continues to help people everyday from bricked phones to shiny new things on their respective devices and this is what I created, with the guidance of certain moderators of course.
[*]I wanted to create a thread in which any question can be asked, be it porting related or anything and we all help each other out, this has been going for a few years now and has been a huge success so I have updated the quick start guide and I will be a more ever-present force in the thread to answer any help and such that you may need, because if we all help each other this place can be a more user-friendly and more interactive place to visit.
Please also note you may PM me if you wish to ask anything in private, or if you feel the need to just say hello.
Please also note that this thread was indeed a sticky at one time however I had other commitments in 2011 (College and such) and it was removed by November 2011.
[*]For donations, I would kindly ask you to donate to the Macmillan cancer care and support, however if you wish to donate to me I will donate it to the charity anyway, myself and Macmillan thank you for your support, no one should have to face cancer alone.
HERE IS A GUIDE TO GET STARTED
GENERAL KNOWLEDGE v1.0
Rooting - Gives you complete root system access allowing things to be done that usually would be denied.
[*]S-OFF - (HTC Devices) Basically means you can flash ROM's to the SYSTEM partitions and such.
[*]Write Protection - This can mean a variety of things, from a locked boot-loader to SD card access, consult your device forum for information.
[*]Bricked(Soft) - Soft brick means that it can be recovered using appropriate methods found in your device forum.
[*]Bricked(Hard) - Very hard to fix usually means it's beyond repair but can be fixed in certain circumstances and at a local repair dealer for your phone.
[*]Kernels - The backbone of the phone, they are responsible for making everything run, the CPU, Schedulers and such are configurable using the kernel.
[*]CPU0 - Different for each phone however CPU0 is usually the 1st logical processor followed by 1,2,3 for quad core phones.
[*]Dual Core/Quad Core - Dual core means you get CPU0 and CPU1, Quad core means CPU0, CPU1, CPU2 and CPU3 are all available.
[*]Chip-set - This is your main-board, it means what your phone is built upon.
[*]Lib files - Found in /system/lib usually however this can be different, they control the software to firmware gaps on your phone, so they enable sound, camera, video; the major things live here, don't touch it unless you know what you're doing.
[*]Battery Stats - These control how long your battery lasts, they are reset when you delete the file from the system however it's strongly recommended you don't delete them.
[*]AOSP - Basically means the original Google Android software as a bare-bone OS.
[*]Partitions - These are different for each phone and should be treated with great care for example flashing a puppy to the radio partition would be a foolish action.
[*]Launchers - They change the UI of the phone, there are many out there so try them all until you find one that suits you just right.
[*]Logcat - This is only useful if you have an error with your phone, it's a simple adb logcat command however I prefer to use QTADB which is a nice GUI style logct application.
[*]ROM's - You flash these on phones that are able to flash Custom software, you can get many varieties however the main ones are 'Stock' the original phone OS, 'CM' which is AOSP, 'MIUI' An AOSP/AOKP style crossover mimics the iOS UI.
[*]Recovery - When flashed; custom recovery allows you to make changes to the different partitions inside the phone for example flashing a custom ROM.
[*]Flashing - Basically writing information to a partition or making a fool of yourself in public (the latter is not recommended due to laws)
[*]Over-clocking - This means pushing your hardware beyond its manufacturers original settings, this can be useful to create a faster phone but treat it with care as you can damage phone hardware.
[*]Under-clocking - This means lowering the stress on the system by making the hardware run slower than it's intended to do, great for saving battery.
[*]Under-volting - This means under-volting your CPU or GPU, this can cause stability issues but on the plus side can save battery, it's all about striking a balance.
[*]Benchmarking - This means to test your phone to its max and find out how it stacks up against other devices.
[*]IO Schedulers- They control how the system reacts in different situations, there are different types of Schedulers available so use each until you find one suitable for you (protip: Use fiops or noop)
[*]CPU Governors - They control the CPU frequencies and such for example "Performance governor" will give you constant speed, whereas "Conservative governor" will give you low speed.
[*]GPU Governors - They do the same as their CPU counterparts except they control the graphical section of the hardware.
[*]Radios - They control the baseband aspects of a phone (your network and such) they have different names for each device, they are very dangerous to mess around with.
Note:
Updated as of 12/06/13
So what are you waiting for? Ask questions!
comnd promt is responding
I hav managed the ss number and when put in the beta f oth d par revolutionary it come from the cmd promt to root the htc evo any ideas
alsworld said:
I hav managed the ss number and when put in the beta f oth d par revolutionary it come from the cmd promt to root the htc evo any ideas
Click to expand...
Click to collapse
i didn't really understand all that, but from what i got, you want to root it? or s-off it?
try the revoluitonary.io site
i used revolutionary cwm, loaded rmk's root zip, and wound up in a permanent bootscreen. so i flashed rmk gingersense r1 rom, and now i dont have cwm anymore. it just boots normal. wtfdid? do i need to reinstall cwm every time i flash the rom? any tips would be appreciated. total root newb if you couldn't tell.
inspire rooting
samuel2706 said:
HELP AND SUPPORT
From now on, i shall be conducting a help session for ANYONE with any kind of problem relating to android, be it a brick or a problem with fastboot or you can't root your phone, hell we have all been there, so maybe i could help you.
it shall be
If you have any other problems or need help or even want to learn about android and become a developer then just post in the thread, i'll get back to you. ALL OF YOU.
so don't worry if i don't get back within the first hour or so, i'll help you don't worry.
I'm not doing this for my own benefit, i'm doing it for yours, i'm patient and i understand how daunting places like this must be, i felt the same way when i first joined, i was scared about rooting my phone and still get a bit scared when it doesn't boot straight away but once you know the basics things just flow to you
i want to help you, help yourselves. so drop by with any questions about android, i'm going to be there from the moment this is posted
Click to expand...
Click to collapse
i have an inspire 4g with gingerbread i want to root it and put coredroid in it i tried bubbys method and also the hack it kit and both did not root my device i live in india and my inspire is carrier unlocked please suggest me a simple method to root my phone
vamsi4012 said:
i have an inspire 4g with gingerbread i want to root it and put coredroid in it i tried bubbys method and also the hack it kit and both did not root my device i live in india and my inspire is carrier unlocked please suggest me a simple method to root my phone
Click to expand...
Click to collapse
This should work
i know you said you had tried it but try again, DO everything as it says, even if it's as simple as case sensitive names..
Do you know any methods of rooting 2.3.4? The device I'm looking to root is a Kyocera Echo running GB 2.3.4. Gingerbreak, SuperOneClick, and z4root (lol), have all failed in rooting the device.
As far as I know, there's no locked bootloaders or anything that should be in the way except for no recovery. The Echo has fastboot if there's actually a method of rooting through there.
Thanks.
just tried it not working after some time it says device connected do u think coredroid is worth all the trouble?
Jamin13 said:
Do you know any methods of rooting 2.3.4? The device I'm looking to root is a Kyocera Echo running GB 2.3.4. Gingerbreak, SuperOneClick, and z4root (lol), have all failed in rooting the device.
As far as I know, there's no locked bootloaders or anything that should be in the way except for no recovery. The Echo has fastboot if there's actually a method of rooting through there.
Thanks.
Click to expand...
Click to collapse
Z4ROOT is apparently said to work, there isn't a lot on the forums for this device but i will keep my eyes peeled and PM you when i find something out
vamsi4012 said:
just tried it not working after some time it says device connected do u think coredroid is worth all the trouble?
Click to expand...
Click to collapse
do you have the drivers installed? download the SDK and install the drivers pal
samuel2706 said:
Z4ROOT is apparently said to work, there isn't a lot on the forums for this device but i will keep my eyes peeled and PM you when i find something out
Click to expand...
Click to collapse
That was probably for Froyo but maybe it does. I'm thinking if someone could get a custom recovery working, we could root it by just flashing Superuser.
Sent from my M9300 using XDA Premium App
i did all that i have teh sdk installed
vamsi4012 said:
i did all that i have teh sdk installed
Click to expand...
Click to collapse
Hmmm so you have tried all sorts of things? and z4root doesn't work?
mcsplatt said:
i used revolutionary cwm, loaded rmk's root zip, and wound up in a permanent bootscreen. so i flashed rmk gingersense r1 rom, and now i dont have cwm anymore. it just boots normal. wtfdid? do i need to reinstall cwm every time i flash the rom? any tips would be appreciated. total root newb if you couldn't tell.
Click to expand...
Click to collapse
Nah man you shouldn't need to install it every single time bro, you got any logcats or things you could send me?
or a recovery log? that would be awesome, if you don't know how to get these i'll teach you just pop over to the IRC if not then i'll tell you on here, it's fine
How can I sign a ROM or a bootloader for Samsung Recovery 3E?
Where was this thread 4 months ago when I was not getting any sleep. Thanks.
I'd like to try and become a developer, mainly because my Samsung Droid Charge hasn't received any AOSP love yet and I want to try and help the dev(s) that are working on it, also I would like to make my own rom. But I have no idea where to start, and I have questions like do I need Linux, do I need to/where do I learn terminal commands, how does smali/baksmali work, how to compile/decompile, how does github work, what is a toolchain, do I need to know how to code, do I need to know any languages, what is Eclipse...stuff like that. I'm a complete noob at this kind of stuff and I feel it's a bit far out of my reach but I'm willing to give it a shot if I can get a decent start. I realize it won't just happen overnight, I have the patience to keep learning and doing research to figure it out, but I would like help getting started.
@samuel2706: I have a Droid x2 and as you it has a locked bootloader. I also have a Galaxy Tab 7" which does NOT have a locked bootloader. I've been in Android for a very very long time, I am an experience flasher and rooter, but I want to get into the development side.
Could you direct me to what I need to read up on and learn about and do for me to become a developer? I would like to develop from my devices, I know that a locked bootloader steeply limits what I can do, that's why I am more interested in developing for my tablet. I mean a lot of things interest me. I look at my logcat on my devices, I see errors, and I just want to go in and fix them, I want to make my device smooth as butter, lol.
I'm also interested in finding an exploit of some sort for my Droid x2 so that I can crack it. There has gotta be a way to crack it open.
Thanks!!!
Stock rooted Gingerbread for HTC Inspire
Hey Samuel. Thanks for doing this. I got my Inspire about a weeks ago, rooted it the day I got it, and have been lurking these forums since. Saw this opportunity to ask a n00b question, and registered. So, I'm looking for a stock, rooted Gingerbread ROM. It was suggested I don't return my phone to stock, update, and then re-root. Not sure why, but I'll listen. Thanks in advance, and thanks for doing this.
-MM
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
davide136 said:
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
Click to expand...
Click to collapse
Bit early considering we aren't even positive what the final product's hardware will entirely be Can't wait though
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
davide136 said:
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
Click to expand...
Click to collapse
Exactly that's what I'm afraid of, too. If I decide to buy a new phone, I'd like to compile ROMs for it by myself, too, but therefore the vendor, device and kernel tree need to be published by HTC. I've just been looking around how custom development for the HTC One M9 looks like. Although I couldn't find many ROMs, there are official Cyanogenmod versions and open device and kernel trees. Thus I could compile many ROMs for the One M9. This gives me hope regarding the HTC 10. The Galaxy S6 instead didn't have no huge moding posibilities. There's only an unofficial, unstable device and kernel tree alongside a bugy CM-version. Just like the S6 the S7 probably won't get huge development support as well. This is what gives me hope regarding the HTC 10.
The only question I'm currently asking myself is if I should buy the HTC 10 or wait for the Oneplus 3 which will be published later in Q2 2016. Compared to the OP2 and OP1 it'll be a bit more expensive but it'll also be better equiped. Furthermore the price will probably be much lower than the price of the HTC 10. What are your expectations and what have you been able to definitely find out so far?
I'm still tryng to figure out what to do...lg has dropped support for rooted or bootloader unlocked device in italy, and the g5 seems to be a bit strange te me, i mean, it's not as premium as g4..regarding oneplus devices, for the 1 and 2 i read about bad screens and something else wich i don't remember, never saw one...i'd prefer staying on a strong brand...samsung obviously is exhiliated from any decision...sony maybe but no xD never liked the screens in the past...
My old nexus 5 make me wish about a decent nexus around 5" screen, I'd really love it, especially powered from a snapdragon 820 cpu..
Mi5 is lovable, but, you know...it's xiaomi...china brand, china support, 30 days for travelling a device if something happens, and that is for 2 times...its frightening xD
Htc 10 seems to be the best choice, ut will surely be premium, even if it does not have a good camera i don't care, just bought an eos 700d xD i just hope there will be a lot of modding, that is why i asked here
Htcdev.com is still working good for all the other htc, it must have decent modding, i think I'll go for it. At least, that's what I'm thinking now...but who knows
Inviato dal mio SM-G920F utilizzando Tapatalk
Yeah, Xiaomi is a brand I've been looking at over the last two years. I recommended Xiaomi phones to friends who wanted to have good and cheap devices. They are lucky all together but the only phone by Xiaomi I'd buy is the Mi Note Pro as a phone should have 5,7 inch in my opinion. I'd also like to have an AMOLED-Display in my next device so I hope HTC will release a bigger version of the 10 as well. The LG G5 is not really what I am looking for since it's a bit strange to have several components you can choose from. I think I'll buy a OP3 when it's published as it'll probably be more developer friendly but maybe the 10 by HTC will convince me, too. I'm really excited about the upcoming devices especially because my Nexus 4 from 2012 becomes slower and slower. Very anoying. Maybe a new Nexus will be released at the Google IO this year. This would be awesome. Anyway, I hope the potent upcoming phones will come sooner than later as I don't know how long my N4 will survive.
Very informed you guys are. I like this thread cause' I think a lot like you.
Sent from my Nexus 5 using XDA-Developers mobile app
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Rohaq said:
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Click to expand...
Click to collapse
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
Well, looks like it paid to wait then, come on, release day!
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
davide136 said:
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
Click to expand...
Click to collapse
No, the things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
0verdaflow said:
When is this gonna be released ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
JEANRIVERA said:
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
Click to expand...
Click to collapse
Maybe there's another HTC phone to come in early may, hopefully a phablet but let's see...
Anyone know how we will get root on the unlocked version?
km8j said:
Anyone know how we will get root on the unlocked version?
Click to expand...
Click to collapse
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Behold_this said:
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Click to expand...
Click to collapse
Is this a big process? Is everything already available? Does any part of the rooting process wipe the device? If so, may make more sense to just do it right out of the box to avoid losing info
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Sent from my HTC One M9 using XDA Labs
HTCNerdYoda said:
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Click to expand...
Click to collapse
But does the bootloader unlock wrote y the phone?
km8j said:
But does the bootloader unlock wrote y the phone?
Click to expand...
Click to collapse
If you meant wipe the phone, then yes, it does.
I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pinokaille said:
I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
View attachment 5413839
Click to expand...
Click to collapse
It seems it's a common behavior between newest samsung devices. Look at this video:
Good phone overall, but let down by manufacturer's restrictions. Like the Realme GT.
Did you get any message like "camera will not function" while in bootloader unlock menu?I bought this phone but if something like this is present then I will cancel,better to buy some other thing.
Arobase40 said:
There is NO problem with the camera when the Galaxy A52S 5G is unlocked !!!
Mine is working pretty fine so I guess the issue is somewhere else !
Click to expand...
Click to collapse
SM-A528B model ?
Arobase40 said:
Yes !
Click to expand...
Click to collapse
Did you just unlock bootloader, or manage to root the phone as well?
i had the same issue after unlocking the BL, had to relock it again to get the camera to work.
deleted
Arobase40 said:
There is NO problem with the camera when the Galaxy A52S 5G is unlocked !!!
Mine is working pretty fine so I guess the issue is somewhere else !
Click to expand...
Click to collapse
Would you mind sending a screenshot as a verification that your bootloader is unlocked with working camera? Just split the screen with camera on the one half and developer options with OEM unlock option open on the other half
Pinokaille said:
I unlocked the bootloader of my galaxy a52s 5g (SM-528B)
But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
View attachment 5413839
Click to expand...
Click to collapse
This is PRECISELY what i see on my fold 3
if the camera returns AFTER BOOTLOADER RELOCK............
.................It is therefore confirmed that the A52 5G has the same booby trap as the Z fold 3
The Flip 3 does not have this however
I have the A52 5G (SM-A526B) and when I rooted my phone I had no problems with the camera. The only way to verify if OP's problem is intentional by Samsung or something went wrong in his unlocking process is if he (or someone else with the A52s 5G) posts a photo of the bootloader unlock screen. If it is intentional it will clearly say the camera will not function after unlocking
I have the same issue with my SM-A528B. I have unlocked the bootloader (The warning when unlocking the bootloader says nothing about the camera. It is just the regular warning about un-secure software etc.)
I used the latest Magisk to patch the boot image and flashed using Odin. Unfortunately it got stuck in a boot loop and I decided to flash the original boot image back. Now when starting the Samsung camera app, I get the "Camera Failed" error and the app closes. However, when testing other camera apps, some are able to use the front/selfie camera, but the rear camera always gives an error.
Update:
Flashing the BL, AP, CP and CSC did not help.
However locking the bootloader again made the camera work just fine. Thank you samsung for that little feature.
Arobase40 said:
Well no I can't do that as I re-locked my bootloader and that drive me to think there is something wrong with A52S...
Whenever my phone is unlocked (or supposed to be) or locked, the OEM option is always ON and recently I received an OTA update witch means my phone has never really been unlocked even when I got the message my system has been modified !!! ^^
That also explain why I couldn't root my phone with Magisk and the modified AP file.
BTW, if you have a rooted A52S 5G phone could you send me a build.prop file so I'll try to build a TWRP version for this model of phone, or if anyone else could send me this file ?
Click to expand...
Click to collapse
Thats sad to hear.
To get build.prop you can simply download the whole firmware from a site like samfw.com or with a tool like SamFirm and then extract it.
i can confirm that unlocking BL on SM-A528B makes camera unusable. black screen same as OP stated.
vladinc said:
i can confirm that unlocking BL on SM-A528B makes camera unusable. black screen same as OP stated.
Click to expand...
Click to collapse
Samsung fixed this camera issue on the Galaxy Z Fold 3, we hope it will do the same with the SM-A528B.
F
Arobase40 said:
SM-A528B bootloader is still not unlocked but there is a workaround when rooting it with Magiskv24.3.
You may have to repatch the AP file and flash it again, and then enable Zygist option in Magisk 24.3, install LSPosed-zygist module and SafetyNet Fix 2.2.1. reboot.
On, first try the camera won't work, so you have to force close the camera app in Settings, Applications.
Camera should work on next try.
You have to redo this same operation after every reboot... ^^
Click to expand...
Click to collapse
I did this step by step and everything was fine with root and camera working 100%.
Arobase40 said:
SM-A528B bootloader is still not unlocked but there is a workaround when rooting it with Magiskv24.3.
You may have to repatch the AP file and flash it again, and then enable Zygist option in Magisk 24.3, install LSPosed-zygist module and SafetyNet Fix 2.2.1. reboot.
On, first try the camera won't work, so you have to force close the camera app in Settings, Applications.
Camera should work on next try.
You have to redo this same operation after every reboot... ^^
Click to expand...
Click to collapse
Is there any fix for that? I unlocked the bootloader of my Galaxy A52s (SM-A528B/DS) and I get the damn error.
I just don't want to continue and root the phone unless I'm 100% sure that the camera will work...
Dammit Samsung!
Arobase40 said:
This is explained in post #22 just above !!! ^^
Click to expand...
Click to collapse
But that involves triggering knox. I want to avoid triggering knox (be it with root or flashing a patched AP) unless I'm 100% sure that camera will work.
Considering that just with the bootloader unlocked but nothing flashed the camera doesn't work.... I can't be 100% sure.
Thanks for trying to help, tho.
Arobase40 said:
You can't root this phone without triggering Knox !!!
Once again read post #22 to who I answered and read back the answer at post #23 about the result with the camera...
Click to expand...
Click to collapse
Once again: But that involves triggering knox. I want to avoid triggering knox
It's good that you spend your time trying to help people make the most out of their phones, but you try so hard to convince people on using your how-to's that you often ignore what compromises they are willing to make / not make.
Arobase40 said:
Listen, you asked to know how to root your phone with you camera working and I gave you the answer which is already an "exploit". If there was a way to avoid triggering Knox you can imagine I would use myself it asap as any other users too but there is none !!!
Want to root your phone ? Then you have to make this compromise, if not, then don"t root your phone Period
Click to expand...
Click to collapse
Read again, but this time read right please:
A52S 5G (SM-A528B) Unlock bootloader camera failed
I unlocked the bootloader of my galaxy a52s 5g (SM-528B) But the camera doesn't work on any application anymore it's a complete block and when I patch the boot.img with magisk I have a boot loop someone has the same problem or knows how to fix this?
forum.xda-developers.com
Nowhere in this thread I asked how to root my phone....
Get out and do something else besides trying to get everyone to follow your xda tutorials. Most importantly read correctly before going off on someone for not following your suggestions.
You might think that I'm nobody to tell you something like that, but trust me... I'm doing you a favour, it will help you to not be perceived as a maniac easy to trigger whenever someone rejects his suggestions.
Is is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED background? If so, what are the steps for installing OTAs, and what are the chances of bricking your device. If you have rooted, do you use quick switch and do you think it is worth it? ThanksIs is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED backround? If so,
It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me. All stuff Google could implement on its own without issues, but Google being Google...
With Zygisk/hide & the fix for SafetyNet, all my apps/banking stuff/GPay is working fine, so there is no "downside" to rootinng, except updating firmware.
By updating firmware you mean OTAs right? What are the steps for installing them?
Divine Bicycle said:
By updating firmware you mean OTAs right? What are the steps for installing them?
Click to expand...
Click to collapse
Hi. Click the How To Guide filter above the Pixel 6 Pro section and you'll find all the directions you need.
Keep in mind that although disabling Verity and Verification are no longer required for root, some custom kernels for stock still require that. If you're not going to ever use a custom kernel, then it's not a concern.
At least one custom kernel developer wasn't sure if it was still necessary so still advises it for use with their custom kernel.
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.
Morgrain said:
It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me.
Click to expand...
Click to collapse
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.
RetroTech07 said:
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.
Click to expand...
Click to collapse
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.
roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.
Click to expand...
Click to collapse
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?
roirraW edor ehT said:
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.
Click to expand...
Click to collapse
I use it alongside JamesDSP (I really prefer the bass of JamesDSP over V4A) and have since Ice Cream Sandwich. I'm not sure if "better" is the right word, but it does allow you to adjust the sound more the way you want it.
Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
Hi, check over here:
Samsung Galaxy Note 10+
The Samsung Galaxy Note 10+ is a 6.8" phone with a 1440x3040p resolution display. The Exynos 9825/Snapdragon 855 chipset is paired with 12GB of RAM and 256/512GB of storage. The main camera is 12+12+16MP and the selfie camera is 10MP. The battery has a 4300mAh capacity.
forum.xda-developers.com
Cheers
ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
This really isn't the place to ask about anything not related to the Pixel 6 Pro. As for as the P6P and the January update, it's been previously announced that it would come for the P6 & P6P in late January.
December 2021 Update Paused
V0latyle said:
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?
Click to expand...
Click to collapse
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.
roirraW edor ehT said:
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
Click to expand...
Click to collapse
Embrace the madness!!!
Lughnasadh said:
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.
Click to expand...
Click to collapse
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.
roirraW edor ehT said:
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.
Click to expand...
Click to collapse
Yeah, that makes sense because you only restored the stock boot image, but not the stock vbmeta so verity and verification remained disabled, allowing you to flash whatever you heart desires.
I'll test it right now. Stock P5, January update, Magisk patched boot image. Let's see what happens...
Reflashed vbmeta and disabled verity/verification. Boot image is patched. Result: Rescue Party.
Reflashed unpatched boot image. Result: Rescue Party
Reflashed vbmeta without options, reflashed patched boot image. Result: Successful boot.
Alright, I was thinking about not rooting at first but now I'm getting that itch. Welp.....time to try and root this joint
roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
Click to expand...
Click to collapse
I've been usng Dec build without veritfy/verification disabled (with Canary 23016 & Kiri 1.40) since mid December & have no issues to report. Guinea pig status: achieved?
Mentioned above is my question. Thank you
joining in on this question cause my new phone is on the way. are there any working custom recoverys or custom roms available yet? lineage os and twrp seems to have nothing yet.
i've seen a bootloader unlock on yt but found nothing to push onto the device afterwards
Depends as far as I've seen on mine the oem unlock is not it the settings under developer options so no bootloader unlocking which means no root even though it's exynos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The option is in developer settings
Why put something different on for the sake of only having sth different? Cant see where any custom rom could be any better than Samsungs current ONE UI, which is great.
download magisk apk on your a54 and again download your a54's firmware from samfw.com, unpack it and get your AP file, open magisk and click install and select from file and select AP file, make sure your bootloader is unlocked, move your patched AP file to your WINDOWS PC, install samsung usb drivers and odin https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/, open odin and connect your a54 to your pc with a usb cable, now put the patched AP into the AP slot of course and hit start, after it flashes you will have a rooted a54.
dj_mol3y_x8 said:
View attachment 5887405
The option is in developer settings
Click to expand...
Click to collapse
Werid not in mine
jolly_roger_hook said:
Werid not in mine
Click to expand...
Click to collapse
what model do you got? for example i got a a53 and its model is A536B which means it OEM unlockable
TringQuack said:
what model do you got? for example i got a a53 and its model is A536B which means it OEM unlockable
Click to expand...
Click to collapse
A546B/DS
terry_mccann said:
Why put something different on for the sake of only having sth different? Cant see where any custom rom could be any better than Samsungs current ONE UI, which is great.
Click to expand...
Click to collapse
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want
dj_mol3y_x8 said:
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want
Click to expand...
Click to collapse
to put it simple: updates
for example on my current lineageOS i get a systemupdate every half month, they are very up to date. or even have higher android-support past the manufacturers "expiration date". and i still dont see any big company names supporting android updates past the shelflife, except nokia and their longtime support promise, which gets also dropped after 4 years, while the hardware could still support newer androids. i would have been stuck on android 10 with my current device (oneplus5) but here i am with a smooth android 13 on lineageOS. thats the main reason i want a custom rom and dont stay on stock.
apps will have higher android requirements and my phone will just get outdated by the playstore - wow.
dj_mol3y_x8 said:
Fully agree with you.
oneUI is not anything like touchwiz from back in the day.
oneUI is far more optimized and getting less bloated and much more freedom.
So for me it's Samsung's stock OS or a buggy rom. No real choice
Let's do a run down over the years
Early android years CM/linage was where it was at
Reasons...
More customizable.
Less bloat
Theme's
Add or remove apps/features
Early Samsung
Touchwiz bloat apps none removable
Horrible UI
Slow and laggy
Now if we move to modern Samsung things are much different
90% of pre installed apps are removable
Theme's as standard. And can use apps like theme park and hex installer to side load themes created. oneUI only core (no root needed). Not possible oneUI CORE
Regular updates
Fast and streamline.
Samsung have listened to its users and are definitely heading in the correct direction.
So that said for me I don't get the need for a custom OS.
I will just use Sammy OS with a theme I make for the looks I want
Click to expand...
Click to collapse
Not really that I want a custom rom there are a good deal of things root can be used for that doesn't involve a custom rom such as full access to all storage areas on the phone, custom recovery (TWRP). Samsung removed access to alot of minor some major things that were what made android great to stay current with the market root allows you to get some back I do agree with UI being way better then touchwiz I still want root for other things
Samsung U.S. variants don't have OEM Unlock option anymore. I have an S23 Ultra & an A54 - both are US unlocked variants and neither of them have it. I mean I bought them unlocked, so why no OEM unlock? I don't personally care as custom ROM's never really act right. It's only good for old phones IMO that aren't updated any longer and to put Lineage OS on it or something.
mewcatchew said:
Samsung U.S. variants don't have OEM Unlock option anymore. I have an S23 Ultra & an A54 - both are US unlocked variants and neither of them have it. I mean I bought them unlocked, so why no OEM unlock? I don't personally care as custom ROM's never really act right. It's only good for old phones IMO that aren't updated any longer and to put Lineage OS on it or something.
Click to expand...
Click to collapse
Yea that's the same issue I have even though it's unlocked and exynos its US so they completly removed the oem option from dev settings
dj_mol3y_x8 said:
View attachment 5887405
The option is in developer settings
Click to expand...
Click to collapse
what model do you have?
i'm using a546u1 and it doesn't show oem unlocking in developer settings
Just putting this out there.
Reason I got into custom ROMs in the first place is because they're usually light-weight so they run faster and they don't come with a bunch of invasive and uninstallable bloat-ware. With my A546U I can't even uninstall MS OneDrive and it drives me nuts. Hoping someone figures out how to unlock the bootloader on this thing so I can flash the PE rom someone mentioned in another thread. I also saw there's a version of TWRP that's in the works. Hopefully someone smarter than myself can figure this out soon. Still probably gonna purchase a different phone because removing all the excessive google/Samsung apps is a necessity for me.
This is my first Samsung device and I'm not too thrilled with it tbh
h0miemaru said:
Just putting this out there.
Reason I got into custom ROMs in the first place is because they're usually light-weight so they run faster and they don't come with a bunch of invasive and uninstallable bloat-ware. With my A546U I can't even uninstall MS OneDrive and it drives me nuts. Hoping someone figures out how to unlock the bootloader on this thing so I can flash the PE rom someone mentioned in another thread. I also saw there's a version of TWRP that's in the works. Hopefully someone smarter than myself can figure this out soon. Still probably gonna purchase a different phone because removing all the excessive google/Samsung apps is a necessity for me.
This is my first Samsung device and I'm not too thrilled with it tbh
Click to expand...
Click to collapse
You can use ADBAppControl made by fellow XDA member to remove any un-uninstallable app through ADB.
There's no rescritctions with this program so be careful. You can disable/uninstall critical system apps and it won't stop you, (systemUI, OneUI Home, etc).
Can be used to completely de-google the phone, which is what i use it for.
FoxyDrew said:
You can use ADBAppControl made by fellow XDA member to remove any un-uninstallable app through ADB.
There's no rescritctions with this program so be careful. You can disable/uninstall critical system apps and it won't stop you, (systemUI, OneUI Home, etc).
Can be used to completely de-google the phone, which is what i use it for.
Click to expand...
Click to collapse
Awesome thank you so much!
Definitely going to look into this.
And just to clarify this can be done to the stock firmware A546U (US version; no OEM unlock toggle in dev settings)?