bruh, I regret updating my samsung phone, Android 13 on the A53 is not good, the battery is wasteful and many applications don't use, which is a bad user experience. I've tried debloating and it's better but it's still good on Android 12 it turns out, yep I wanted to downgrade it was discussed before some said it didn't work. before I had a Samsung A10, I also had a custom ROM. many say you can't if the binaries are different, but after I try, I can flash it with other binaries. I want to try but with consideration of success. in download mode it says custom binary which I think can use any binary.
Related
It seems like all custom roms include root. I'm trying to get around SafetyNet so I'd like to find one that doesn't. I currently have CyanogenMod 13 with virtual repartition version of TWRP. Are there ROMs like this? I'm currently reading through the development forum but most don't say one way or the other, probably because they include root.
If I can't find one, are there some that can be unrooted? I don't think CyanogenMod falls into this category. I can try to hide root if nothing else and have done a lot of reading on that using SUhide, Xposed, Root Switch but I think it would be a lot easier if there was a stock-ish kit kat or higher ROM I could use and unroot.
Thanks!
Depending on what you need to pass SafetyNet for, I'd say you are probably out of luck on the S2.
The last official ROM (from Samsung) for the Skyrocket was Jelly Bean (4.1.2), which is too old. Unfortunately, I don't know of any third-party ROM beyond that which doesn't come with root support pre-installed, and given the S2's curious bootloader configuration, it might not pass SafetyNet even if you could find one. Then, there is the minor fact that the S2 is old enough that it might be not be approved by Google even if you could get past all the other issues.
If you really need this, it might be time to consider an upgrade. However, if you do manage to get it to work, that would be a pretty cool find for this old phone.
I'm not really a very advanced user, but always had rooted devices and two that I flashed Custom Roms. This is my first Samsung, finding Touchwiz to be very different from what I used before.
I bought the S7 (930F) and had the news that it was going to be updated to Oreo, so I decided waiting for the update before tinkering with it.. But the update never came. Finally this month Samsung released the update for my region, so I would like to know which would be the best way for me to start finally using my phone that I bought for over 2 months!
My phone is still with Nougat, is it better for me to get the OTA or to flash the Firmware I downloaded from Sammobile? Any of these methods better than the other in preventing errors? I always found in PCs that a fresh clean install was better than an update, but with mobiles I don't have the experience to say.
My main objective is to experiment before doing a debloat as I'm still not sure what might be useful for me on Samsung's bloat (you are welcome to point me what is useful and what is not).
I did see that some of the Customs ROMS have different camera apps and some people were complaining about this, I particularly liked the S7 camera app and the Pro option, that's what holds me back in flashing a Custom ROM atm.
I would like to Root and I find Unlocked Bootloader to be useful to have Xposed Framework and other things that I can do having it.
As I'm a relative newbie, what would you guys recommend me doing? Please help
tl;dr: I want to have Oreo, be able to debloat, want to root and unlock bootloader, not sure about Custom Rom.
Lineage if you want basic and simple (sort of like stock Android). Resurrection Remix if you're a customisation nut (not a slam... I use RR).
If you wonna full samsung u need flash base firmawre custom roms only 8.0 android
If you dnt need samsung integration (pulsometr doesnt work) you can flash 8.1 roms try cosmic os or Lineage 15
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.
So, i have an LG K11 Plus (LM-X410BCW), released in 2018, the hardware of this phone is pretty good but, for some reason, while its CPU does supports 64-Bits, LGE installed an 32-Bits kernel on it (thank you for mistakes like that you always do, LGE.... ugh)
I searched for another root and custom kernel for this phone, and i could not find any. No rooting, no custom bootloader, and no custom kernel. Simply, nothing.
And for the most unfortunate, this phone is now completely abandoned by the manufacturer. Their official ROM and kernel are so bad, so glitched, so awful. The phone does not use the maximum power of its hardware, it keeps rebooting, it's stuck in Android 7.0 and even its camera app is glitched (my BACK flash doesn't work on the back camera, the app recognizes it as a "frontal" flash)
I know for rooting and installing custom kernel, i need another bootloader first
So i plan to make an unofficial bootloader for this model.
But i don't know where to begin, i know nothing about Android deep-modding and developing mobile custom kernels and bootloaders, i've no clues how to do that
I only know the basics of Android app developing, Android shell scripting and i'm more advanced in J2ME applications (completely useless for today's Android standards)
So, ¿where do i begin to do that?
My initial plans is making a unofficial TWRP bootloader for this model, but i don't know how i'll do that
I'd really help you if i knew how to, i also have this phone. I got it for a realtively high price and must say that it's absolutely unworthy of it's existance in our planet and modern society. The absolute maximum of modifications it allowed me to do was to remove bloatware packages using ADB, so i removed almost everything Google/Android related and now i'm working on a list of what you can/can't remove.
I removed the included launchers to only use Evie launcher, installed XDA's Navigation Gestures app (tho it made my phone lag a bit, as any overlay/draw-over-screen app will do), replaced Play Store by F-Droid, and etc... The phone is still bad, sub-entry level hardware even for it's time, has a Vulkan-capable GPU without Vulkan drivers included in the OS, and a 64-bit CPU running a 32-bit Kernel/OS, like you mentioned. But after that, the experience became a little bit smoother, at least!
I don't know nothing about this, but maybe you can get this phone's stock ROM in KDZ format, and start doing brute-force modifications to it, to flash it with LGUp, or LGFlashTool as if it was a stock ROM, but your modified version, because i don't think this phone checks the integrity of the ROM being flashed, or at least not in a way that can't be easily bypassed.
I have found its firmware on the internet, but i don't know how to modify it yet... But maybe i'll not delay much to learn it if i begin to. But i think i'll not be able to change its kernel nor the bootloader, as i want, from the firmware only, only the ROM... So it would be a bit useless as the LG's negligency was most on its software, with that lack of Vulkan and 64-bit support stuff
hi everyone, I am new to this forum.
i've been interested in rooting / mods for my old Samsung s9 to give it a new life.
I did so by rooting it using the TWRP app in combination with the Magisk V23.0
now what happened was that i was downloading some random apps yesterday and for some reason the phone went on bootloop...
i accidentally deleted the system without making a backup lol... a little stupid of me...
now it keeps telling me that i've no OS on my phone. i was thinking that i could easily find the ''un-edited'' or simple version of my original OS. but i've looked through many sites without succes.. either looks 2 good to be true or just fake...
is there anyone who can advise me on what to do? i just want my phone to work with any OS right now... but which one is the cleanest or best to use? i do prefer a newer os like 10
thanks in advance!
If you still have access to recovery mode, your best choice would probably be installing LineageOS. It's the most lightweight ROM and many ROMs are based on Lineage. From what i can see, your phone is no longer officially supported.
I found this one based on Lineage 18.1 (Android 11). Before installing, take a look at the bugs, working, and installing sections.
And don't forget to install the Google Apps after installing the system and before rebooting.
that looks crispy. i appreciate your quick & good advise. can you tell me wether i can still run Magisk on it?
Yes, you can still flash Magisk or any type of root with both the OS and the GApps.
what i'm consider about is, wether a region code CRC matters?