Unable to flash recovery/supersu on Galaxy A6 - General Questions and Answers

Hi,
Background: I did it all a lot with my One+1/+3. I'm working with terminal & ADB command line tool. So all the enable unlock OEM. USB modes etc. are set up (I'm Android SW APP dev).
I have 2 quick questions.
Now with the Galaxy A6+ nothing works: So I get it there is no fastboot, and I'm able to get into the download mode (substitute to fastboot) only via recovery->reboot to bootloader. While I wanted to get there via adb reboot fastboot. OK.
Then I tried to flash recovery img.tar using Odin - everything seems good, but then adb reboot recovery - and I'm back in the default (useless) recovery.
Question number 1: Why flashing the recovery not worked?
Another shot: adb reboot recovery -> apply update from ADB -> adb sideload SuperSU.zip, again everything looks good, but then adb shell su - no root.
Question number 1: Why flashing SuperSu not worked?
Thanks,
Mike

mikethe1 said:
Hi,
Background: I did it all a lot with my One+1/+3. I'm working with terminal & ADB command line tool. So all the enable unlock OEM. USB modes etc. are set up (I'm Android SW APP dev).
I have 2 quick questions.
Now with the Galaxy A6+ nothing works: So I get it there is no fastboot, and I'm able to get into the download mode (substitute to fastboot) only via recovery->reboot to bootloader. While I wanted to get there via adb reboot fastboot. OK.
Then I tried to flash recovery img.tar using Odin - everything seems good, but then adb reboot recovery - and I'm back in the default (useless) recovery.
Question number 1: Why flashing the recovery not worked?
Another shot: adb reboot recovery -> apply update from ADB -> adb sideload SuperSU.zip, again everything looks good, but then adb shell su - no root.
Question number 1: Why flashing SuperSu not worked?
Thanks,
Mike
Click to expand...
Click to collapse
You probably flashed the file correctly, where you messed up is you didn't use the correct booting procedure to keep the custom recovery, if you don't use the correct boot order, the device reverts to stock recovery.
Follow these steps to correctly flash the recovery .tar file via Odin.
1) charge battery to full
2) boot device into download mode
3) open Odin
4) connect your device to PC
5) place the recovery .tar file in the AP slot in Odin.
6) find the options in Odin, find the "autoreboot" option, make sure that option is UNCHECKED(it is easier if you do not let the device automatically reboot after the flashing process is done).
7) click Start in Odin.
8) Wait for it to flash and give you a green PASS.
9) After the flash is complete and you have a green PASS, disconnect your device from PC.
10) power the device off (or manually remove/disconnect the battery then replace/reconnect the battery).
11) press and hold volume up+home then power(or press and hold volume up then press and hold power if you don't have a home button), when you see the Samsung logo, release the power button but continue holding the volume down+home button(or just volume up if you don't have a home button) and it should boot into TWRP and you'll keep TWRP this time.
Sent from my LGL84VL using Tapatalk

