Captain_cookie_200
Senior Member
Great to hear that it worked
Great to hear that it worked
is a kernel for a12 available yet?I did mention that this is A11-firmware-only right in the Supported device section tho....
A new build with A12 kernel is needed of course. The sooner Samsung release their source.
huh? what gsi did you use? i am on the latest A32 firmware for my region with the Arrow OS 12.1 sep patch gsi. Dont try any gsi's based on phh's 415 you likely tried one of those and it must have immidiately rebooted on samsung splash screen. although using crdroid v415-sep and arrow os from there are safe. infact its what i am using right now. although what vendor did you use the only vendor i found for this phone didnt boot.is a kernel for a12 available yet?
I've tried flashing a gsi on my device with andriod 12 and I couldn't get anything working not even to boot up and it's the first time this has happened, I followed all the steps for twrp but I can't boot anything even,I decrypted the storage,formated the data,installed a custom vendor and even without the custom vendor it doesn't boot,so I'm still currently on stock a12 with a slight issue that my mobile data disconnects every 5min
what firmware are you on and did you install any custom vendor? android 11 gsi's dont boot for me and some android 12 gsi's do not boot e.g. statix osI only tried phh's gsi's,in fact I tried 2,one was Corvus OS and Decendent OS and the vendor I used was from @klfld tut on how to install the gsi.
same problem here. i used an old firmware that didnt have this bug. Although IT WASNT OPTIMIZED AS MUCH AS THE LATEST FIRMWARE. so i just decided to go to custom gsi. since i am already dealing with lag. i used cheris OS now (idek how to pronounce). It looks amazing and even has the NOW playing feature from the pixel phones! I DONT HAVE TO INSTALL AMBIENT MUSIC MOD EPIK you can check it from here if you wantI flashed back to stock android 12 with the stock vendor,because I couldn't get anything to work, but I have a problem where my network completely disconnects but my emei is still there,but it's annoying because when I'm on a call it disconnects completely within 5min
uhhh i think its not under warranty anymore since you tried to flash a custom vendor, gsi earlier no? knox is gone and so is your warranty rip. So uh the problems i have with gsi's are as followsdo you still have that problem with the gsi though? also do you mind listing the steps and giving me the links of the twrpand vendor you used to install the gsi, I'd appreciate it because I literally locked my bootloader and everything with the intention of taking my phone back to my carrier because it is still under warranty but if I could get a gsi to work on here then I wouldn't have to
Ao instalar a imagem gsi através do twrp, diz que a imagem é muito grande.View attachment 5569861
Code:#include <not_my_phone.h> #include <std_disclaimer.h> /* * Your warranty is... still valid? * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this Recovery * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
TWRP 3.6.2_12.1 - Samsung Galaxy A32 4G
Current Status: Stable-ish
Supported Models:
Bugs known so far:
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
- TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
- Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge)
- If you are going to root, there is a patch needed to ensure functionality.
- USB-OTG
<!> PSA: I don't have the device to verify some of these bugs.
Download:
- TWRP (3.6.2): https://forum.xda-developers.com/attachments/twrp-3-6-2_12-1_s_hkk-tar.5641541/
- Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
- Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
- Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
- (Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
- Unlock Bootloader:
- Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
- Go back, go to Developer Settings.
- Turn on OEM unlock toggle.
- Desligue o telefone, segure vol-up + vol-down e, em seguida, conecte o cabo de carregamento (por favor, não use apenas um cabo de carregamento de terceiros, ele deve ter capacidade de transferência de dados).
Seu dispositivo inicializará no modo de download com um aviso. Aceite isso.
- Segure o volume para cima até que o telefone mostre o painel de desbloqueio do bootloader "Unlock Bootloader?".
- Pressione aumentar o volume novamente. Agora o bootloader do seu telefone está desbloqueado.
<!> Ele agora iniciará o processo de limpeza de dados. Deixe-o fazer o seu trabalho.
- Quando ele reiniciar no sistema operacional, termine de configurar seu dispositivo.
Verifique novamente se o desbloqueio OEM ainda está ativado.
- Preparando-se para a instalação:
- Baixe tudo acima para o seu PC.
- Instale o driver USB da Samsung.
- Abra Odin.
- Conecte seu telefone ao seu PC. Deve haver uma entrada COM no topo.
- Verifique se o seu telefone está no modo Download. (veja o passo 4 da seção Desbloquear Bootloader)
- Certifique-se de que OEM LOCK e REATIVATION LOCK em sua tela mostram "OFF". Se não estiver desligado, NÃO PROSSIGA MAIS.
<!> Para aqueles com bloqueio ativado, use seu dispositivo por 7 dias sem reiniciar uma vez. Em seguida, verifique os bloqueios acima novamente.
- Instalando :
- Certifique-se de que o telefone esteja no modo Download.
- Em Odin:
- Carregar em Userdata: arquivo VBMeta_disabler.tar.
- Carregar no AP: arquivo TWRP TAR.
- Se prepare. mantenha a mão no botão Aumentar volume e Liga / Desliga (não pressione ainda).
- Em Odin, pressione Iniciar. Ele piscará e, em seguida, reiniciará. Quando a tela desligar, pressione rapidamente o botão Vol-up e Power para inicializar a recuperação (isso deve levar cerca de 20 a 30 segundos).
<!> Você deve ter o TWRP instalado e funcionando agora.
- Pós-instalação:
- DEVE : Acionar o multi-desativador.
- No TWRP, vá para Avançado > Terminal.
- Digite
multidisabler
e digite. Se falhar com algo sobre o espaço livre do fornecedor, execute-o novamente.- Execute o
multidisabler
novamente.- Vá para a tela principal. vá para Wipe > Format Data, digite
yes
e deslize.- Reinicie para Recuperação. Agora você pode fazer outras coisas.
- Deve: Fazer backup de todas as partições vitais:
- No TWRP, vá para Backup
- Backup: EFS, Modem, NVRAM.
- Se você deseja fazer o root, DEVE : tornar o NVD_IMEI somente leitura.
<!> Magisk tem um bug em dispositivos MTK A onde depois de algum tempo o IMEI é perdido, causando perda de comunicação móvel.
<!> Por enquanto, evite rootear seu A32.
<!> Se você ainda deseja continuar, FAÇA BACKUP DE TUDO PRIMEIRO, ESPECIALMENTE NVRAM/EFS. Em seguida, siga as instruções aqui como mitigação no OneUI:
https://forum.xda-developers.com/t/fixed-rooted-a325m-suddenly-no-imei-no-sim.4386753/post-86588571
Problema do Magisk: https ://github.com/topjohnwu/Magisk/issues/1801
Atualizarei isso quando o problema for corrigido. E, claro, siga o tópico XDA acima para atualizações completas. A mitigação não é perfeita e os usuários já relataram algumas peculiaridades.
- Aproveite: reinicie seu telefone para ter um estoque enraizado, instale coisas personalizadas ou faça o que quiser.
Melhoria:
<!> Use quando você já tiver qualquer recuperação personalizada instalada (TWRP, SHRP, Ofox e similares)
<!> Você também pode usar o Odin para atualizar, as etapas semelhantes à seção Instalar. Toda pós-instalação, se já feita, é desnecessária para ser feita novamente.
- Baixe a imagem TWRP em vez disso: https://github.com/almondnguyen/twr...a32-20220703/TWRP-3.6.2_12.1-a32-20220703.img
- Copie-o para o telefone e reinicie para o TWRP (Combo é Power + Volume-up)
- Vá: Instalar > Instalar imagem > selecione o arquivo TWRP .img > selecione Recuperação
- Deslize para confirmar a piscar.
- Se for bem-sucedido, reinicie para recuperação.
GSI e coisas relacionadas:
GSI deve ser flashable diretamente agora. Grande crédito para @Long266
- Instale o TWRP, faça todas as instruções.
- Baixe um GSI. Phh é um bom começo.
![]()
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.github.com
- Se baixou um arquivo XZ, extraia-o para obter um arquivo IMG. Copie o arquivo IMG para o seu telefone.
- Reinicie no TWRP.
- Toque em Instalar > Instalar Imagem > Selecione seu arquivo GSI .img.
- Selecione Imagem do sistema e, em seguida, flash.
- Se anteriormente você estava em estoque, Limpar > Formatar dados.
- Reiniciar sistema.
- Lucro.
Códigos fonte:
- Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
- Dispositivo TWRP: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Créditos:
- Desenvolvedores envolvidos na criação e manutenção de TWRP, twrpdtgen, Magisk e software básico.
- Todos os testadores.
- @Long266 como testador, collab-dev.
- @ianmacd para multidesativador.
- @afaneh92 para uma árvore base 32x e multidisabler MTK-Samsung.
- @dronkit e @Mighty_Rearranger para correção de IMEI Magisk em dispositivos MTK.
- @klfld para guia de instalação do GSI.
Versões mais antigas:
[ocultar]
[/ocultar]
- TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
- TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Informações do rodapé:
Situação: Beta
Versão Estável Atual: 3.6.2_12.1
Criado: 2022-03-24
Última atualização: 2022-07-03
Qual versão do android você está usando?Ao instalar a imagem gsi através do twrp, diz que a imagem é muito grande.
I tried some like crdroid, pixel, lineage, spark, arrow etc, all android 12
Bagaimana cara install custom room dengan TWRP 3.6.2 mungkin bisa dijelaskanAnda dapat menggunakan "instal Gambar" di bawah TWRP.
Dari bagian <!> Untuk info lebih lanjut, unduh file .img, salin ke ponsel Anda. Lalu pergi ke TWRP > Install > Install Image > pilih TWRP img > pilih Recovery to flash.
Jika sudah selesai, langkah pasca instalasi tidak perlu dilakukan lagi.
sunting: bagian pemutakhiran ditambahkan ke pos utama.
udah coba android 13 spark os? Anda harus menginstal stock firmware samsung android 11 terlebih dahulu agar bisa boot. setelah itu sangat h
Trimakasih atas sarannya saya sudah mencoba banyak cara tetapi masih gagal dengan hasil nullBahasa inggris
tidak ada custom rom untuk perangkat ini. ada sesuatu yang dikenal sebagai gambar sistem generik. disana banyak tersedia. Anda dapat melihat mereka di sini. cukup flash dan pilih sistem dan setelah reboot boot. tentu saja menghapus data dan hal-hal lain. di sini
Diterjemahkan
tidak ada custom rom untuk perangkat ini. ada sesuatu yang dikenal sebagai gambar sistem generik. disana banyak tersedia. Anda dapat melihat mereka di sini. cukup flash dan pilih sistem dan setelah reboot boot. tentu saja menghapus data dan hal-hal lain. di sini
Bagaimana cara install custom room dengan TWRP 3.6.2 mungkin bisa
SAya sudah melakukan hal itu tetapi masih gagal dengan hasil nullBagaimana cara install custom room dengan TWRP 3.6.2 mungkin bisa dijelaskan
EnglishTrimakasih atas sarannya saya sudah mencoba banyak cara tetapi masih gagal dengan hasil null
SEkali lagi trimaksih atas sarannya ,, saya sudah menggunakan firemwear andro 11 ,, dan posisi sudah di root ,, saya butuh twrp hanya untuk pasang costom room ,, dari sekian banyak costom room yang saya coba semunya gagal dengan hasil sama ,, mungkin anda ada saran saya harus pasang gsi yang mana??Bahasa inggris
mengapa apa yang terjadi setiap kali? gsi apa coba? saya juga menyarankan untuk mem-flash firmware Android 11 terlebih dahulu. Gambar sistem generik Android 11,12,13 bisa boot dengan baik di atasnya. Vendor Android 12 lamban dan Android 13 tidak bisa boot .
Diterjemahkan
mengapa apa yang terjadi setiap kali? gsi apa coba? saya juga menyarankan untuk mem-flash firmware Android 11 terlebih dahulu. Gambar sistem generik Android 11,12,13 bisa boot dengan baik di atasnya. Vendor Android 12 lamban dan Android 13 tidak bisa booting.
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
multidisabler
, then enter. If it fails with something about vendor free space, run it again.multidisabler
again.yes
then swipe.I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
I should clarify that I don't own the device and all the testing was/is done by @Long266 .I can't install large IMG files to internal memory? For example a gsi?
Very good job!!!I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.