Develop Bugs

[Q] Need some help on flashing rom.

O.k my wife got an AT&T Samsung Galaxy S3 when they first came out I bought it for her and it has this rom build on it l747UCALG1 and mine which I just bought about three days ago have this build on it l747UCALH9. Her build I was able to root if need be but my phone I can't and I am already on 2 count of the custom binary and I can't reset it since some how I can't root the phone the developers are seeing all of this stuff that we are doing to the phones and I believe they are trying to stop us. But anyway can some one tell me since I have a copy of her stock Firmware how can I just flash my phone or what have you with her stock firmware which is l747UCALG1 so I can root my phone. Also if you don't mind please leave me a clear step-by-step way to do it and if it works without doing any damage at all to my phone, and if I want to later go back to the stock that is on my phone now I can but I don't think I will unless I have to send or take it in ever for warranty repair or just sale it. If this works right leave me your e-mail or if you have a paypal account give me that address or what have you and I will send you a donation.. (Thanks)
Sincerely,
System Network Admin

http://forum.xda-developers.com/showthread.php?t=1739426
OR
http://forum.xda-developers.com/showthread.php?t=1746665

How to Revert to Old Firmware & Root Newest Release -
Hello and welcome to XDA.
I understand your concern to root your device especially with it being on the latest firmware, but I will do my best in order to explain every step to you in the utmost detail. I am currently on I747UCLH9 with a Custom ROM. Meaning I kept the Modem & Bootloader and kicked the Kernel and Firmware. Before I begin, I would like to ask you to thank to all the Developers / Posters who made & put this content together as this would not be possible without them. I will link all of their original posts at the end of this. Be sure to give credit to every one of them and please make sure to give thanks to them. I take absolutely NO CREDIT for any of these links/steps whatsoever. I simply researched and compiled them in order to help you. With that being said, let us begin.
Before anything you must remember this. After you are finished downloading whatever items you need, you MUST (and I cannot stress this enough) FACTORY RESET YOUR DEVICE. Reason being is because a lot of other people have tried this same process of downgrading without wiping and ended up getting startup boot errors. Be sure to NOT sign into your Google account. This is just a warning, follow the steps below to know when you should begin this process.
All files you download should be saved on your desktop. Personally I prefer to make a separate folder for these kind of delicate things. Keeps it organized so you don't forget where you are.
Make sure your phone IS NOT plugged in to your computer as of right now & you have NO external SD card.
Now;
Let's begin.
Before you start be sure you have the Samsung USB drivers installed. Which you can get from Samsung's website or here.
Samsung USB Drivers
Also be sure that you have WinRAR installed as well which you can get right here.
WinRAR
To be on the VERY SAFE side you must download ADB (Android SDK). What you must do is when it asks you for where you would like to install it, you MUST ONLY CLICK "Local Disk C:" . AND THATS IT. The best thing is to keep it here so when you have to execute a command line, it will be very simple. You will have a folder called "android" here. THAT IS YOUR ADB FOLDER. You will understand what I mean shortly. *Note* this is for CWM-T (ClockworkMod Touch).
Android SDK
1. Download the stock rooted LG1 Firmware. I747UCLG1 Stock + Root Only.
2. Right-Click the LG1 Firmware you just downloaded and extract it. It is currently root69.stock_ATT_I747UCALG1.7z ; the extraction process will turn it into the correct .tar file (Flashable file type with Odin)
3. Now that you have the Stock ROM, you need..well ODIN! Here's the link. Odin 3.07.
4. Since it is in .zip format you need to extract this as well. You will end up with 4 files. Right-Click on the Odin3 v3.07.exe and run it as administrator. Now you are at the Odin screen with nothing there -_-".
5. Factory reset your phone. Just let it boot up but DO NOT sign into your Google account, just click through skip everything head straight to your Settings, then Developer Options & make sure USB Debugging is enabled/checked. Back out of your settings completely and you are at the home screen.
6. Now, just hit the power button and turn your device off. After it is completely turned off hold the Volume Down + Home button. While holding these 2. Press and hold the Power button. You should now be holding all three buttons at the same time waiting for a green lettered screen to come on (Download Mode). Use the phone keys to select the option to continue. Your phone will now say Downloading, do not turn off device. (Or along those lines).
7. After selecting the option that sends your phone to the screen with the text "Downloading, Do not turn off device." You should be holding your phone in hand with USB plugged into your computer but your device is not connected. Odin is open on your computer screen with nothing still. From here just plug your phone in and you will see a pop-up in the first box of many under the Odin logo which says "COM: #".(#: Being a select number of your device. This is of no importance, as long as you see this pop up.) Once you see this your phone will be ready to be flashed back. Just click the PDA button and browse to the root69.stock_ATT_I747UCALG1.tar file. (Be sure you click the .tar and not the .zip.)
8. Check to make sure no other boxes should be checked except for Auto-Reboot.
9. Press Start and wait for the process to finish.
10. Everything should go through fine and your phone will start back up and you will be on LG1. You are now on stock firmware BUT rooted. Unplug your phone, Skip past everything once again and make sure USB Debugging is enabled. Keep your phone unplugged & don't forget to close ODIN.
Now before you do anything. You need a Custom Recovery AKA CWM. Well in this case we will be installing the latest touch version.
11. Download the latest ClockworkMod Touch from here. This link is saved in a way specifically from their website. You can either go to www.clockworkmod.com and browse the ROM Manager tab for the 6.0.1.4 Recovery. OR you can just right click the link provided right here and press "Save As..." this file will come up and asked to be saved as recovery-clockwork-touch-6.0.1.4-d2att.img. RENAME IT AS "recovery.img" without the quotes & save it.
ClockworkMod Touch 6.0.1.4
12. Now that you have this file. Plug in your phone to your computer and in the root folder of your phone storage and copy the recovery.img file to it; which is the first folder that pops up when you press open when you plug your phone in. (Remember no SD CARDS!)
13. Now, click the Start button on your taskbar and in the search bar type cmd. Now you will see cmd.exe; press enter and you will see the Command Prompt open. If you saved the Android SDK the way I told you to, you can copy and paste the line below. If you saved it somewhere else you can change the folder simply by browsing to the android folder. Make sure you click on the "platform-tools" folder. NOT the "platform" folder. Also whichever directory it is you must add a "\" at the end so it will find the location correctly.
cd C:\android\platform-tools\
14. Now you are in the directory time to run ADB Shell and flash that recovery! Copy and paste or type the following; I recommend you copy and paste the last line as it gets tricky. After the SU command your phone will be detected.
First you type adb shell
following that su
and finally dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
As you can see in the last command it is named recovery.img there are no special characters or numbers or symbols to mess with the flashing. After you run this command you will an output similar to the following.
14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.430 secs (5014019 bytes/sec)
Finish up this step with the following command
reboot recovery
15. Your device will now restart and head straight into recovery. Congrats you now have LG1 Stock + Root with CWM-T. Unplug the USB and press "Reboot System".
TO UPGRADE BACK TO LH9 WITH ROOT AND CWM-T
Before I begin.
You must remember that this step REQUIRES you download 4 files to go on the root of your phone memory. Your phone should now be on the home screen. Plug it in and open your phone memory. With that being said you need the following files. The Rom, Modem, Bootloader, and Kernel. You will be flashing them in this following order as well.
16. Download the following pieces and save them to the root of your phone's memory. Be sure to remember which file has what name so when you enter the recovery you aren't lost as to which to flash first.
I747UCLH9 ROM Download
I747UCLH9 Modem Download
I747UCLH9 Bootloader Download
I747UCLH9 Kernel Download
17. After everything has finished transferring, remove the phone from the computer and turn your phone. Remember how you got into download mode? Well instead of holding Volume Down + Home, you hold Volume Up + Home. While holding these two press and hold your power button until you see it says Samsung Galaxy S III. If you look at the top left hand of the screen while it's JUST turning on. You will see some blue text flash. When you see that you know your entering the recovery and can release the buttons.
18. You are back at the recovery. You must now do the following. Touch the options as I list them. Follow these steps precisely.
- Wipe Data/Factory Reset
- Yes -- Delete all user data
- Wipe Cache
- Yes - Wipe Cache
- Advanced
- Wipe Dalvik Cache
+++++Go Back+++++
- Install Zip from SD Card
- Choose zip from SD Card
Now choose them in the following order, ROM, Modem, Bootloader, and finally Kernel.
WAIIIITTTTTTTT! After you are finished flashing the Kernel you MUST do the following. Click options as I state them.
- Wipe Cache
- Yes - Wipe Cache
- Advanced
- Wipe Dalvik Cache
- Advanced
- Fix Permissions
+++++Go Back+++++
Reboot System
19. Wait for your phone to reboot and NOW you can sign into your Google account. Go past everything go into your App drawer first and check for Superuser/SuperSU once you see that, go into your settings and check your ROM, Modem, Bootloader, Kernel. Yes. They are bone stock with root. Congrats you achieved maximum upgrade with root.
Now I would like to give my shout-outs; Thanks; and share the following posts that helped me compile this. I couldn't have done it without you guys.
neverends - Samsung Drivers & Odin provided. Steps to flash with Odin as well.http://forum.xda-developers.com/showthread.php?t=1722686
mrRobinson - I747UCLG1 Stock root injected file. Location of Odin, and commands to execute ADB shell to flash recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
drothenberger - Provided CWM Flashable version of I747UCLH9. Blessing, really. Stock root with latest FULL update without having to revert back to LG1 stock.
http://forum.xda-developers.com/showthread.php?t=1896773
ALSO
Thanks to you all above; the CWM Team, CM10/AOKP Team, Moderators & Posters alike. None of this would have been possible without you. Keep up the good work. Bless -

jaysoblitzed said:
Hello and welcome to XDA.-
Click to expand...
Click to collapse
You made an awesome guide!! Hope he made a generous donation. Thanks!!

werked said:
You made an awesome guide!! Hope he made a generous donation. Thanks!!
Click to expand...
Click to collapse
Thank you, I really appreciate that. I don't accept donations I simply did it to help those who wanted/needed it
Sent from my T&K Blessed SGH-I747

I do not see the 4 download links for the ROM, Modem, Bootloader and Kernel. Can you post them.

I will fix the links but if you simply look at the people / threads I have given credit to at the bottom of my guide you will see drothenberger's thread. He has the original links there. Mind you, you MUST scroll down to the part where it says "PIECES:" and download following his links. Don't worry I will re-post them accordingly.
Sent from my T&K LH9 Blessed SGH-I747

Does upgrading from rooted LH9 from a rooted LG1 trip flash counter since we are installing 4 separate files instead of 1 .tar?
thanks!

Solutions found for Samsung Galaxy Discover(SCH-R740C)

Initial instructions can be found here. but i will detail them out further.
Disclamer: these files are meant specifically for the Samsung Galaxy Discover(SCH-R740C). Use on any other device will result in an instant brick of device. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures.
You have been warned.
now to the goodies.....
List of supplies:
1. Phone (SCH-R740C)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. Files from this location. click here
HOW TO UPDATE DEVICE FROM 4.0.4 TO 4.1.2​
easiest method is to use simple upgrade tool from here or here under downloads then software.
the simple upgrade tool will update the device if like mine, the OTA method failed.
ROOTING​
NOTE:this method only works for devices already running 4.1.2. for rooting 4.0.4, use kingoroot which can be found here
before starting, please make sure you have "UPDATE-SuperSU.zip" copied to the root of your external SD card which you can download from here
+++to install CWM:
Follow these steps very carefully, or you might brick your phone.
1. Download Odin package and CWM-recovery-amazing3gcri-eng.tar.md5 from here Extract Odin to a known location and copy the tar.md5 files to the same location
2. Right click on the .exe file inside of the odin folder and select “Run as Administrator”
3. Now that odin is running:
4. Place you galaxy discover in download mode:
4a. With phone off hold vol - and power button
4b. Wait for the phone to present it warning menu release vol - and power
4c. press Vol +
5. CLICK ON THE PDA BUTTON
6. Browse to the appropriate sub directory and select "CWM-recovery-amazing3gcri-eng.tar.md5"
7. Press Start.
DO NOT DISCONNECT, UNPLUG, PLAY WITH ANY BUTTONS, OR CLICK ANYTHING ON EITHER THE PHONE OR COMPUTER UNTIL ODIN HAS FINISHED FLASHING CLOCKWORK RECOVERY ON YOUR PHONE.
8. To boot into recovery, turn off the phone, now press and hold the volume up button, press and hold the power button, wait for phone to boot to recovery, release both buttons. ignore the triangle at the bottom of the screen, that will get fixed later
9. Now highlight "Install ZIP". select "choose from sdcard"
10. Scroll to "UPDATE-SuperSU.zip", and select using power button. another menu will pop up with "- - Yes Install UPDATE-SuperSU-v1.94.zip" use power button to select it.
11. Wait for the magic.....
12. Once it is done, go ahead and pull battery and reboot device.
+++At this point, your device if the steps above have been followed to a T, should be fully functional(rooted) and running 4.1.2.
TO INSTALL NEAR-STOCK DEODEXED 4.1.2​
1. Download "deodexednearstock4.1.2SCH-R740C.zip" from here. and put it onto the root of your external SD card.
2.reboot phone into CWM recovery
3.(recommended but can be skipped if on 4.1.2)once in recovery, use the volume keys to highlight wipe data/factory reset. use the power button to select it.
3a. use volume keys again to highlight " Yes - Wipe all user data". and use the power button to select it. wait until it is done
4.highlight "Install ZIP. select "choose from sdcard"
5. scroll to "deodexednearstock4.1.2SCH-R740C.zip", and select using power button. another menu will pop up with "- - Yes Install deodexednearstock4.1.2SCH-R740C.zip" use power button to select it.
6. wait for the magic.....
7. once it is done, go ahead and pull battery and reboot device. it may take about up to 10 minutes or so to get into the device itself to get it set back up.
+++at this point you should be on stock(except for launcher and browser) deodexed 4.1.2
just a word of warning, you'll have to install a web browser into it. when i first installed NakedRom from it's original form, it did not come with one. And to get Google Voice Search to work, just let it update from the Play Market.
TO REMOVE TRIANGLE ON BOOT​
1. Go into download mode again (volume down + power and then volume up)
2. Plug in the phone.
3 Open Odin and select PDA and open "stock_recovery.tar.md5"
4. Make sure phone recognizes, and hit start.
4a. Again, same as last time, do not touch device until it says complete.
5. When it's done, pull battery and reboot device.
+++At this point the triangle should have gone away but just to make sure.....
6. download and install triangle away from chainfire. here's the link
7. follow these instructions here. it's a youtube video about an S3 but the way you work the application should be really close to what's shown. run the application and let it do it's thing.
now device is completely stock (except the ADW launcher and root)
credits/ kudos; thanks to cowboyenvy for providing the initial tutorial.
chainfire for his wonderful softwares. and the gentleman who ported NakedRom to this device (to which this is all based off of).
just a word of warning, you'll have to install a web browser into it. when i first installed NakedRom from it's original form, it did not come with one. And to get google voice search to work, just let it update from the market.
the rom is fully deodexed so you should see a little bit of a speed improvement.
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.

REriginal post
will have files in their respective locations in less than 20 minute from this post

schizoidd said:
will have files in their respective locations in less than 20 minute from this post
Click to expand...
Click to collapse
ignore this quote. everything's ready

no longer developing on....
I am no longer Deving on this device. I have a HTC Desire 510 now that I have been working on an will release things for it as needed

But I will be keeping links alive until cricket stops CDMA support in July of this year

warnings
just an FYI, maxing out the processor speed not only greatly reduces battery life of the device but also shortens the usable life of the device even after changing the battery
by the end of my device's life, it was only good for making calls, surfing the internet, sending texts, etc. but I couldn't play even the simplest of games (like 2048) without my device freezing

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.

Easy guide: flash SuperMan-Rom on the S7 930F, using Heimdall on Linux/MacOS/Windows

Tired of 1000-page threads and confusing instructions? Here's how to flash a new S7 to the excellent SuperMan ROM using the open source tool Heimdall (far easier than Odin, and works on Linux and MacOS as well as on Windows). You'll get root in the process, install the Blueborne patch (which hasn't yet shipped to all Samsung phones via OTA updates), remove a bunch of annoyances like the "volume too loud" warning, and get a fast phone without bloat or apps you can't remove.
What you need
S7 G930-F or FD (why you'd get a non-international phone beats me, F or FD (dual SIM) are the best variants of the S7)
The phone is new or you've backed up all your data - you can do that using TWRP between steps 11 and 12 below
PC or Mac
MicroUSB cable
microSD card inserted into the phone
Step-by-step instructions
Download the SuperMan ROM .zip
While it's downloading, boot your new phone normally
Activate Developer options (Settings -> About phone -> (Software info) -> Build number, and tap it 7 times)
Go to Settings -> Developer options and check "OEM unlock"
Download the latest TWRP .img from https://dl.twrp.me/herolte/
On Linux, download the attached heimdall binary, or compile it per the instructions at the very end of the Linux README (don't worry about QT, you're not going to need the front-end because it's buggy and unnecessary; here are all the dependencies you need). On MacOS or Windows, get the Heimdall binaries from Heimdall's home page.
When the SuperMan ROM is finished downloading, copy it to the external microSD card
Power off the phone and boot it in Download mode (Home+Power+Volume Down)
Run heimdall flash --RECOVERY twrp-<version>-herolte.img
If it doesn't do so automatically, reboot the phone in recovery mode (power off, then Home+Power+Volume Up)
In TWRP, swipe to allow modifications
Format Data and type "yes". This will remove the encryption.
Back in TWRP, choose "Install" and locate the ZIP on the external_sd card
Reboot to install the SuperMan ROM (don't be alarmed if the boot animation takes ~10 minutes) - the installer is referred to as "Aroma" and will let you choose a bunch of configuration settings and apps to install.
I recommend NOT installing any 3Minit apps unless you're into questionable-bordering-on-pointless theming of the battery indicator and clock (hopefully you have better things to do with your life)
I also recommend not installing any apps you can install later from Play.
That's it. Clear, simple instructions. You're welcome.

this has nothing to do with superman rom but how one gets a custom recovery on their phone.
plus this is in the wrong thread.
probably why people are reading 1000s of posts in the 1st place is by posting dupe info.

[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.