#crdroid — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #crdroid, aggregated by home.social.
-
crDroid 12.7
#crDroid #Official #QPR2 #ROM #miatoll
| OFFICIAL
Android: 16
Build date: 11.02.2026
Maintainer: kardebayanhttps://garitoshare.space/index.php/topic,90.msg110.html#msg110
-
crDroid 12.7
#crDroid #Official #QPR2 #ROM #miatoll
| OFFICIAL
Android: 16
Build date: 11.02.2026
Maintainer: kardebayanhttps://garitoshare.space/index.php/topic,90.msg110.html#msg110
-
crDroid 12.7
#crDroid #Official #QPR2 #ROM #miatoll
| OFFICIAL
Android: 16
Build date: 11.02.2026
Maintainer: kardebayanhttps://garitoshare.space/index.php/topic,90.msg110.html#msg110
-
crDroid 12.7
#crDroid #Official #QPR2 #ROM #miatoll
| OFFICIAL
Android: 16
Build date: 11.02.2026
Maintainer: kardebayanhttps://garitoshare.space/index.php/topic,90.msg110.html#msg110
-
In order to watch the Super Bowl, as well as get access to the Jurassic World movies to satisfy my kiddo's current obsession with all things dinosaur, I did a month's subscription to Peacock. In installing the Peacock app onto my Android phone running a "degoogled" crDrojd rom, TrackerControl detected a hilarious level of 10 embedded known trackers. Without the protection of a blocker like TrackerControl, this supposed streaming service is also a data mining extravaganza, sending tons of info back to all kinds of 3rd parties.
#SuperBowl #privacy #android #apps #trackercontrol #crdroid #Peacock #datamining #streaming #movies #enshittification #degoogled -
Necesito ayuda urgente porfi 🙏
✅SOLUCIONADO: He repetido el proceso, me aparece en el ADB y además resulta que se me olvidaba el firmware jeje. A ver si sigue yendo bien
ACTUALIZACIÓN: ahora he logrado que se inicie /e/OS pero no tengo wifi ni detecta la SIM. He visto por ahí que conviene instalar la rom original y volver a intentar instalar luego /e/OS pero no sé si funcionará
Quería instalar /e/OS en mi Poco X5 Pro 5G y he seguido las instrucciones (link abajo).
Lo que ha pasado es lo siguiente:
1. flasheo bien el recovery de crdroid
2. formateo
3. con ADB meto la ROM.zip
4. Se queda al 47% y en el recovery me pregunta si quiero meter algo más. Le digo que no para que reinicie al sistema
5. Me aparece el recovery de /e/OS, supongo que debo instalar la rom desde ahí pero en ADB no aparece mi dispositivoAsí que mi movil está atascado ahí hasta que logre instalar algo. ¿Alguien podría ayudarme o tiene alguna intuición de qué falla? ¿No debería usar el recovery de crdroid y he entendido mal lo que explica en el link? Estoy un poco desesperado.
-
На древнем мобильнике с 9-м Android'ом использование Conversations оказалось несколько затруднено. Всё дело в голосовых сообщения, записываемых в m4a-контейнеры и сжатием AAC-кодеком. Минимальный размер любого аудио-сообщения получался четыреста килобайт, если открыть в hex-редакторе эти 400Кб, то есть заголовок, есть окончание, а между ними сплошные нули.
В целом оно и ясно, Conversations обращается через API SDK к системе, таковая как умеет так и работает с m4a-контейнерами. На момент 9-го ведройда поддержка m4a была не повсеместно (лишь на устройствах отдельных вендоров).
Пришлось накатить на мобильник 16-й Android, благо что 23-я LineageOS это предоставляет. Минимальные голосовые сообщения в Conversations стали теперь порядка семи килобайт.
И как бы с одной стороны 400Кб, с другой 7Кб ... ну как-то разница ощутима. На родных вендоровских прошивках других производителей других мобильников в 16-м ведройде аудио-сообщения получаются таких же размеров.
И для сравнения, если взять 14-й Android в варианте от LineageOS или же crDroid, то минимальный размер аудио-сообщения выходит несколько больше, порядка 14Кб или 19Кб что ли. Хоть и в два раза, но однозначно это не тот выигрыш, чтобы ради него с 14-го ведройда переводить мобильник на 16-й :)
В любом случае, спасибо ребятам из LineageOS и crDroid, если бы не свежие версии Android для «устаревших» мобильников, но и не пришлось бы научиться менять аккумуляторы самостоятельно в домашних условиях. А так вот, получается иметь прямо даже запас из аппаратов, пусть и поношенных и устаревших (технически и морально). Не фиг свалки захламлять, планеты запасной ещё не обзавелись, пусть работает то, что может работать.
#aac #m4a #multimedia #android #mobile #Conversations #xmpp #jabber #LineageOS #crDroid #lang_ru -
На древнем мобильнике с 9-м Android'ом использование Conversations оказалось несколько затруднено. Всё дело в голосовых сообщения, записываемых в m4a-контейнеры и сжатием AAC-кодеком. Минимальный размер любого аудио-сообщения получался четыреста килобайт, если открыть в hex-редакторе эти 400Кб, то есть заголовок, есть окончание, а между ними сплошные нули.
В целом оно и ясно, Conversations обращается через API SDK к системе, а так как умеет так и работает с m4a-контейнерами, с учётом того, что на момент 9-го ведройда поддержка m4a была не повсеместно (а лишь на устройствах отдельных вендоров).
Пришлось накатить на мобильник 16-й Android, благо что 23-я LineageOS это предоставляет. Минимальные голосовые сообщения в Conversations стали теперь порядка семи килобайт.
И как бы с одной стороны 400Кб, с другой 7Кб ... ну как-то разница ощутима. На родных вендоровских прошивках других производителей других мобильников в 16-м ведройде аудио-сообщения получаются таких же размеров.
И для сравнения, если взять 14-й Android в варианте от LineageOS или же crDroid, то минимальный размер аудио-сообщения выходит несколько больше, порядка 14Кб или 19Кб что ли. Хоть и в два раза, но однозначно это не тот выигрыш, чтобы ради него с 14-го ведройда переводить мобильник на 16-й :)
В любом случае, спасибо ребятам из LineageOS и crDroid, если бы не свежие версии Android для «устаревших» мобильников, но и не пришлось бы научиться менять аккумуляторы самостоятельно в домашних условиях. А так вот, получается иметь прямо даже запас из аппаратов, пусть и поношенных и устаревших (технически и морально). Не фиг свалки захламлять, планеты запасной ещё не обзавелись, пусть работает то, что может работать.
#aac #m4a #multimedia #android #mobile #Conversations #xmpp #jabber #LineageOS #crDroid #lang_ru -
So many weird decisions at Apple in recent 2-3 years, both UI wise and conceptually. By now it feels as if parts of macOS were vibe coded, considering the level of inconsistency and instability. They start to switch things around, then suddenly stop half-way. Doesn't matter if along the way things broke. Now we need to drop everything and focus on AI 🙄
They are doing some great work as well. Passkeys are nice and the improvements for passkeys in macOS Tahoe are welcome - users can now export passkeys - yey! But how can I install - let alone enjoy - that new UI style, after Tim Apple bowed down to Trump and handed over that ridiculous glass trophy in the new UI style?
That OS 26 look is the first time I really feel I won't accustom to what Apple thinks is good for users. I have an iPad running iPadOS26 and it just made me use my #CrDroid customOS tablet more and the iPad less.
It's not even funny anymore. And I am a long time macOS user and love that OS. #enshittification at full speed 😢
I wish I could erase that video out of my memory, really!
youtube.com/watch?v=cjAPyyugM6Q
On the bright side: I discovered Android, Linux, CustomRoms, Linux phones - so thanks Apple I guess? :black_sparkling_heart: -
Hey #lineageos users, is #crdroid good ? Researching compatibility for my eventual phone replacement once the current one kicks the bucket for good
-
Übrigens: die App der ING funktioniert sogar auf meinem gerooteten Android, mit Custom ROM, und ohne jegliche Google Play-Dienste installiert.
(crDroid 11.7, Android 15, Google Pixel 8a)
Ich hatte mir extra einen TAN-Generator bestellt und eingerichtet, aber aus reinem Interesse die App installiert; und siehe da: die funktioniert entgegen allen Erfahrungsberichten komplett einwandfrei!
Nur halt keine Benachrichtigungen, aber das ist ja ohne Push Service eh normal.
#degoogled #LineageOS #crDroid #Android #CustomRoms #ING #Bank #Finanzen
-
Übrigens: die App der ING funktioniert sogar auf meinem gerooteten Android, mit Custom ROM, und ohne jegliche Google Play-Dienste installiert.
(crDroid 11.7, Android 15, Google Pixel 8a)
Ich hatte mir extra einen TAN-Generator bestellt und eingerichtet, aber aus reinem Interesse die App installiert; und siehe da: die funktioniert entgegen allen Erfahrungsberichten komplett einwandfrei!
Nur halt keine Benachrichtigungen, aber das ist ja ohne Push Service eh normal.
#degoogled #LineageOS #crDroid #Android #CustomRoms #ING #Bank #Finanzen
-
Übrigens: die App der ING funktioniert sogar auf meinem gerooteten Android, mit Custom ROM, und ohne jegliche Google Play-Dienste installiert.
(crDroid 11.7, Android 15, Google Pixel 8a)
Ich hatte mir extra einen TAN-Generator bestellt und eingerichtet, aber aus reinem Interesse die App installiert; und siehe da: die funktioniert entgegen allen Erfahrungsberichten komplett einwandfrei!
Nur halt keine Benachrichtigungen, aber das ist ja ohne Push Service eh normal.
#degoogled #LineageOS #crDroid #Android #CustomRoms #ING #Bank #Finanzen
-
Übrigens: die App der ING funktioniert sogar auf meinem gerooteten Android, mit Custom ROM, und ohne jegliche Google Play-Dienste installiert.
(crDroid 11.7, Android 15, Google Pixel 8a)
Ich hatte mir extra einen TAN-Generator bestellt und eingerichtet, aber aus reinem Interesse die App installiert; und siehe da: die funktioniert entgegen allen Erfahrungsberichten komplett einwandfrei!
Nur halt keine Benachrichtigungen, aber das ist ja ohne Push Service eh normal.
#degoogled #LineageOS #crDroid #Android #CustomRoms #ING #Bank #Finanzen
-
Übrigens: die App der ING funktioniert sogar auf meinem gerooteten Android, mit Custom ROM, und ohne jegliche Google Play-Dienste installiert.
(crDroid 11.7, Android 15, Google Pixel 8a)
Ich hatte mir extra einen TAN-Generator bestellt und eingerichtet, aber aus reinem Interesse die App installiert; und siehe da: die funktioniert entgegen allen Erfahrungsberichten komplett einwandfrei!
Nur halt keine Benachrichtigungen, aber das ist ja ohne Push Service eh normal.
#degoogled #LineageOS #crDroid #Android #CustomRoms #ING #Bank #Finanzen
-
I am currently researching at the FSFE for FreeYourAndroid on the topic of microG.
If you use microG, how have you installed it? Or was it already there?
(User app can come from F-Droid repo too)
---
Ich recherchiere gerade bei der #FSFE für #FreeYourAndroid zum Thema #microG.
Falls du es benutzt, wie hast du es installiert? Oder war es bereits da?
#Android #Google #Privacy #PlayServices #Whatsapp #Navigation #DBNavigator #LineageOS #iodeOS #eOS #CalyxOS #CrDroid #UnifiedPush #BeaconDB
-
Wollte gerade ein Bankkonto eröffnen.
Wieso haben wir überhaupt die #eID und die #AusweisApp, wenn wir gleichzeitig noch das #Postident haben?? Wieso muss in Deutschland immer alles drei, vier redundante Lösungen für alles haben?
Postident-App geht nicht auf #degoogled #Android, die Videoverifikation soll auch auf dem PC gehen, aber Infos dazu gibt es nicht; funktionieren tut's auch ned.
Das heißt, ich muss jetzt stattdessen zu ner Postfiliale latschen. Toll, danke.
Freu mich schon drauf, wenn diese Offline-Optionen ganz abgeschafft werden. Ich hab ja schon die eID aktivieren müssen, weil man ohne #Elster nicht mehr selbstständig sein kann. Aber da ist die AusweisApp wenigstens #FOSS und funktioniert auf meinem gerooteten Smartphone.
-
My Redmi Note 13 Pro 5G running crDroid has been experiencing some weird buggy issues on my keyboard, apps, and the entire UI.
For some weird reason, after the recent October update, the phone started bugging out several times. The vibration effects on keyboards would stop working and then sometimes just shuts itself down; when I restart the phone, it shows that a sign of a completely empty battery when there's still 10-20% of charge left.
Another problem is also when the U.I. just flickers rapidly for no reason as well as my FUTO keyboard crashes so many times that it is becoming extremely annoying.
I don't know why this is happening, I'm planning on a firmware upgrade with @AmyIsCoolz but until then, I can only fix this issue by restarting the damn phone whenever the vibrations stop working.
-
Sto per cambiare #rom sul mio #miatoll faccio l'update alla #crdroid A16, cambia qualcosa per il #playintegrityapi se metto le #NikGapps invece delle #microg? Non credo cambi molto non lo passerò ugualmente 🤔🤔 @android @tecnologia
-
È arrivato il mio momento, #Revolut ha deciso arbitrariamente di bloccare la mia app, ho resistito fino ad ora sperando non succedesse, ed ora! #noplayintegrityapi #playintegrtyapi #google #googlemerda #lineageos #crdroid #aospe #android #root #magisk #mastoaiuto
Che poi di fatto al momento mi rileva il root non l'integrità, eppure magisk è installato con un nome diverso e c'è l'offuscamento attivo sulle app 🤷🏻♂️🤷🏻♂️🤷🏻♂️ #boostme -
È arrivato il mio momento, #Revolut ha deciso arbitrariamente di bloccare la mia app, ho resistito fino ad ora sperando non succedesse, ed ora! #noplayintegrityapi #playintegrtyapi #google #googlemerda #lineageos #crdroid #aospe #android #root #magisk #mastoaiuto
Che poi di fatto al momento mi rileva il root non l'integrità, eppure magisk è installato con un nome diverso e c'è l'offuscamento attivo sulle app 🤷🏻♂️🤷🏻♂️🤷🏻♂️ #boostme -
È arrivato il mio momento, #Revolut ha deciso arbitrariamente di bloccare la mia app, ho resistito fino ad ora sperando non succedesse, ed ora! #noplayintegrityapi #playintegrtyapi #google #googlemerda #lineageos #crdroid #aospe #android #root #magisk #mastoaiuto
Che poi di fatto al momento mi rileva il root non l'integrità, eppure magisk è installato con un nome diverso e c'è l'offuscamento attivo sulle app 🤷🏻♂️🤷🏻♂️🤷🏻♂️ #boostme -
È arrivato il mio momento, #Revolut ha deciso arbitrariamente di bloccare la mia app, ho resistito fino ad ora sperando non succedesse, ed ora! #noplayintegrityapi #playintegrtyapi #google #googlemerda #lineageos #crdroid #aospe #android #root #magisk #mastoaiuto
Che poi di fatto al momento mi rileva il root non l'integrità, eppure magisk è installato con un nome diverso e c'è l'offuscamento attivo sulle app 🤷🏻♂️🤷🏻♂️🤷🏻♂️ #boostme -
È arrivato il mio momento, #Revolut ha deciso arbitrariamente di bloccare la mia app, ho resistito fino ad ora sperando non succedesse, ed ora! #noplayintegrityapi #playintegrtyapi #google #googlemerda #lineageos #crdroid #aospe #android #root #magisk #mastoaiuto
Che poi di fatto al momento mi rileva il root non l'integrità, eppure magisk è installato con un nome diverso e c'è l'offuscamento attivo sulle app 🤷🏻♂️🤷🏻♂️🤷🏻♂️ #boostme -
I am wondering if there is a tool that list all degoogled alternative ROMs and their supported devices.
#eOS #IodeOS #GrapheneOS #LineageOS #crDroid #degoogled #microG
-
@willsilvah @luizinho94 @frufru Tenho um #Samsung.
Como usava muito #crDroid meio que tive que adaptar umas coisas, mas até que ta prestando sistema. -
@willsilvah Tente o #crDroid
Boa alternativa ao LineageOS.
Só tem um #problema.
Atualmente está ficando complicado usar aparelho com #customROM -
Are there any "advanced" #android rooting/modding support channels? Places where I can ask things like:
* Is it possible for me to decrypt and mount the /data partition manually from the lineageos recovery?
* What exactly was it that google changed about play integrity that broke bypasses? It doesn't seem to affect microg, will it in the future?
* How are secrets stored in the keystore and can I disable the hardware keystore to make backups work? -
Hmm... Apparently, it's not easy reverting from #postmarketOS back to #LineageOS or #crdroid
Slot A works, slot B refuses to boot (stuck in "bootloader unlocked" screen), although I followed the complete crDroid install instructions, which wipes everything.
(Linux: no, there are no msm tools)
-
I have only 16 gb of storage on my Galaxy s5, but the phone supports external sd cards up to 128 gb and luckily I have one :D
I plan to use this phone primarily for audio books, podcasts and other offline media.
But most of apps either do not support selecting custom folder for their content or even aren't moveable to sd card.
I found an app called "app mgr iii" which requires root access (thanks that I have it) and moves any app to sd card ignoring app's manifest.
Will it be stable? We will know in future. Now the av3715 app (Russian free audio books for #blind) successfully downloads its content and works after moving it to sd.Other apps will be checked too soon :D
-
After the welcome process you'll see a standard #CRDroid launcher which is fully accessible and is very simple.
I use Microsoft Launcher on my primary phone but for the sake of battery and cpu optimization I'll stick to the default launcher on this old Samsung.Some accessibility labels in the UI are not translated to Russian and some buttons on recent apps screen have no accessibility labels at all.
The left one is for share, the middle one is for force kill of current app and the right one is for closing all apps.
Or enable read identifiers in Talk Back and get English names of these buttons.Btw, Jieshuo screenreader works fine on this phone and as usual is much much faster than Talk Back, so I switch to it and leave Talk Back as a backup method.
Advanced Braille Keyboard #abk works fine too and I'm happy about that :D
-
After the welcome process you'll see a standard #CRDroid launcher which is fully accessible and is very simple.
I use Microsoft Launcher on my primary phone but for the sake of battery and cpu optimization I'll stick to the default launcher on this old Samsung.Some accessibility labels in the UI are not translated to Russian and some buttons on recent apps screen have no accessibility labels at all.
The left one is for share, the middle one is for force kill of current app and the right one is for closing all apps.
Or enable read identifiers in Talk Back and get English names of these buttons.Btw, Jieshuo screenreader works fine on this phone and as usual is much much faster than Talk Back, so I switch to it and leave Talk Back as a backup method.
Advanced Braille Keyboard #abk works fine too and I'm happy about that :D
-
After the welcome process you'll see a standard #CRDroid launcher which is fully accessible and is very simple.
I use Microsoft Launcher on my primary phone but for the sake of battery and cpu optimization I'll stick to the default launcher on this old Samsung.Some accessibility labels in the UI are not translated to Russian and some buttons on recent apps screen have no accessibility labels at all.
The left one is for share, the middle one is for force kill of current app and the right one is for closing all apps.
Or enable read identifiers in Talk Back and get English names of these buttons.Btw, Jieshuo screenreader works fine on this phone and as usual is much much faster than Talk Back, so I switch to it and leave Talk Back as a backup method.
Advanced Braille Keyboard #abk works fine too and I'm happy about that :D
-
After the welcome process you'll see a standard #CRDroid launcher which is fully accessible and is very simple.
I use Microsoft Launcher on my primary phone but for the sake of battery and cpu optimization I'll stick to the default launcher on this old Samsung.Some accessibility labels in the UI are not translated to Russian and some buttons on recent apps screen have no accessibility labels at all.
The left one is for share, the middle one is for force kill of current app and the right one is for closing all apps.
Or enable read identifiers in Talk Back and get English names of these buttons.Btw, Jieshuo screenreader works fine on this phone and as usual is much much faster than Talk Back, so I switch to it and leave Talk Back as a backup method.
Advanced Braille Keyboard #abk works fine too and I'm happy about that :D
-
After the welcome process you'll see a standard #CRDroid launcher which is fully accessible and is very simple.
I use Microsoft Launcher on my primary phone but for the sake of battery and cpu optimization I'll stick to the default launcher on this old Samsung.Some accessibility labels in the UI are not translated to Russian and some buttons on recent apps screen have no accessibility labels at all.
The left one is for share, the middle one is for force kill of current app and the right one is for closing all apps.
Or enable read identifiers in Talk Back and get English names of these buttons.Btw, Jieshuo screenreader works fine on this phone and as usual is much much faster than Talk Back, so I switch to it and leave Talk Back as a backup method.
Advanced Braille Keyboard #abk works fine too and I'm happy about that :D
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
So, I've flashed #CRDroid version 7.39 with #Android 11.
You can find flashing instructions around the internet. I rather give you a bunch of useful links for you to not search and download something random.We need #Odin to flash something because Samsung's download mode isn't compatible with Fastboot and only operable via their program.
I've used #Odin3 v3.14 which my friend gave to me. Probably you can download it here but I'm not sure:
https://odindownload.com/download/Odin3_v3.14.4.zipAlso we need #TWRP recovery; It's available on the official website (we need a tar file, not the bare img):
https://dl.twrp.me/klte/And of course we need official CRDroid:
https://crdroid.net/klte/7If you need #Root, then download #magisk (but this CRDroid already includes some minimal root):
https://github.com/topjohnwu/Magisk/releasesThat's it! Download, Flash by following instructions and enjoy!
-
So, I've flashed #CRDroid version 7.39 with #Android 11.
You can find flashing instructions around the internet. I rather give you a bunch of useful links for you to not search and download something random.We need #Odin to flash something because Samsung's download mode isn't compatible with Fastboot and only operable via their program.
I've used #Odin3 v3.14 which my friend gave to me. Probably you can download it here but I'm not sure:
https://odindownload.com/download/Odin3_v3.14.4.zipAlso we need #TWRP recovery; It's available on the official website (we need a tar file, not the bare img):
https://dl.twrp.me/klte/And of course we need official CRDroid:
https://crdroid.net/klte/7If you need #Root, then download #magisk (but this CRDroid already includes some minimal root):
https://github.com/topjohnwu/Magisk/releasesThat's it! Download, Flash by following instructions and enjoy!
-
So, I've flashed #CRDroid version 7.39 with #Android 11.
You can find flashing instructions around the internet. I rather give you a bunch of useful links for you to not search and download something random.We need #Odin to flash something because Samsung's download mode isn't compatible with Fastboot and only operable via their program.
I've used #Odin3 v3.14 which my friend gave to me. Probably you can download it here but I'm not sure:
https://odindownload.com/download/Odin3_v3.14.4.zipAlso we need #TWRP recovery; It's available on the official website (we need a tar file, not the bare img):
https://dl.twrp.me/klte/And of course we need official CRDroid:
https://crdroid.net/klte/7If you need #Root, then download #magisk (but this CRDroid already includes some minimal root):
https://github.com/topjohnwu/Magisk/releasesThat's it! Download, Flash by following instructions and enjoy!
-
So, I've flashed #CRDroid version 7.39 with #Android 11.
You can find flashing instructions around the internet. I rather give you a bunch of useful links for you to not search and download something random.We need #Odin to flash something because Samsung's download mode isn't compatible with Fastboot and only operable via their program.
I've used #Odin3 v3.14 which my friend gave to me. Probably you can download it here but I'm not sure:
https://odindownload.com/download/Odin3_v3.14.4.zipAlso we need #TWRP recovery; It's available on the official website (we need a tar file, not the bare img):
https://dl.twrp.me/klte/And of course we need official CRDroid:
https://crdroid.net/klte/7If you need #Root, then download #magisk (but this CRDroid already includes some minimal root):
https://github.com/topjohnwu/Magisk/releasesThat's it! Download, Flash by following instructions and enjoy!
-
So, I've flashed #CRDroid version 7.39 with #Android 11.
You can find flashing instructions around the internet. I rather give you a bunch of useful links for you to not search and download something random.We need #Odin to flash something because Samsung's download mode isn't compatible with Fastboot and only operable via their program.
I've used #Odin3 v3.14 which my friend gave to me. Probably you can download it here but I'm not sure:
https://odindownload.com/download/Odin3_v3.14.4.zipAlso we need #TWRP recovery; It's available on the official website (we need a tar file, not the bare img):
https://dl.twrp.me/klte/And of course we need official CRDroid:
https://crdroid.net/klte/7If you need #Root, then download #magisk (but this CRDroid already includes some minimal root):
https://github.com/topjohnwu/Magisk/releasesThat's it! Download, Flash by following instructions and enjoy!
-
I have found an old Samsung Galaxy s5 while reorganizing my old boxes with technical stuff.
16 gb of storage, 2 gb of ram, 32-bit cpu, Samsung Touch Wiz on Android 6.0.1, everything working but battery is almost dead.
Perfect target for crazy experiments, isn't it?I've flashed #CRDroid 7 with #Android 11 without #gapps.
The latest update was in February 2024 and this is an official end of life for this device. But still it works and Android 11 on a device which was abandoned officially on Android 6 is stable and smooth.
Not the fastest of course, but works and doesn't freeze every second.
I'd say it is comfortably usable for some tasks.In the series of posts I will tell my experience and share anything I find useful.
So check replies to this post or visit my profile :D
-
А ещё я тут откопал в кладовке #Samsung Galaxy s5, и о боже, он включился.
Лагал он нещадно, но всё же протупился и показал, что хоть как-то работать он может.
В итоге на следующий же день на него был залит #twrp и #crdroid с Android 11 (на минуточку из коробки там был 6 андроид и не было обновлений).
Полёт нормальный, гаппсы я туда ставить не рискнул (ибо умрёт, с двумя-то гб озу), поэтому постараюсь тут в серии постов на английском рассказать о своём опыте true #degoogle :D -