Develop Bugs

pit files for i317 and i317m

As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.

If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480

Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?

pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.

Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.

anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?

Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.

Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...

anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.

terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.

rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin

Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app

Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).

Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!

My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks

Works fine on i317m

anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593

qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.

Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE

kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged

Unrooted note 4 change from 5.0 to 4.4

Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?

I am totally interested in this as well any step-by-step information would be highly appreciated

I would have to say no... you can flash back to 4.4... but need root to flash
Sent from my SM-N910P using Tapatalk

kaz007 said:
Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?
Click to expand...
Click to collapse
Here's a step by step procedure to downgrade, make sure you backup your internal sd card contents because it requires a data/reset on 4.4. since lollipop encrypts internal storage.
Download these 3 files.
USB (Driver) ver.1.5.45.0 ( Latest as of this post ) from samsung.com/support, search for your device SM-N910P and choose your color, and select manuals and downloads
Odin v3.10.6, from rwilco12's website, HERE
N910PVPU1ANK2 .TAR file, from ViperBoy's thread in generals forum HERE
Save these files to your desktop within a folder called Note4Downgrade makes it easier to find.
Uninstall your previous drivers like old Samsung, Kies of any versions.
open the Odin zip file, drag and drop its contents into the Note4Downgrade folder.
Open the N910PVPU1ANK2 zip file, drag and drop the .tar file into the Note4Downgrade folder.
Install the latest Samsung drivers, no need to reboot your computer.
Open the Odin3.10.6 executable file, select PDA or AP slot and load in the NK2.tar file, it'll take awhile and the Odin program will freeze as the file that its loading is ~1.8 GB's.
In the mean time while this is being loaded, shutdown your Note 4 Device and go into download mode by pressing Volume Down, Home Button, and Power Button Simultaneously.
Hold it down until it starts up into an Android Logo Firmware screen, Next Press Volume Up to continue into the next dialogue.
Once the file is loaded into the Odin program, use the original Samsung USB cable and plug it into a USB 2.0 port ( No, Not 3.0, Sometimes it can cause issues and errors, its do-able, but not recommended. )
Have the Odin Program detect your device and Windows will install the device drivers. Once this is done, a word within a blue box will state this message up top.
[COM:##]
It does not matter on what the "##" is as long as that is reading a number, meaning Odin has recognized and detected your device.
Stop here and recheck your progress.
- Latest Samsung Drivers installed ( SM-N910P )
- Odin 3.10.6 with loaded N910PVPU1ANK2.tar inside the PDA or AP slot
- Device in download mode, plugged into a USB 2.0
- Odin with [COM:##] in a box.
Proceed to clicking the "START" button if you have all of your above progresses done.
This will take around 15-30 minutes of flashing the stock 4.4 firmware, this will not tick the KNOX switch if you haven't rooted your device already as this is stock firmware.
It'll auto reboot once it is done, First time boot up will take longer as it is loading the device for the "First Time".
Once you're done, and you're on the welcome screen of the device, power it off.
Now we need to do 2 sets of resets, data factory within recovery, and an internal SD card wipe through Backup and Reset menu within settings of the device.
Now go into the devices recovery by pressing these 3 buttons. Power UP, Home Button, and Power Button.
Hold it until you see blue text at the top left corner of your devices screen stating "REBOOTING RECOVERY. . . ."
Then you can let go.
LEGEND
- Volume buttons = up or down
- Power Button = Proceed into next dialogue
From here go into the wipe data/factory and reset the device.
Once done, do a cache wipe.
and lastly, reboot the device.
Once your device has been rebooted, skip all the welcome steps and go to home, pull down the notifications bar and select the setting button up top.
scroll down to storage and unmount your Ext SD Card and take it out ( If you have one! ), now back out and go within Back up and Reset under personalizations. checkbox wipe internal Card and factory data reset again.
Once its all done it'll reboot, now you're on the latest firmware of kitkat on the note 4.
I hope this will help you as well as others wanting to stay on kitkat for any reasons they have or if they run into issues on lollipop.
Your guide, simplified!
- Spark91

Awesommmme! Thanks for taking the time Spark!

Glad I've helped out!

Very thorough guide.

bought a note 4 (sm-n910p) from eBay thinking that i can use ssu.apk to sim unlock the device. It was on lollipop.
so i thought i can downgrade to 4.4 . unfortunately while flashing kitkat using odin i got a fail message .After that phone is showing ("firmware upgrade encountered an issue ")
i tried to flash stock lollipop firmware using odin sadly now it show { THERE IS NO PIT PARTITION } error .
the device is on oe1 build

I'm on N910PVPU3BOF5 will that work with my phone ?

zjor2000 said:
I'm on N910PVPU3BOF5 will that work with my phone ?
Click to expand...
Click to collapse
I think of5 has an updated bootloader and cannot be downgraded.

[SOLVED] Help Flashing Lineage OS

EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS

Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.

abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!

I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.

I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.

~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?

abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18

Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.

~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?

vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.

~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.

vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...

~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.

[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model

Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw

*reserved*

Thank you for this amazing guide and the file without which it would not have been possible.

Be sure to join my TG group, if you are interested in AOSP, there's a lineage build testing currently running.

Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.

Awesome

sosimple said:
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Click to expand...
Click to collapse
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!

hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.

4TheBesT said:
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
Click to expand...
Click to collapse
If you are not sure what's the purpose of rooting a phone you shouldn't be doing it. "To make you happy with your phone" is a really subject question with no right answer, that depends on your specific needs.
If you ask about modules check out Magisk Modules.
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Hello, just to confirm that the steps detailed in this guide works, thanks OP, at least this gives us more freedom.
{
"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"
}

no able to root with this method ! .. step ( v-meta disabler ) with system CP,AP,HOME CSC fail with official binary .. i follow you're steps !
i guess the file v-meta disabler u have attached is not compatible with my device ?! and yes i have same you'res BTD2 ONEUI 2.1 FIRMWARE

teenoo said:
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
Click to expand...
Click to collapse
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.

Is there any way to unlock the bootloader and root SM-G770U1?

kamill85 said:
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Click to expand...
Click to collapse
I was about to give up on the July update until I read this and tried a few more things. Bad internet caused missing "Install" buttons and I tried patched the WHOLE AP...instead of just patching a boot.tar like in Stage 5. So gooder internet, Odin-ing only the AP with the Magisk patched boot.tar, another wipe,
Code:
adb install .\MagiskManager-v7.5.1.apk
and I was rooty tooty.
I didn't care about burning everything on the phone. I think that some of the extra steps here were for trying to minimize the wipes. Thanks for the extra hope @kamill85 !

Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,

SamFirm
sosimple said:
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
Click to expand...
Click to collapse
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!

dim42 said:
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
Click to expand...
Click to collapse
Thanks. What Deprecated meant? What iis the difference from original?

the show stopper said:
Is there any way to unlock the bootloader and root SM-G770U1?
Click to expand...
Click to collapse
+1
Also curious if anyone's gotten this working with the US version

So if i do this ill never ever be able to use Samsung pay ever again?

Vaughnn said:
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
Click to expand...
Click to collapse
Anyway to get to pass the safety nets?

Yes i pass safety net, but i use systemizer and with it i cant pass.
When I switch off systemizer in magisk I pass safety net

How To Guide Samsung Galaxy A54 5G [Root Stock ROM with Magisk]

WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel

Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app​

V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171​"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.​"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.​"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)​"App > Installed" shows the currently installed version of the Magisk app​
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations

Hello,
What about Knox with this method ??
Thanks

leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.

Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.

terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.

Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!

draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.

So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?

Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.

sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?

Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself

LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.

knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..

bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.

bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.

Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..