Droidriven said:
You probably flashed the file correctly, where you messed up is you didn't use the correct booting procedure to keep the custom recovery, if you don't use the correct boot order, the device reverts to stock recovery.
10) power the device off (or manually remove/disconnect the battery then replace/reconnect the battery).
11) press and hold volume down+home then power(or press and hold volume down then press and hold power if you don't have a home button), when you see the Samsung logo, release the power button but continue holding the volume down+home button(or just volume down if you don't have a home button) and it should boot into TWRP and you'll keep TWRP this time.
Click to expand...
Click to collapse
This not worked:
1. From download mode my only option to exit/reboot is power & vol down, and then it reboots into Android.
2. There is no option in Galaxy A6 Plus to remove the battery.
3. Anyway, the correct way to enter into recovery in Galaxy A6 Plus is also Power & vol up, not just down as you wrote (In both cases you end up booting into recovery).
4. Then, after it booted into Android->power off->boot into recovery: For a moment I see blue screen with Android logo, and then in goes to original recovery, printing the following:
#fail to open recovey_cause(No such file or directory)#
#Reboot Recovery Cause is [UKNOWN]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Performing factory reset and repeating this "dance" gives same results.
I repeated the same with various links to TRWP versions, Some of them intended for A6 (not A6 plus):
(a) Some of those originally intended to A6 Plus failed on Odin, and some succeed.
(a) Some of those originally intended to A6 failed on Odin, and some succeed.
But regardless, in all Odin success case, the mentioned in the beginning situation repeated: No way to shut down from download mode->Boot into Android->Boot into Recovery with above message.
When rebooting into download mode, the following is printed:
ODIN MODE (HIGH SPEED) (in red)
PRODUCT NAME: SM-A605G
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
OEM LOCK: OFF
WARRANTY VOID: 0x1 (0x20c) (some pointer to bytes in Hexa)
QUALCOMM SECUREBOOT: ENABLE (CSB) (in gray)
RP SWREV: S1, T1, R1, A1, P1 (in gray)
RP SWREV: K 1, S 1 (in gray)
SECURE DOWNLOAD: ENABLE (in blue)
DID: some Hexa string
download mode !! (in yellow)
Thanks,

