As we are lacking other sections like Q/A forum, General forum, so I created this thread which will be a all in one general thread. So now onwards don't create a thread for your problem, help or advice instead post within this thread.
Only we are supposed to keep our forum clean and tidy.
Let the discussions begin! :silly:
Recovery mode not working
Hi all,
I have a question about recovery mode. Here is the whole history step by step, that also might help new people:
Yesterday, I rooted my Samsung Galaxy GT-I8160L. The successful procedure used was the one described here.
Then I wanted to do a backup using Clockworkmod (known as CWM) method, so I downloaded and installed the kernel I8160XXLD8 with CWM recovery support, also successfully, because I read somewhere that there is no way to install CWM with other method for this phone, was it right? This is the link.
To here, everything so far, so good. Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Any advices? I think there is something related with the system partition. Maybe in one of those desperate tries I did check the re-partition checkbox in Odin and messed it up.
I'm writing my question here hoping this is the rigth place :laugh:
---------- Post added at 06:45 PM ---------- Previous post was at 06:11 PM ----------
munrolazar said:
Hi all,
I have a question about recovery mode. Here is the whole history step by step, that also might help new people:
Yesterday, I rooted my Samsung Galaxy GT-I8160L. The successful procedure used was the one described here.
Then I wanted to do a backup using Clockworkmod (known as CWM) method, so I downloaded and installed the kernel I8160XXLD8 with CWM recovery support, also successfully, because I read somewhere that there is no way to install CWM with other method for this phone, was it right? This is the link.
To here, everything so far, so good. Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Any advices? I think there is something related with the system partition. Maybe in one of those desperate tries I did check the re-partition checkbox in Odin and messed it up.
I'm writing my question here hoping this is the rigth place :laugh:
Click to expand...
Click to collapse
Seems to be that in my desperation I kept pressed vol up + home + power, so it never entered the mode. I just released the power button once the phone vibrates and now enters recovery mode as explained here. Now I think the errors are clear. The following error messages are shown below the CWM-based Recovery:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
This error messages keep showing. For example, if I try to do a backup restore from the external sd card, I choose backup and restore menu, and then Backup, this is what is shown:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
What can I do?
.Thanks
Samsung Galaxy Ace 2 I-8160L default ROM with PIT file download
I solved the problem myself. But I'm going to describe the steps of what I did ok, what crashed everything and how I solved.
Smart Phone Model: Samsung Galaxy Ace 2 I-8160L
How to root it http://forum.xda-developers.com/showpost.php?p=27610432&postcount=31
Add Clockworkmod (also known as CWM) to recovery mode to create backups http://forum.xda-developers.com/showthread.php?p=30792392#post30792392
What I did wrong
Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Seems to be that in my desperation I kept pressed vol up + home + power, so it never entered the mode. I just released the power button once the phone vibrates and now enters recovery mode as explained here. Now I think the errors are clear. The following error messages are shown below the CWM-based Recovery:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
This error messages keep showing. For example, if I try to do a backup restore from the external sd card, I choose backup and restore menu, and then Backup, this is what is shown:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
How to fix it
Well, this might be just one way to fix it. I downloaded a lot of firmware files from SamMobile (nice guys, by te way) but none of these worked.
A very nice guy posted a very useful backup of the I-8160L that can be downloaded from here (this is the forum entry in spanish). This download is worth the time, and even the subscription to the site because it contains:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
CSC_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY-CSC-MULTI-UUB_LH1_4G.tar.md5
GT-I8160L_LA_UB_4G.pit
Odin3_v1.84.exe
Odin3.ini
Click to expand...
Click to collapse
Yes! This file contains the PIT file for the Samsung Galaxy Ace 2 I-8160L. But Wait! Do not install it yet. I'm not an expert in root development, but I used to fail installing the original ROM. I flashed my phone again with this file in the PDA field:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
Click to expand...
Click to collapse
Of ODIN and it worked! No PIT file needed!
======
Resolví el problema solo. Pero voy a describir los pasos de lo que hice bien, lo que dañó todo y cómo lo resolví.
Modelo del Smart Phone: Samsung Galaxy Ace 2 I-8160L
Cómo hacerle el proceso de Root (en inglés) http://forum.xda-developers.com/showpost.php?p=27610432&postcount=31
Agregar Clockworkmod (también conocido como CWM) en modo Recovery para crear copias de seguridad (en inglés) http://forum.xda-developers.com/showthread.php?p=30792392#post30792392
¿Qué hice mal?
Quise instalar un ROM personalizado, y sé que hice algo mal porque los problemas de rutas de archivo empezaron a aparecer, principalmente con el error "no /cache directory found", y luego haciendo el procedimiento con una ROM de fábrica desde Odin, pienso que eso dañó todo más profundamente: ahora el teléfono ni siquiera podía entrar en modo de recuperación. Pero el modo de descarga funcionaba, con el modo Odin, e incluso el contador de flash seguía operando.
Desde ahí, empecé a leer y probar cosas, pero nada funcionó: hacer el flash de la ROM original, usar Samsung Kies para restaurar las condiciones de fábrica... nada funcionaba, y el contador seguía corriendo; Kies fallaba cada vez, llegaba hasta el procedimiento de firmware de emergencia, descargaba algo, pero luego se cerraba.
Incluso intenté con las herramientas de adb tools desde la línea de comando, en la cual el teléfono era reconocido, con el comando ./adb devices. Cuando intentaba hacer un shell al teléfono, se mostraba el error: exec '/system/bin/sh' failed: I/O error (5)
Parece que en mi desesperación mantuve presionado volúmen arriba + botón home + botón encendido, así que nunca entraba al modo que quería. Una vez uno siente que el teléfono vibra, suelta el botón de encendido y entra al modo de recuperación como se explica aquí. Ahora creo que el error es claro. Estos son los mensajes que aparecen abajo de la consola de recuperación basada en CWM:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Estos errores se muestran cada vez. Por ejemplo, si intento hacer restauración de un backup desde una tarjeta SD externa, escojo el menú "backup and restore", y luego "Backup" y esto es lo que sale:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cómo lo arreglé
Bien, este puede ser solo una manera de arreglar el problema. Descargué muchos archivos de firmware de SamMobile (unos chicos muy organizados, por cierto) pero nada de esto funcionó.
Un muchacho muy generoso subió un backup muy útil del I-8160L que puede ser descargado desde aquí (esta es la URL del hilo del foro). Esta descarga vale la pena, incluso la subscripción al sitio, ya que contiene:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
CSC_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY-CSC-MULTI-UUB_LH1_4G.tar.md5
GT-I8160L_LA_UB_4G.pit
Odin3_v1.84.exe
Odin3.ini
Click to expand...
Click to collapse
¡Sí! Este archivo tiene el archifamoso y archi buscado archivo PIT para el Samsung Galaxy Ace 2 I-8160L. ¡Pero espera! No lo instales todavía. Aunque yo no sea un experto en hacer ROOT ni en los MOD ROM de Android, hice el procedimiento flash de nuevo, utilizando el campo PDA de Odin con el siguiente archivo:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
Click to expand...
Click to collapse
¡Y funcionó! Sin necesidad de usar el archivo PIT.
custom ROM definition?
Hi,
I'm new to Android and semi-experienced at modding in general, I just wanted someone to clarify, what qualifies as a "custom ROM"? I've been picking up info here and there on the forums and as far as I can tell flashing a stock ROM does not increase the counter when flashed using the correct procedure (as I have seen since I'm using a pre-rooted stock), but will flashing something like the "stock lite" ROM increase the counter? Or does these kind of modifications to a ROM not make it custom? As I understand it as long as the kernel remains in its original state any modification to a ROM still qualifies it as a stock ROM, is this information correct?
hi
i have mu galaxy ace 2 simlock i want to unlock it.
please help?
@xenex1
yep, every rom that you flash with odin and have custom kernel.bin in it will increase the counter. so flashing prerooted roms (stock lite included) will not change the counter. also when you have rooted phone, you can flash kernel.bin by dd command through adb or directly from the phone without increasing the counter. so.. you can root the phone, flash (by dd) custom kernel with cwm/twrp recovery and then you're free to install any ROM 'cause flashing through recovery don't increase the counter (even when rom has a custom kernel).
damn, that was long..
@kira95
samsung phones don't have locked boot loaders so there's no need to UNLOCK it.
if you mean ROOT, then there are two options:
- flash prerooted rom through ODIN (doesn't increase the counter),
- flash custom kernel through ODIN (changes the counter and flash status).
and i just wanna say.. HAPPY NEW YEAR TO ALL!!!
5:30 AM, gotta go to bed
@up
Yes, you must be very tired, kira wrote about simlock...
Wysyłane z mojego GT-I8160 za pomocą Tapatalk 2
I have a problem. I edited framework.jar and after I put it in /system/framework/ the phone does not start (it stuck on Samsung Galaxy Ace 2 first screen) and if I close the phone, it reboot itself.
At first, I thought I did something wrong when I edited framework.jar, but then I tried only with framework.jar deodexed (without modification) and the same thing happend.
I tried to put android.policy.jar deodex in /system/framework/ and again the phone is stuck on Samsung Galaxy Ace 2 screen.
What is the problem with deodex files in /system/framework/? In /system/app I have bought deodex and odex files and there is no problem.
I wiped the cache partition and dalvik cache before I flash the update.zip that contains framework.jar (before restart in recovery I deleted framework.odex).
Update: I deodexted all file in /system/framework/ and a flash them in CWM Recovery ( before restart in recovery I deleted all .odex files from framework folder). The result is that the phone restart after the second Samsung screen.
Aflter I reflash odex files, I had to reenter samsung account.
Sorry for my english
don't mix odex files with deodexed ones. use only one 'type'.
@up up
oh, that occured to me also.. when i turned off my pc
simlock:
don't have a clue
@WiCiO_MeDi
Thanks for clarifying, seems i've hit on a problem while flashing a custom kernel though, I tried to use the dd comands in the terminal and all looked well up until the reboot now my device is stuck on the screen that displays the phone and model.
I was using the pre-rooted stock ROM using this method here http://forum.xda-developers.com/showthread.php?t=1881964, which worked fine.
Then I tried to get adventurous and tried to add this kernel to the mix http://forum.xda-developers.com/showthread.php?t=1962100.
Any suggestions for this confused noob?
Sorry nevermind the above, the answer on how to fix the issue was quite simple, just re-flash the original ROM, I must have messed up the recovery mode when installing the kernel.
you mean the bootanimation?
try again 'cause it works for others then it should work for you.
write down all steps that you did, maybe you've mistyped something or just did something wrong
Yeah you're right, I must have done something stupid the first time round, works now though cheers.
Sent from my GT-I8160 using xda app-developers app
Hi everyone, i have one question regarding the fisplay turn off animation. Where are located those files and hiw ti change them?
Sent from my GT-I8160 using xda app-developers app
hello,
my question is : Can i put a om of GT-I8160 in my GT-I8160P or i can brick my mobie phone?
i have the nfc mobile phone can you put here a link of roms to this mobile GT-I8160P.
and finally i want to whrere i can find a post of how do a rom ??
@sersik
Firstly, yes there is always a chance of bricking a phone when flashing any ROM.
As for your NFC enabled device if all goes well it should work fine but you will lose the NFC functionality unless you flash with the proper ROM for that hardware.
You can get your stock ROM from this site if someone has uploaded it (signup is required to download).
And use this threads instructions to build a pre-rooted ROM that doesn't increase the counter.
Hope this helps.
thanks to you xenex1
but if i put a rom of GT-I8160 in my GT-I8160P is the same risk of pu a rom of GT-I8160 in a GT-I8160, no??
and in the roms i say a rom that is created by another person
thanks
Yes the ROM for the GT-I8160 will work on the GT-I8160P but you will lose the NFC function since the GT-I8160 does not have it.
Also yes you can use a ROM that was created by someone else, if it is a pre-rooted ROM then simple flash it using ODIN (counter does not increase) but if it is a custom ROM then flashing with ODIN WILL increase the counter, and in turn you will lose your warranty on the device.
If you want to install a custom ROM without increasing the counter you must first use a pre-rooted stock ROM then install the custom ROM using either CWM, TWRP, Through Terminal or ADB.
OTAVALO said:
Hi everyone, i have one question regarding the fisplay turn off animation. Where are located those files and hiw ti change them?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
They are found inside framework-res.apk. But you have to decompile it first. By the way, why do you want to change it? Do you have the default animation or the CRT animation?
Sent from my GT-I8160 running Holo Bean Beta
I've been having a weird problem lately. After booting up my Ace 2 all my apps force closes, including system apps.
This happened after I installed Suppresed ROM and rebooted. After that I returned to stock ROM rooted with SuperSU, and it happened again. After that I changed to SuperUser and it works fine after a while but if I install some "risky" software, such as BusyBox Installer, it seems to happen again, I made a CWM backup everyday just in case this happened again. It happened to me almost 5 times already.
Just wondering, are any of you having a similiar problem?
Just now I installed Jelly Cream and it won't mount anything on boot and recovery. I hope a quick flash will fix this or Lord help me.. -___-"
uchihakurtz said:
I've been having a weird problem lately. After booting up my Ace 2 all my apps force closes, including system apps.
This happened after I installed Suppresed ROM and rebooted. After that I returned to stock ROM rooted with SuperSU, and it happened again. After that I changed to SuperUser and it works fine after a while but if I install some "risky" software, such as BusyBox Installer, it seems to happen again, I made a CWM backup everyday just in case this happened again. It happened to me almost 5 times already.
Just wondering, are any of you having a similiar problem?
Just now I installed Jelly Cream and it won't mount anything on boot and recovery. I hope a quick flash will fix this or Lord help me.. -___-"
Click to expand...
Click to collapse
the problem is in the firmware i think , so new firmwares doesnt have that problem
Hi there,
I tried following this guide: [HOWTO]/[ROM] [UNOFFCIAL] How to Flash Lineage OS 19.0
However the LineageOs link is broken, so I tried searching by the name and came here: Andy Yan's personal builds // GSI Files
But I'm not sure if this would work or that I would need a special patched version or something.
Would I also need to install Android 12 beforehand?
Thanks in advance!
P.S. If someone can help me out, then I would be happy to write an updated guide!
Just flashed this 5mins ago. My rom was latest samsung. One UI40
A12. Works fine
Works perfectly fine for me too, only problem is that magisk complains about a wrong su version and i can't get rid of it.
Oh, and somehow, google drive won't pick my google account, can't use it somehow, everything else works.
OK..solved those 2 problems. I installed the latest google drive apk from apkmirror. I don't know if it's just a bad version on play store or if the device is identified as whatever and get's the wrong version.
To get rid of the stupid su that doesn't come from magisk, you can adb shell to device, su, and then execute /sytem/bin/phh-securize.sh. It will throw some errors, but remove the stuff and magisk doesn't complain anymore and still works flawlessly.
nEUTRon666 said:
OK..solved those 2 problems. I installed the latest google drive apk from apkmirror. I don't know if it's just a bad version on play store or if the device is identified as whatever and get's the wrong version.
To get rid of the stupid su that doesn't come from magisk, you can adb shell to device, su, and then execute /sytem/bin/phh-securize.sh. It will throw some errors, but remove the stuff and magisk doesn't complain anymore and still works flawlessly.
Click to expand...
Click to collapse
Thanks for the info, finally got magisk to work properly after running phh-securitize!
Hi it's my first time in a forum, sorry for my bad English, but I want to root my A51 with magisk and flash the lineage OS 19 ROM and install twrp on my phone, but I don't know exactly how to do, and which file of lineage OS I have to choose here are they all working for a51 android 12 ??
Hello,
my problem is: I can not install the TWRP-11-3.6.2-a51-20220602-0515.img. The SM-A515F will not boot in to the latest TWRP. Only the version twrp-a51-3.5.0_10-1_ianmacd.tar will be installed an I can enter in to it.
Then I select the image of the Lineagos 19 for this phone to install, and I got this error messages:
Error opening: /data/bootchart (Permission denied), /data/misc (Permission denied) etc ...
@shanman-2
In your signature, you have an SM-A515F with LineageOS 19 and TWRP-11... installed
What has you done, for this installation?
Thanks for your help.
Greenatic said:
Salve è la mia prima volta in un forum, scusate il mio pessimo inglese, ma voglio fare il root del mio A51 con magisk e flashare la ROM di lineage OS 19 e installare twrp sul mio telefono, ma non so esattamente come fare, e quale file del sistema operativo di lignaggio devo scegliere qui funzionano tutti per a51 Android 12?
Click to expand...
Click to collapse
You have to download this (lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img), if you are going to use this guide in the top of this Page (https://forum.xda-developers.com/t/howto-rom-unoffcial-how-to-flash-lineage-os-19-0.4423111/) you wil understand all of it
tiptel170 said:
Hello,
my problem is: I can not install the TWRP-11-3.6.2-a51-20220602-0515.img. The SM-A515F will not boot in to the latest TWRP. Only the version twrp-a51-3.5.0_10-1_ianmacd.tar will be installed an I can enter in to it.
Then I select the image of the Lineagos 19 for this phone to install, and I got this error messages:
Error opening: /data/bootchart (Permission denied), /data/misc (Permission denied) etc ...
@shanman-2
In your signature, you have an SM-A515F with LineageOS 19 and TWRP-11... installed
What has you done, for this installation?
Thanks for your help.
Click to expand...
Click to collapse
So here is the latest update:
Code:
1. Download here this ROM:
https://samfw.com/firmware/SM-A515F/DTM/A515FXXS5FVI2
2. Unpack the zip-files
for ZIP in $(ls *.zip); do yes | unzip $ZIP; done
3. Rename from m5 to tar
for MD5 in $(ls *.md5 |sed -e "s/.md5//"); do mv $MD5.md5 $MD5; done
4. Unpack the tar files
for TAR in $(ls *.tar); do tar -xvf $TAR; done
5. Unpack the lz4 files
LZ4 in $(ls *.lz4); do yes | lz4 $LZ4; done
6. Flashing the img files to the phone
heimdall flash --SUPER super.img --BOOT boot.img --CACHE cache.img --DTBO dtbo.img --METADATA metadata.img --OMR omr.img --PRISM prism.img --RECOVERY recovery.img --USERDATA userdata.img --VBMETA vbmeta.img --VBMETA_SAMSUNG vbmeta_samsung.img
7. Flashing the bin files to the phone
heimdall flash --CM cm.bin --KEYSTORAGE keystorage.bin --RADIO modem.bin --CP_DEBUG modem_debug.bin --BOOTLOADER sboot.bin --UH uh.bin --UP_PARAM up_param.bin
8. Unlock the bootloader in the download mode ( keep pressing together Vol+ and Vol- and conecting to the USB-port of the computer ). And then keep Vol+ for 2 sec. for unlocking.
9. Boot the phone
10. Connect the phone with the USB-cable to the computer
11. Preparing the phone for the devoling mode, and accept all the avsings in the phone.
12. Computer: adb shell
13. a51:/ $ reboot download
14. Use this: TWRP-11-3.6.2-a51-20220602-0515, this will working with the new stockrom
The I made this steps:
Code:
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache
3.3.2. flash disable_dm_verity
3.3.3. flash multidisabler
3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)
3.3.5. reboot recovery
3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
3.3.7. Wipe data
3.3.8. Reboot
This is from: DerTopher
Source:
[link] https://forum.xda-developers.com/t/howto-rom-unoffcial-how-to-flash-lineage-os-19-0.4423111/ [/link]
Than I will boot the LOS 19.1, but there is no booting up, only start - restart - start etc....
Only I can enter in to the TWRP.
Is there an solution? I made an "heimdall print-pit" but this not work.
Thank you for the support...
How to change quantity of slots in home to 3 slots ?
Update 01/29/2023:
Whit this version of the android it will function well.
You have to download this version: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
This step is verry importand!
Code:
3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
The correct form:
Code:
3.3.6.1 rename lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img in to system.img and keep it in the same folder likes the chondone zip-file!
3.3.6.2 Then flash the chondone zip-file, and don't worry about the error massege "can not find the /oem ..."
Thanks for the help and the support for me Hy gays - this an grate jop - keep doing.
The Samsung Android Version 12 is on this phone slow, and has a lot of bolt apps inside.
A115m R kernel v1.3
Qualcomm SDM450 Snapdragon 450
For Android 11 OneUI 3.1
Thanks to @ for module loading fix
bugs:
?
Installation
Post 2
Kernel source code
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
Installing physwizz custom kernels
INSTALL AT YOUR OWN RISK
I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES
But I will help any well-mannered person to recover.
Note: physwizz kernels work best with debloated stock or with wizzROM
Other custom ROMs may not be supported
A. Preparation
1. Root the phone
2. Compress your patched boot.img to make boot.tar
3. Copy boot.tar to PC
B. Installation
Method 1
Install from twrp
Reboot to recovery
Backup boot and dtbo (if available)
Install kernel zip
Wipe both caches
Reboot
Method 2
Install kernel from terminal.
1. Download magisk module (magic flash zip) https://github.com/Magisk-Modules-Alt-Repo/magic-flash
2. Install module and reboot.
3. Open terminal.
4. Navigate to folder containing kernel zip.
Use
ls to list contents
and
cd to change directories
5. Type su
6. Type flash kernel zip
7. Reboot
Method 3
Using ADB
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload filename.zip
Method 4
Using boot.img
Install AIK Mobile from magisk modules https://t.me/physwizz2/82
Use rootexplorer to access
/data/local/AIK-MOBILE
Add patched boot.img and tap unpackimg.sh
Exit the folder and return to see the files.
Edit the files (eg to add a new Image
rename Image to boot.img-zImage and insert in split-image folder)
Tap repackimg.sh
Rename new_image.img to boot.img
Compress boot.img to boot.tar
Copy boot.tar to PC
Reboot phone to download mode
Install boot.tar from odin
C. Removal
Method 1
Reboot to recovery
Restore boot and dtbo
Reboot
Method 2.
Reboot phone to download mode
Install patched boot.tar from odin
@physwizz
So far 16 people have downloaded the file.
Any feedback?
Hi, mate. Is this kernel compatible with LineageOS GSI ROM? I'm using A115F as a test phone for experiments but I can't seem to find an appropriate kernel for my device. Somehow, samsung's stock kernel won't cooperate with LOS GSI causing File Transfer (MTP) and others features to fail. That's it, thanks.
Alright, just tested it out and I found some issues.
Here's the list of what I found so far.
1. WiFi not working
2. Bluetooth not working
3. SIM Card fails to get signal (sometimes it works)
4. MTP still not working (I hope someone fix this issue)
I'm using LOS GSI a64 image. Samsung A115F (Galaxy A11) Snapdragon 450
I'll update this list, if I found a new one.
jcatrdev said:
Alright, just tested it out and I found some issues.
Here's the list of what I found so far.
1. WiFi not working
2. Bluetooth not working
3. SIM Card fails to get signal (sometimes it works)
4. MTP still not working (I hope someone fix this issue)
I'm using LOS GSI a64 image. Samsung A115F (Galaxy A11) Snapdragon 450
I'll update this list, if I found a new one.
Click to expand...
Click to collapse
Ok
does it come with root?
My model a115m its work for me ?
physwizz said:
OK
Click to expand...
Click to collapse
jcatrdev said:
Tudo bem, acabei de testar e encontrei alguns problemas.
Aqui está a lista do que encontrei até agora.
1. Wi-Fi não funciona
2. Bluetooth não funciona
3. O cartão SIM não recebe sinal (às vezes funciona)
4. O MTP ainda não está funcionando (espero que alguém corrija esse problema)
Estou usando a imagem LOS GSI a64. Samsung A115F (Galaxy A11) Snapdragon 450
Vou atualizar esta lista, se eu encontrar uma nova.
Click to expand...
Click to collapse
if you don't mind, could you help me to install LOS GSI a64?? I've been stuck in stock for a long time
swamp66 said:
if you don't mind, could you help me to install LOS GSI a64?? I've been stuck in stock for a long time
Click to expand...
Click to collapse
Download Android 11 GSI (arm64 ab) with GApps
1. Unzip img file
2.Wipe data and system from TWRP recovery
3. Install system.img into system partition
4. Install my kernel
5. Reboot
i tested in stock and a lot didn't work here :
camera, flashlight, wifi, games make the phone restart, I only tested cod mobile
unfortunately if it is not resolved this makes the use unfeasible
Obs: but thanks to the developer for making stuff for the a115m, currently there is very little about this device
swamp66 said:
i tested in stock and a lot didn't work here :
camera, flashlight, wifi, games make the phone restart, I only tested cod mobile
unfortunately if it is not resolved this makes the use unfeasible
Obs: but thanks to the developer for making stuff for the a115m, currently there is very little about this device
Click to expand...
Click to collapse
Thanks for feedback.
I'll look at it.
I don't own this device
Hello, mate, do you know any way to enter ADB sideload mode on the Galaxy A11? I have the Android 12 firmware installed. Thank you in advance!
raidenmania02 said:
Hello, mate, do you know any way to enter ADB sideload mode on the Galaxy A11? I have the Android 12 firmware installed. Thank you in advance!
Click to expand...
Click to collapse
Using ADB
Install adb tools on pc
Connect phone to PC in normal mode
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload filename.zip
Can I sideload a GSI?
raidenmania02 said:
Can I sideload a GSI?
Click to expand...
Click to collapse
I haven't tried
Use TWRP
Is this work for Sm-a115f/ds , its verry lagged and if someone called me there are a black screen and i can't do anything. Can anyone help me please ??
Muhamad fawaz said:
Is this work for Sm-a115f/ds , its verry lagged and if someone called me there are a black screen and i can't do anything. Can anyone help me please ??
Click to expand...
Click to collapse
Reinstall your stock firmware