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
Related
So you got a galaxy s7 with this on it* failed to mount /efs or worse like mine efs and dm verity verification failed. First let me just say I spent* week's on my pc trying to fix this! I was throwing all kinds of **** at it and I got something to stickfollow my steps to get that sexy paperweight working again*
1.First phone off remove sd card use a different one if u only have one format and use* I no you seen this a million times lol don't hate me for it. Download stock firmware I used Odin when you get to recovery with the failed efs *at the bottom click reboot and let it sit for a min or 2 now put it back in download mode*
2.download twpr*and flash it once your in recovery click wipe now click format data and type yes DO NOT reboot click the home icon then click reboot now click recovery
3.google search no-verity-opt-encrypt-5.1 and download it should be the second one says android file host now search for SR3-SuperSU-v2.79 and download after you have the 2 files copy to phone make sure your mounted in recovery now install the first one then click home icon now click install and install* super su and click home icon again* click reboot and click recovery
4.Now that your phone is back in recovery we need to use adb* if you can't for any reason you can use the terminal on twpr* type .....
mke2fs /dev/block/sda3
mount -w -t ext4 /dev/block/sda3
reboot
5.So now you should have a new problem on the phone the screen says something about drk go to https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Follow guide A
6.Now that you flashed your firmware your phone should be up and running again your not done plz listen do not restart your phone go straight to settings and enable developer setting and make sure oem and usb debugging is clicked
I hope this helps* and also thanks to the person or persons who made the drk deal on xda and person or persons for su and who ever made the no verity app
twrp and other 2 zips can be found here.
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
munchy_cool said:
twrp and other 2 zips can be found here.
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
FRP lock On
FACTORY BINARY BLOCK by FRP
saya sudah flashing dengan frimware dari sammobile
tapi frp masih ON
kondisi device bootlop
and E:failed to mount /efs (Invalid argument)
@davide62 did you have frp lock on or off before attempting this method? i'm having the same issue :/
syntenza said:
@davide62 did you have frp lock on or off before attempting this method? i'm having the same issue :/
Click to expand...
Click to collapse
Mine was off
agieljk said:
FRP lock On
FACTORY BINARY BLOCK by FRP
saya sudah flashing dengan frimware dari sammobile
tapi frp masih ON
kondisi device bootlop
and E:failed to mount /efs (Invalid argument)
Click to expand...
Click to collapse
ambil stock firmware nya di-flash lagi sekali. Cuba root ikoti cara di xda ni. Mungkin ada satu dua langkah kamu salah. Mas lain kali tulis dalam bahasa inggeris. (Translation: take the stock firmware flash it all over again and re-root according to the steps found in xda, there is one or two steps you did make a mistake. Please do write in english)
Rooting And TWRP for Samsung J2 Prime SM-G5325
By: Aldous M.C
https://forum.xda-developers.com/member.php?u=7506444
warning: not for noobs who dont know anything about odin/flashing/rooting
I found this in 4pda.ru forums i could not really understand even the page was translated from russian to english. though i figured out how they did this
The concept was to create a odin package with a patched boot.image of samsung a3 with twrp recovery.img inside odin package then flashing it thru odin and after that flashing back the stock boot.img of Samsung J2 Prime then booting directly to recovery to flash SuperSU to patch the Stock Boot.img to make TWRP stick and not be replaced by stock recovery or giving a SEAndroid enforing error when booting to TWRP
So this is how you do it. First you need A full official firmware of Samsung SM-G532G (J2 Prime) Odin, and a Tar-Tool to convert boot.img from firmware to a odin package
WHAT YOU NEED (download links below)
1. Download latest firmware for J2 prime
2. Open Firmware file open the AP file, inside you will see folders and the boot.img. extract the boot image by draging it out from the AP file
3. Download tar-tool and extract folder to deskop or anywhere then Place boot.img inside TAR-Tool
4. then run the ImgToTar.MD5.bat file and you will see a boot.tar.md5 file appear. (do not rename it to anything else odin will not recognize this as boot.img and will not flash)
5. Now you have a Odin flashable boot.img from your original firmware. place it somewhere you can easily access we will use it later.
FLASHING THE TWRP
1. on your phone go to developer options and enable usb debbuging and toggle oem unlock to ON
2. power of your phone
3. Open odin on pc and click AP then select/browse the A3 boot img+TWRP odin package select it.
4. then go to options tab uncheck the auto reboot and do not check anything else just the auto-reboot
5. Open your phone to ODIN mode Press and hold home key + Volume down then power
6.Plug in your phone to your pc and press volume up to continue download
7. in PC start the download in Odin if it says pass go to next step
8. at this point you cannot power off the device all you have to do is remove the battery and put it back in BUT DO NOT TURN IT ON YET!
9. Go to ODIN mode again on your phone and the flash the stock boot.img you created with the TAR-Tool (REMEMBER TO ALWAYS UNCHECK AUTO-REBOOT in Odin so you will not end up with a reboot after a succesful flash. again you cannot turn off the phone, just pull the battery and put it back in. Do not turn it on yet dont boot it else your TWRP recovery will be replaced by stock or put you in a boot loop
10. Now Go to Recovery mode, while phone is powered off Press and hold home key + volume up + power key.
11, Tadaa, you have your TWRP recovery booted, now you can flash SUPERSU (use flashable SuperSU 2.79 or latest)
[almost forgot before doing all this place the SuperSU flashable zip on both storages internal and sdcard]
12. now the stock boot.image is patched by SuperSU and it will now hold the TWRP even after reboot.
13. Your done turn your phone on and you have a rooted Samsung J2 Prime.
DOWNLOADS
https://yadi.sk/d/zsYDiUSk3FJHPX - A3+TWRP odin package
https://forum.xda-developers.com/showthread.php?t=2446269 - TAR-Tool
https://drive.google.com/uc?id=0B4fZWSYgVIIOR2kxSVBsYTdmWFE - SAMSUNG J2 Prime FIRMWARE (SM-G532G) you can also find other sources with updated firmwares for your region.
BIG thanks to:
Mk.Mourad for the Tar-Tool script
A Russian comrade JacobN of 4pda,ru forum for the A3+twrp odin package
i am not responsible for anything that happens to your phone while doing this. tested by me and will work if you follow carefully all procedures.
Aldous M.C
twrp keep read only ....
thanks it's worked
but my phone stuck on bootloop samsung logo......it won't start up .......
e : failed to mount / efs (invalid argument )
e : failed to mount / efs (invalid argument )
e : failed to mount / efs (invalid argument )
dm-variety failed...........
how to fix it ...
please help me
thanks
thanks for this. my phone's AP is G532GDXU1AQC1 will this work?. BL is G532GDXU1AQC1 and CP is G532GDXU1AQA3. thank yo:good:u!. i've been waiting for someone speaking in english to make a root for j2 prime. it seems that the forum in 4pda only supports g532f variant of j2 prime.
room4two said:
thanks for this. my phone's AP is G532GDXU1AQC1 will this work?. BL is G532GDXU1AQC1 and CP is G532GDXU1AQA3. thank yo:good:u!. i've been waiting for someone speaking in english to make a root for j2 prime. it seems that the forum in 4pda only supports g532f variant of j2 prime.
Click to expand...
Click to collapse
i am already rooted. thanks for this method!. no problems at all
Can I use this with Baseband version AQA3 and Build number AQC1 ?
does this work on dual sim version? SM-G532G/DS?
and if by chance, you could post pictures
thanks!
chalermla said:
Can I use this with Baseband version AQA3 and Build number AQC1 ?
Click to expand...
Click to collapse
ive tried this and it worked for aqa3 aqc1
room4two said:
ive tried this and it worked for aqa3 aqc1
Click to expand...
Click to collapse
Is your phone also the dual-sim version? Thanks anyway, :good::good:
thanks bro, this method is done, sorry my english
Phone: samsung j2 prime (SM-G532M)
Pais: Bolivia
Empresa: VIVA
Compilacion: MMB29T.G532MUMU1AQD2
Para los de habla hispana remarco lo importante en el procedimiento desmarcar en odin el reseteo automatico y no tocar nada mas
para salir del menu download quiten la bateria y la colocan de nuevo, por nada del mundo prendan el telefono hasta realizar todo el procedimiento
resumen:
1.- entrar al menu download y flashear con odin el A3_boot_twrp_recovery.tar.md5. Quitar bateria y volver a colocarla
2.- entrar al menu donwload y flashear con odin boot.tar.md5 creado por ustedes en base del original. Quitar bateria y volver a colocarla
3.- entrar al menu de twrp con vol+,menu,power e instalar super su (SuperSU-v2.82-201705271822.zip)
4.- encender normalmente y vuala root 100%
Thanks
OHHHHH WAOOOOW.....
THANKS a Lot Man....You Are Great.....
Finally, I have found for which i was searching since i bought my j2 prime....
Finally,i have Rooted the latest firmware of my Grand Prime+/j2 prime g532f available on Samsung website...Now I have TWRP and Have installed Xposed....Now I Can Download Direct Files Into SD Card From Uc Browser and have full access to sd card....
I Can Instal Large Games In SD Card.....
Wow I am very Happy and Satisfied with my Mobile now....
help me
hey help me plz, give me ur official boot.img and recovery.img my galaxy j2 prime is bootloop
ajireza said:
hey help me plz, give me ur official boot.img and recovery.img my galaxy j2 prime is bootloop
Click to expand...
Click to collapse
Flash a stock firmware...it will be okay...
Procedure continues to apply Magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Following the procedure given in the first post, Magisk can also be installed. I'll continue with a new step 10:
10) If you followed the original thread and installed SuperSU, you'll need to uninstall it in order to proceed. Unroot your phone using this unSU script. If you haven't yet, ignore this.
11) To install latest Magisk, DOWNLOAD the following:
Latest Magisk
Latest Magisk Manager
(Verify you're downloading the latest versions in this thread here.)
Place these downloads in your SD Card and also extract the stock boot.img from your firmware AP file, as described before. We'll need it.
12) Now press and hold Vol Up + Home + Power will boot usa into TWRP. Now we need to first install the stock boot.img. This is done because Magisk installer will complain if it detects this patched boot.img we used in earlier steps to boot TWRP and thus fail. Installing the stock boot.img will let us install Magisk successfully. SO in TWRP, go to Install / Install Image and browse to the boot.img file; then select "Select Partition to Flash Image: Boot" and flash it.
13) Go back to TWRP home and proceed to install Magisk Zip file. The installer should end without any errors.
14) Reboot your Samsung to system, and you can now install Magisk Manager (allow unknown sources, you know this already). Once done, open it. You'll be greeted with beautifil green ticks :good:
TWRP will still be there when you need it.
ENJOY!!!!
Thanks to a lot to @4ld0u5 for the original thread.
Hello, I'm helping a friend root his/her SM-G532G/DS
Is this method will work for the stock rom mentioned below (link) or is this stock rom legit for SM-G532G/ds ?
thank you very much.
http://updato.com/firmware-archive-select-model?record=10D3009C4CAA11E7963AFA163EE8F90B
metafaniel said:
Following the procedure given in the first post, Magisk can also be installed. I'll continue with a new step 10:
10) If you followed the original thread and installed SuperSU, you'll need to uninstall it in order to proceed. Unroot your phone using this unSU script. If you haven't yet, ignore this.
11) To install latest Magisk, DOWNLOAD the following:
Latest Magisk
Latest Magisk Manager
(Verify you're downloading the latest versions in this thread here.)
Place these downloads in your SD Card and also extract the stock boot.img from your firmware AP file, as described before. We'll need it.
12) Now press and hold Vol Up + Home + Power will boot usa into TWRP. Now we need to first install the stock boot.img. This is done because Magisk installer will complain if it detects this patched boot.img we used in earlier steps to boot TWRP and thus fail. Installing the stock boot.img will let us install Magisk successfully. SO in TWRP, go to Install / Install Image and browse to the boot.img file; then select "Select Partition to Flash Image: Boot" and flash it.
13) Go back to TWRP home and proceed to install Magisk Zip file. The installer should end without any errors.
14) Reboot your Samsung to system, and you can now install Magisk Manager (allow unknown sources, you know this already). Once done, open it. You'll be greeted with beautifil green ticks :good:
TWRP will still be there when you need it.
ENJOY!!!!
Thanks to a lot to @4ld0u5 for the original thread.
Click to expand...
Click to collapse
Thanks
Can you upload stock boot.img for j2 prime g532f ....i am waiting...i have no computer.... ??
I'm sorry. I couldn't understand this part..
2. Open Firmware file open the AP file, inside you will see folders and the boot.img. extract the boot image by draging it out from the AP file
Please assist. TQ..
i already followed step by step . but after i reboot i need to enter password that i don't know i had. please help me asap
i have the problem with my twrp . are u already solve the problem u faced?
pheak28 said:
thanks it's worked
but my phone stuck on bootloop samsung logo......it won't start up .......
e : failed to mount / efs (invalid argument )
e : failed to mount / efs (invalid argument )
e : failed to mount / efs (invalid argument )
dm-variety failed...........
how to fix it ...
please help me
thanks
Click to expand...
Click to collapse
I have the same problem with my twrp too sir . just like yours. can anyone help me?
Hello brother. Im already rooted with SuperSU. I want to try Magiisk. Is it okay if I flash my J2 Prime with the stock rom and then root it directly using Magisk?
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error message.
To flash a ROM on Android devices with Dynamic Partition Layout you have to flash it by means of fastbootd
Code:
fastboot devices
fastboot reboot fastboot
fastboot flash <PARTITION> <FILENAME>.
Look also inside here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
jwoegerbauer said:
To flash a ROM on Android devices with Dynamic Partition Layout you have to flash it by means of fastbootd
Code:
fastboot devices
fastboot reboot fastboot
fastboot flash <PARTITION> <FILENAME>.
Look also inside here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
I forgot to tell, I don't have Fastboot (I think), cause I have a Samsung device. It could work on TWRP Fastboot mode?
IDK. Never used TWRP. And I never owned a Samsung phone.
ferreraiury05 said:
Tengo muchas ganas de instalar GSI, pero cuando iba a flashear vi que mi dispositivo "no tiene la partición del sistema". Allí se llama Super Partition. ¿Alguien sabe cómo puedo instalarlo? Probé algunos tutoriales en video, pero siempre aparece un mensaje de error.
Click to expand...
Click to collapse
hello, first flash stock then enter fastbootd mode and put. fastboot erase system and then give fastboot flash system and the name of your gsi. If you get a space error put this command fastboot delete-logical-partition product_a you give enter and re-enter the command fastboot system and name of your gsi and voila it will be installed
I am new to linux (as expected) and tried installing Kali NetHunter on my android device [One Plus 6]. I was successful in installing with Android 8 but my phone keeps bricking when attempted with Android 9/10. I referred to these instructions and followed these steps:
I am looking for help and also any explanations for my understanding of the process is also appreciated very much!
1) Start developer mode, enable oem unlocking and usb debugging, and restart in fastboot mode > then from Powershell: fastboot oem unlock
Phone gets wiped so again start developer mode, usb debugging.
2) Now I download the twrp .img and zip files, also the Magisk.apk from github then rename the apk to .zip (as instructed in their documentation). Finally move these files to the internal storage of the phone.
3) Restart phone in Fastboot mode > from Powershell: fastboot boot twrp-3.x.x-x-enchilada.img (version according to android 8 or 10 respectively)
4) Now that I am temporary booted into twrp I install the twrp .zip file from here and reboot into recovery mode (TWRP that was installed).
Now I flash install the Magisk.zip and reboot the OS > Install the magisk.apk that shows up.
Following the kali nethunter documentation linked above no extra steps are needed for android 8. So I just install the Nethunter zip from Magisk app (click the modules [puzzle piece] icon and select nethunter zip). This works perfectly!!! Ps: if i flash nethunter from TWRP it says successful but bricks the phone and doesn't reboot. Don't know why but if you do please let me know or hint what i should look into to understand better.
****[NEED HELP HERE]****
FOR ANDROID 10: The Kali documentation says for disabling encryption we need to first flash Universal DM-Verity, ForceEncrypt Disabler. So I download the zip and move it to internal storage, from what I understand for my requirement I do not need to change anything in file naming. If I flash this zip using Magisk or TWRP the result is just a bricked phone that gets stuck on "The bootloader is unlocked" warning message.
If I skip this step then it bricks if I flash nethunter through TWRP and if I flash as a module using Magisk then it works fine.
According to nethunter documentation without the Universal DM-Verity, SSH capabilites should not work but on my phone it works just fine if I open the NetHunter app > Kali services > SSH (don't know an extensive way to test this or if any other functionality has been compromised without the ForceEncrypt Disabler). Am I understanding this part wrong? or in my case I do not need to flash Universal DM-Verity, ForceEncrypt Disabler? This step is what confuses me and I have tried countless times via different ways over the past summer.
The Kernel is shows is 4.9.179-perf+ with Android 10.
The reason i wanted to update to Android 10 from 8 is because I am having compatibility issues with RTL8814AU and none of the drivers I find seem to work (Android 8 kernel is 4.9.65-perf+).
Thank you for your time to read and respond!
Friend when you install magisk and disable verity and turn on your phone install the magisk app and checker root then give the necessary permissions and start the recovery mode in twrp and then install install the nethunter ZIP again what happens to me it worked like this
Amigo cuando instales magisk y disable verity y encienda tu teléfono instala la app de magisk y checker root luego da los permisos necesarios e inicia el modo recovery en twrp y luego instala instala el ZIP de nethunter de nuevo haber que pasa a mi me funcionó así
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.