Related
I'm having an issue while trying to install CM10.2 (new 4.3 build)
I went into TWRP 2.6.0.0 with the ROMs on an external SD, and wiped everything. (I wanted a really clean install, didn't know I'd make it this hard on me)
I tried to install 10.2, but it would just give me the same error "Error executing updater binary in zip cm-10.2-20130730-UNOFFICIAL-tf700t.zip"
I went back and did a factory reset, then installed 10.1 nightly ROM and 4.2.2 Gapps. The Tablet started up fine and got to the setup screen.
Without starting into the setup, I powered down and started up in recovery mode again.
This time I installed 10.2 ROM and the 4.3 Gapps.
This time, it gets to the setup screen, but I get the "Unfortunately, Settings has stopped" and can't get past the Welcome screen.
I went back again, and installed 10.1 and gapps, then went through setup, updated google apps, restarted, the reboot into recovery.
I installed 10.2 and new gapps again. Everything starts up
EXCEPT:
I can't access Settings or DSP Manager. They both crash on startup and can't be accessed after that.
Went back and wiped everything, started over with Stable 10.1.2. It installed fine.
Set up and installed SuperSU and set binaries, then installed goomanager
loaded up 10.2 and gapps in goo and flashed. Flash would fail with same error as above.
What I tried
wipe everything in TWRP:
Install SuperSU
Factory Reset in Wipe Data
Flash ROM and Gapps
Wipe Cache and Dalvik
Reboot
Set Up Profile
Uncheck to recover from your google account (this will save you from having everything installed)
Update the google apps in play store
Install SuperSU
Grant SuperSU SU privaleges
Run SuperSU and update binaries through TWRP/CWM
(Reboots)
Install GooManager and Grant SU privaleges
From here, I should be able to flash 10.2 and associated new Gapps, but when it restarts into TWRP to install, it fails because of the same error. When I go to reboot from TWRP, it tells me that it appears I do not have root access and asks if I want to install SuperSU.
I install CWM to install a new recovery script instead of TWRP.
I get the exact same scenario.
Then I go and reinstall 10.1.2 and 4.2.2 gapps and everything seems to be fine.
I also cannot install any of the nightly ROMs dirty.
Did I lose root access in recovery?
If I'm in the OS, and go to CWM ROM manager and select "Boot Into Recovery" it essentially just restarts. It never goes to recovery.
I downloaded the Touch Recovery file and when it was done, selected it to install from top left, and it says "Unfortunately, the process android.process.media has stopped"
wtf is going on?
Do this:
– Reboot Recovery (TWRP 2.6)
– If TWRP promt the SuperSU installation, install it.
– Boot into Android.
– Reboot Recovery
– Flash CM 10.1 and Gapps
– Boot into Android
– Don't install SuperSU, superuser it's already merged in CM.
– Reboot Recovery
– Flash CM10.2 like an update (In TWRP /install/select the zip files, ROM and Gapps/wipe cache and dalvik/reboot system
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4 Beta
Hi again mate, if i were you i would try to install a full Asus rom and Wipe everything and i mean a complete Wipe, including data/media (you will use all your data stored on the internal memory).
1) Dowload the latest Asus firmware from Asus site
2) Unpack the zip file, the result will be another ZIP file (this is the file you need to flash)
3) Push the file on a MicroSD
4) Boot in recovery and install the firmware from the MicroSD
5) Reboot your device (at this point you will see a blu bar filling slowly)
6) Wait untill the blu bar is full and when the tablet will reboot press Volume Down so you will go into the bootloader menu
7) Select the WIPE icon (this will erase all your data so be sure you made a backup)
8) After the wipe process is done your device should boot in Android just fine
Now you can install TWRP via fastboot mode, make a nandroid backup of your clean Asus rom and then proceed with the CM 10.2 and GAPPS install , it should work at 99%.
Edit: And btw you don't have to install SU, Rom Manager, Goo Manager or stuff like that, CM builds are already rooted and ready to go.
soyusado said:
Do this:
– Reboot Recovery (TWRP 2.6)
– If TWRP promt the SuperSU installation, install it.
– Boot into Android.
– Reboot Recovery
– Flash CM 10.1 and Gapps
– Boot into Android
– Don't install SuperSU, superuser it's already merged in CM.
– Reboot Recovery
– Flash CM10.2 like an update (In TWRP /install/select the zip files, ROM and Gapps/wipe cache and dalvik/reboot system
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Followed it exactly, and when I get to the point of installing 10.2, it gives me the same error as when we talked in the other thread using TWRP (this is now using CWM):
set_perm: some changes failed
E:Error in /sdcard/cm10.2-20130730-UNOFFICIAL-tf700t.zip
(Status 7)
Installation aborted.
It doesn't make sense to me that I can install the stable builds, but not the 10.2 or nightly builds.
I'm going to try Pretoriano80's method now. I think it's deeper than just the ROM or Recovery script.
Pretoriano80 said:
Hi again mate, if i were you i would try to install a full Asus rom and Wipe everything and i mean a complete Wipe, including data/media (you will use all your data stored on the internal memory).
1) Dowload the latest Asus firmware from Asus site
2) Unpack the zip file, the result will be another ZIP file (this is the file you need to flash)
3) Push the file on a MicroSD
4) Boot in recovery and install the firmware from the MicroSD
5) Reboot your device (at this point you will see a blu bar filling slowly)
6) Wait untill the blu bar is full and when the tablet will reboot press Volume Down so you will go into the bootloader menu
7) Select the WIPE icon (this will erase all your data so be sure you made a backup)
8) After the wipe process is done your device should boot in Android just fine
Now you can install TWRP via fastboot mode, make a nandroid backup of your clean Asus rom and then proceed with the CM 10.2 and GAPPS install , it should work at 99%.
Edit: And btw you don't have to install SU, Rom Manager, Goo Manager or stuff like that, CM builds are already rooted and ready to go.
Click to expand...
Click to collapse
While trying to flash the file, I get this error:
assert failed: package_extract_file("blob", "/tmp/blob")
E:Error in /sdcard/US_epad-user-10.6.1.14.8.zip
(Status 7)
Installation aborted.
sigh
No problems while wiping everything and installing 10.1 stable and gapps, but I can't install 10.2, nightlies, and the asus firmware
As a test, I installed Stable 10.1.0 and gapps, then set up google and it immediately notified me of updates, and I downloaded 10.1.2 and then selected upgrade. It reboot into recovery fine, and installed the file just fine.
I just can't move to 10.2.
A note: When I first unlocked and rooted the tablet, I went straight to 10.1. Ever since then, I've been installing nightly builds as dirty flashes. This is the first time I've done a clean wipe of everything.
I'm wondering if I've lost some root access.
I've tried to connect it to adb. I have the drivers, the PC recognizes it as a TF700 and I can transfer files fine. If I try to connect to the device, it just stays hanging at the "adb wait-for-device" step.
JoJoDaClown said:
While trying to flash the file, I get this error:
assert failed: package_extract_file("blob", "/tmp/blob")
E:Error in /sdcard/US_epad-user-10.6.1.14.8.zip
(Status 7)
Installation aborted.
sigh
Click to expand...
Click to collapse
you are trying to flash from the internal storage or MicroSd?
Edit: Btw, which recovery you are using?
Edit 2: It makes no sense being able to install just CM 10.1 stable and no other rom, something is wrong there. Asus full rom use the staging partition to install but the recovery is failing for some reason.
Maybe you could flash the TWRP 2.5.0.0 via fastboot and try again a full wipe.
---------- Post added at 07:03 PM ---------- Previous post was at 06:43 PM ----------
Are you able to get fastboot up and running? Maybe adb doesn't work because you didn't enabled ADB debugging in Setting/Developer options
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I could also provide you the Stock Recovery for the latest Asus firmware, i'm sure that using the stock recovery you will be able to fix the issues you have. But you will have to flash it via Fastboot.
Pretoriano80 said:
you are trying to flash from the internal storage or MicroSd?
Edit: Btw, which recovery you are using?
Edit 2: It makes no sense being able to install just CM 10.1 stable and no other rom, something is wrong there. Asus full rom use the staging partition to install but the recovery is failing for some reason.
Maybe you could flash the TWRP 2.5.0.0 via fastboot and try again a full wipe.
---------- Post added at 07:03 PM ---------- Previous post was at 06:43 PM ----------
Are you able to get fastboot up and running? Maybe adb doesn't work because you didn't enabled ADB debugging in Setting/Developer options
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I could also provide you the Stock Recovery for the latest Asus firmware, i'm sure that using the stock recovery you will be able to fix the issues you have. But you will have to flash it via Fastboot.
Click to expand...
Click to collapse
I'm currently installing from microSD, although I've tried internal "sdcard" as well.
I'm now using CWM 6.x (whatever the latest is), but had been using TWRP 2.6.0.0
Your Edit2: The point of my confusion and headache.
I haven't been able to get adb up and running, it doesn't find my device. My PC interacts with the device. I've enabled developer options and enable "Android Debugging" as CM calls it.
JoJoDaClown said:
I'm currently installing from microSD, although I've tried internal "sdcard" as well.
I'm now using CWM 6.x (whatever the latest is), but had been using TWRP 2.6.0.0
Your Edit2: The point of my confusion and headache.
I haven't been able to get adb up and running, it doesn't find my device. My PC interacts with the device. I've enabled developer options and enable "Android Debugging" as CM calls it.
Click to expand...
Click to collapse
So from the MicroSD the install proccess of the full Asus firmware is working?Anyway just in case it doesn't work i've prepared a Stock Recovery blob (see attachement) for you,but it must be flashed via Fastboot.
Steps to flash:
1) Download the attachement and unzip the file ,the extracted file will be " recovery.blob "
2) Move the recovery.blob in the same folder where fastboot.exe is located ( this is valid for a Windows OS)
3) Boot your tablet in Fastboot mode (Press Volume Down + Power until you get to the Menu with the 3 icon.Don't select any icons because once you get there the device will enable the fastboot mode by default)r
4) Now open a Command Prompt from the folder where fastboot.exe is located and type the following command
Code:
fastboot flash recovery recovery.blob
5) If everything went good you will see a blu bar ,this means your Stock recovery was installed so you can reboot with this command
Code:
fastboot reboot
If nothing else works try the above and let me know.
Pretoriano80 said:
So from the MicroSD the install proccess of the full Asus firmware is working?Anyway just in case it doesn't work i've prepared a Stock Recovery blob (see attachement) for you,but it must be flashed via Fastboot.
Steps to flash:
1) Download the attachement and unzip the file ,the extracted file will be " recovery.blob "
2) Move the recovery.blob in the same folder where fastboot.exe is located ( this is valid for a Windows OS)
3) Boot your tablet in Fastboot mode (Press Volume Down + Power until you get to the Menu with the 3 icon.Don't select any icons because once you get there the device will enable the fastboot mode by default)r
4) Now open a Command Prompt from the folder where fastboot.exe is located and type the following command
Code:
fastboot flash recovery recovery.blob
5) If everything went good you will see a blu bar ,this means your Stock recovery was installed so you can reboot with this command
Code:
fastboot reboot
If nothing else works try the above and let me know.
Click to expand...
Click to collapse
I'll see if I can get to that this week. I have to fly out for work, so I'll have to load adb on the laptop.
Funny, the 20130808 CM10.2 update installed just fine.
JoJoDaClown said:
Funny, the 20130808 CM10.2 update installed just fine.
Click to expand...
Click to collapse
Well,i don't know why this build works and the previous one don't,but i'm glad you made it this time.
Hello,
As I also have the message assert failed : package_extract_file ("blob, "/tmp/blob") I used the recovery blob provided by Pretoriano80. I got the blue bar, I reboot with the command and since, my TF201 displays on loop the Asus logo and the message up above on the left "The device is Unlocked". It's blocked. Any help please?
When I try to reinstall, I got this :
C:\nvflash1>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787be201812
[-] Incorrect BLOB selected. nverror: 0x4.
Yet, it's my blob.bin
J'ai trouvé un autre blob.bin sur mon PC issu de ma sauvegarde. Je ne sais pas trop quel blob.bin j'utilisais avant...En l'utilisant, j'ai eu une autre erreur :
[-] Error 3 receiving response from command
J'ai suivi la recommandation de jim.g87 qui indique de télécharger un autre nvflash
https://forum.xda-developers.com/showth ... ?t=2457624
et effectivement, ça a débloqué la situation.
J'ai enfin pu lancer la commande et suivre la procédure de vanquische
https://forum.xda-developers.com/showth ... 507&page=2
Ma tablette refonctionne, avec la ROM d'origine.
You were able to get into the tablet once, it got you to the tablet's setup screen correct? - NP
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?
[ROOT] Galaxy J810x Methods Magisk And Twrp
[ROOT Normaly]
1. Download Stock ROM 9.x or upgrade normaly
2. Start your ROM enter configuration, developer options and set Unlock by OEM
3. Download Odin 3.14 and drivers
4. Download Magisk and TWRP 3.3.0 and no-verity-opt-encrypt-6.1.zip
5. Install drivers for J7
6. Copy Magisk and no-verity-opt-encrypt-6.1.zip to SD Card
7. Enter in Stock Recovery and Factory reset
[Download MODE]
8. After this enter in download mode imediatly or your system encrypt
9. no start your stock rom or your system encrypt
10. Open Odin 3.14 flash Stock Bootloader and Modem Only If necessary
11. Flash TWRP with Odin or upgrade via img
12. Reboot imediatly in Recovery
13. Flash Magisk 20
14. Flash no-verity-opt-encrypt-6.1.zip
15. iNTALL your prefered Custom ROM
16. Install Magisk Manager 7.5
17. Press Thanks please
18. in this moment install Havoc or Lineage 17.1
[mAgisk mEthod]
You will need the stock Rom files from Sammobile for your phone model(BL, AP, CP, HOME CSC) and Odin on your PC.
1. Install Magisk manager on your phone.
2 Copy the AP file on your Download folder of your phone.
3 Open Magisk and tap Install Magisk then Select and patch a file. Go on Download folder and select the AP file to patch. After is done it will create a file in your Download folder named magisk_patched.tar. Copy this file back on your PC.
4 Run Odin and put your phone on Download mode. To get in Download mode shut your phone off, Hold pressed VOLUME UP + POWER, select Reboot to bootloader.
5 In Odin select BL, CP and Home_CSC from your stock ROM folder. In AP select the magisk_patched.tar file. Go on Optons and uncheck Auto Reboot. Hit START and let him finish. IMPORTANT, READ FIRST : After is done you have to restart the phone by pressing VOLUME DOWN + POWER and when the screen is black immediately press VOLUME UP + POWER. Dont let go until you are in Recovery mode, even if restarts.
5 select Wipe data/ factory reset and then Reboot system now. Might take a while to boot.
6 Set up your phone and install Magisk Manager again. It will ask you to complete the rooting will need to install few more files. Press OK.
WELL DONE. You have root now.
[RECOVERY][UNOFFICIAL]TWRP 3.3.1-0 Galaxy J8 J810M/F/FN/G/DS
https://forum.xda-developers.com/an...overy-twrp-3-3-1-0-galaxy-j8-j810m-f-t3962423
[Magisk 20.4] Primary option
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
[Manager 7.5.2]
https://www.apkmirror.com/apk/topjohnwu/magisk-manager/magisk-manager-7-5-2-1e2de1bb-release/
[no-verity-opt-encrypt-6.1.zip]
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Official]
Magisk Official Post
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[RMM State Fix] Miracle box
https://forum.xda-developers.com/ga...-rmm-fix-oreo-8-1-oem-unlock-fix-dez-t3877764
The Secret Of My Seccess is Jesus
Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.
Someonerandom said:
Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.
Click to expand...
Click to collapse
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg
hacker812c said:
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg
Click to expand...
Click to collapse
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?
Someonerandom said:
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?
Click to expand...
Click to collapse
Yes
If j8 use custom kernel 10
You install any release treble
I have release arm and arm64
Can i do that with android 8?
J810F android 8 or 10 working ???
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