mikethe1 said:
This not worked:
1. From download mode my only option to exit/reboot is power & vol down, and then it reboots into Android.
2. There is no option in Galaxy A6 Plus to remove the battery.
3. Anyway, the correct way to enter into recovery in Galaxy A6 Plus is also Power & vol up, not just down as you wrote (In both cases you end up booting into recovery).
4. Then, after it booted into Android->power off->boot into recovery: For a moment I see blue screen with Android logo, and then in goes to original recovery, printing the following:
#fail to open recovey_cause(No such file or directory)#
#Reboot Recovery Cause is [UKNOWN]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Performing factory reset and repeating this "dance" gives same results.
I repeated the same with various links to TRWP versions, Some of them intended for A6 (not A6 plus):
(a) Some of those originally intended to A6 Plus failed on Odin, and some succeed.
(a) Some of those originally intended to A6 failed on Odin, and some succeed.
But regardless, in all Odin success case, the mentioned in the beginning situation repeated: No way to shut down from download mode->Boot into Android->Boot into Recovery with above message.
When rebooting into download mode, the following is printed:
ODIN MODE (HIGH SPEED) (in red)
PRODUCT NAME: SM-A605G
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
OEM LOCK: OFF
WARRANTY VOID: 0x1 (0x20c) (some pointer to bytes in Hexa)
QUALCOMM SECUREBOOT: ENABLE (CSB) (in gray)
RP SWREV: S1, T1, R1, A1, P1 (in gray)
RP SWREV: K 1, S 1 (in gray)
SECURE DOWNLOAD: ENABLE (in blue)
DID: some Hexa string
download mode !! (in yellow)
Thanks,
Click to expand...
Click to collapse
I corrected my typo, it was supposed to say volume up+power to boot to recovery.
When flashing recovery, you have to boot into recovery mode immediately after flashing the recovery, you can't allow the device to boot to any other modes before going to recovery, if it does, it reverts back to stock recovery.
Try this
Flash the recovery via Odin, make sure the autoreboot option is UNCHECKED, after it is done, disconnect your device, then press and hold volume up+power, hold it long enough and it should power down, keep holding them until it boots again, when you see the Samsung logo, let go of the power button.
One thing I need to mention, are you sure that your bootloader is unlocked? If it isn't, you can't flash TWRP on the device.
Also, your battery is removable, you have to remove the cover and you'll see a ribbon cable connecting battery to mainboard. You can disconnect that ribbon cable then reconnect it.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Try this
Flash the recovery via Odin, make sure the autoreboot option is UNCHECKED, after it is done, disconnect your device, then press and hold volume up+power, hold it long enough and it should power down, keep holding them until it boots again, when you see the Samsung logo, let go of the power button.
One thing I need to mention, are you sure that your bootloader is unlocked? If it isn't, you can't flash TWRP on the device.
Also, your battery is removable, you have to remove the cover and you'll see a ribbon cable connecting battery to mainboard. You can disconnect that ribbon cable then reconnect it.
Click to expand...
Click to collapse
I tried "press and hold volume up+power, hold it long enough and it should power down" while the phone is in loading mode - not working. The only thing that triggers something is volume down+power (reboots into Android.
Yes the bootloader is unlocked.
It's seems impossible to open the back cover.
Thanks,

mikethe1 said:
I tried "press and hold volume up+power, hold it long enough and it should power down" while the phone is in loading mode - not working. The only thing that triggers something is volume down+power (reboots into Android.
Yes the bootloader is unlocked.
It's seems impossible to open the back cover.
Thanks,
Click to expand...
Click to collapse
Ok, another trick is this.
Flash the recovery .tar file in AP slot, this time you want the autoreboot feature to be checked. When the device is flashing, pay attention, when it's done, it will automatically reboot the device. You need to be right there waiting and ready with your finger on the volume up button waiting to press and hold the volume up button when the device starts the reboot, if you time it right, it should boot into TWRP.
Sent from my LGL84VL using Tapatalk

Hi! I'm new here and also had the same issue about this phone (A6 2018). The problem is it won't turn on yet I can still enter into recovery mode and Odin Download mode. Question is what should I do?

Related

[Q] P3100 Unlock Bootloader, FastBoot, Modes

I apologize if I have understood this all incorrectly, but kindly clarify the following for me.
What I have already done:
1. Installed CWM (ClockWorkMod) on the tablet: Galaxy Tab 2 7.0 using Odin
2. Installed the rooting zip file from external sd
3. Made a backup image on an external sd
What I need to do:
1. Flash a custom ROM onto the device from my PC using fastboot
Errors:
1. Fastboot devices returns nothing (absolutely no response... please find the attached pic)
2. Adb reboot bootloader - just reboots the OS (not in fastboot)
3. Fastboot oem unlock says waiting for device endlessly.
My Queries:
1.I have a recovery mode and download mode (aka odin mode). Is either of them the FASTBOOT mode or is fastboot something completely different. If so how to get into FASTBOOT mode??
I read I have to get a USB icon and a Fastboot mode display on screen. I do not.
2. Why is my device not showing under fastboot devices (on download mode, neither show the device.), but adb devices shows the device under recovery mode
3. Is it possible to flash a ROM using fastboot if I have CWM installed. Or does CWM disable fastboot?
4. Also does this device have a Fastboot mode at all? If yes how to get into Fastboot mode??
From what I've read here, there is no fastboot mode on the Tabs.
Balthazar B said:
From what I've read here, there is no fastboot mode on the Tabs.
Click to expand...
Click to collapse
In that case, how do I flash a custom ROM onto the device?
Thanks!
rtindru said:
In that case, how do I flash a custom ROM onto the device?
Thanks!
Click to expand...
Click to collapse
load it on your external sdcard, boot into cwm and do a fullwipe/factory reset then install the zip from sdcard. poof, rom installed
to boot into cwm, turn off the tablet.
press and hold power and volume down (the one closes to power button) once the samsung tablet logo appears let go of power and continue holding vol down until cwm appears (this can take a couple minutes)
Thanks then!
Darunion said:
load it on your external sdcard, boot into cwm and do a fullwipe/factory reset then install the zip from sdcard. poof, rom installed
to boot into cwm, turn off the tablet.
press and hold power and volume down (the one closes to power button) once the samsung tablet logo appears let go of power and continue holding vol down until cwm appears (this can take a couple minutes)
Click to expand...
Click to collapse
Well thanks for the info.

Can't enter download mode (fastboot enabled)

So i followed a thread and loaded a profile on a kernel manager, reboot and now i'm stuck with a black screen saying [random number] Fastboot mode enabled. I can't enter download mode for flashing stock rom or do anything else. Is there a fix for this?
Lg-H955 model
Push and hold Vol Down + Power, wait few seconds, the device is rebooting or power .
If the device is power off, or reboot, connect usb and release power button, just hold the vol down.
If your laf untouched, download mode is working and flash kdz.
You can't do anything via fastboot, all commands disabled, only some getvar working...
stars2 said:
Push and hold Vol Down + Power, wait few seconds, the device is rebooting or power .
If the device is power off, or reboot, connect usb and release power button, just hold the vol down.
If your laf untouched, download mode is working and flash kdz.
You can't do anything via fastboot, all commands disabled, only some getvar working...
Click to expand...
Click to collapse
Can't poweroff the device... and power+vol brings always to the same fastboot screen =/
I also tried to flash laf.img from the kdz i had, but it fails
Fastboot is totally useless, because all commands disabled, you can't flash, erase, etc... I'm sure
If your laf is not working (i think, no working downlod mode, because reverted to fastboot) or your phone is not booted normally, your phone is bricked.
Only two solutions for you (currently)
1. LG Service
2. EMMC direct flash (require to desolder emmc chip from the pcb)
stars2 said:
Fastboot is totally useless, because all commands disabled, you can't flash, erase, etc... I'm sure
If your laf is not working (i think, no working downlod mode, because reverted to fastboot) or your phone is not booted normally, your phone is bricked.
Only two solutions for you (currently)
1. LG Service
2. EMMC direct flash (require to desolder emmc chip from the pcb)
Click to expand...
Click to collapse
I'm in italy so lg service doesn't cover rooted devices =/. What's EMMC direct flash? If it's a hardware thing i guess i'm screwed

PLEASE HELP! Bricked Honor 8

Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Meiton said:
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Click to expand...
Click to collapse
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
clsA said:
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Clearly follow My steps To unbrick and get normal device ::
Step 1 ::
Download the full firmware of your device.
Step 2 :
make sure that your bootloader is in unlocking state
Follow the video blindly ::: https://youtu.be/OMKDnBqbi3U?list=PL...eT9J26lkefvVkK
don't panic of mobile.
Step 3 :: done ..enjoy u did it
--------------------------------------------------------------------------
If you bricked on nougat then follow the below steps
step one :::
download the downgrade package to mm .
then extract the zip and open the update.app using HuaweiUpdateextrator in that select recovery and extract
1.now, boot your device into fastboot and flash the recovery (Optional)(try this if it said incompatible version on recovery)
2. on your sd card and make a folder "dload" . and copy the update.app which we have extracted earlier
3.the switch off the device and press all three buttons you will be reboot into recovery and done . you device will be okey
Meiton said:
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Click to expand...
Click to collapse
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
clsA said:
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I appreciate your help but I've tried it multiple times always with the same result.
I also can use "adb reboot bootloader", but it will reboot again to stuck recovery.
DJ Daemonix said:
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Click to expand...
Click to collapse
I've tried that, but I am still stuck as that tool is using fastboot as every other tool to flash .img files.
Thank you for the tip though.
Plug phone into computer with USB, then hold down power + volume down until it eventually boots into bootloader. I had the same scenario as you and that's how I got into the bootloader. You can flash either a good TWRP or the stock recovery, either one will work.

How To Guide Unlocking the bootloader and rooting

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
UNLOCKING BOOTLOADER​1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. After holding VOL UP for 10 seconeds you should get in to the screen that will let you unlock the OEM so now just press VOL UP.
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
12. Check in developer options if oem unlocking is grayed out, if it isn't factory reset data and wipe chace partiton will have to be done.
ROOTING​1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds).
After the phone turns off, amedietly boot in to recovery (Vol + and POWER at the same time)
12. Make a factory data reset and whipe cache partition
13. Reboot in to system
14. Conect to interent during setup
15. Enable dev options by taping on build number 7 time. OEM UNLOCKING must be grayed out.
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing, go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
20. After flash reboot
21. Check in developer options if oem unlocking is grayed out, if it isn't the instalation process will have to be followed again
THIS IS A OLD METHOD OF INSTALLING TWRP
INSTALLING TWRP, I RECOMEND FOLOWING MY LATEST GUIDE
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
​INSTALLING TWRP OLD METHOD​# If you are not on the A125F or A127F you might have to do a crossflashing fimware operation
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
LAST_krypton said:
Code:
Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
Click to expand...
Click to collapse
LAST_krypton said:
Code:
# Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
UNLOCKING BOOTLOADER
Code:
1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. VOL UP for bootloader unlock
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
ROOTING
Code:
1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds)
12. After the phone turns of, amedietly boot in to recovery (Vol + and POWER at the same time)
13. Make a factory data reset and whipe cache partition
14. Reboot in to system
15. Conect to interent during setup
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
19. After setup reboot
INSTALLING TWRP
Code:
If you are not on the A125F model you will have to disable MTK Secure Boot and Secure Download and might also downgrade SW REV and then install A125F fimware
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
Click to expand...
Click to collapse
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
edward0181 said:
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
Click to expand...
Click to collapse
Ok sure, I will do it when I get time.
Cheers
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Rularick5 said:
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Click to expand...
Click to collapse
It is possible, and it is the only way for you to do what?. To flash A125F fimware on A125U you have to go through a really complicated method to succeeded, you would have to dismantle the phone and force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware. And forgot to mention, you have to go trought some litle pain with SBL aswel.
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Rularick5 said:
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Click to expand...
Click to collapse
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the i gues
Click to expand...
Click to collapse
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Rularick5 said:
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Click to expand...
Click to collapse
See here, https://forum.xda-developers.com/t/...ing-theories-and-issues-with-our-a12.4336999/
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
Click to expand...
Click to collapse
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
wiiddakidd said:
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
Click to expand...
Click to collapse
You donwload the same fimware your phone is running and copy the AP.tar.md5 fimware file to your phone. Install cannary version of magisk and patch the AP.tar.md5. Transfer magisk_patched-xxxxxxx.tar back to your pc and in odin flash it in AP slot.
wiiddakidd said:
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Click to expand...
Click to collapse
A guide for that, maybe some other day. It would require phone disasembely to force PRELOADER. And what error do you when flashing AP file?
Hello, long time forum lurker here but never posted anything before. I recently have been having a headache from several different AT&T phones all being restricted to the point where I can't do anything with them. I have an SM-A125U from att that doesn't have an OEM unlock option.
Through my Ubuntu computer I can run some basic adb and fastboot commands but nothing that actually helps me. Still though the fact that I can make the phone go to recovery and fastboot make me wonder if there is really nothing I can do about this. Frija also won't let me get a firmware file for my device.
Not totally sure how it works but somebody said AT&T encrypts the software so you can't access specific functions. I am just wondering is there anything I can do through adb or fastboot to fix this issue in any way, or if my only real option is to just buy a new unlocked phone or something?
I explained it here, if it still doesn't work then comment again here.
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
drcroc said:
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
Click to expand...
Click to collapse
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
LAST_krypton said:
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
Click to expand...
Click to collapse
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
drcroc said:
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
Click to expand...
Click to collapse
Make sure OEM unlocking and usb debuging have applayed. Boot in to system, reset developer options and then enable them back. After that enable OEM unlocking and usb debuging and restart. After reseting and booting back in to SYSTEM power off the phone and hold VOL + and VOL - at the same time. UNLOCKING MENUE should now be shown and you will be able to get in to it by VOL + longpress.

Flashing TWRP without first flashing a vbmeta image with verity disabled rendered my Galaxy Note10 exynos unable to boot

Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
TheAckermans said:
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
SubwayChamp said:
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
Click to expand...
Click to collapse
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
TheAckermans said:
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
Click to expand...
Click to collapse
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
SubwayChamp said:
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
Click to expand...
Click to collapse
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
TheAckermans said:
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
Click to expand...
Click to collapse
The screenshots you uploaded some months ago, are the download screen, you, successfully did boot to, download mode doesn't have a useful menu, it's just a mode, so you can flash some things, using Odin. To boot to, use the same way you did it previously, usually, doing it manually, or if you are rooted, you can use other ways too.

Categories

Resources