Related
UPDATED to include instructions for flashing other ROMS
I've successfully unlocked, flashed TWRP, rooted, and flashed Lineage on both an XT1602 and an XT1607. I'd done this before on other devices, but had forgotten just how it all came together, so when I was done I went back and made this step-by-step guide. It's a bit shorthand.
Many thanks to squid2 for his TWRP port, to the folks who make superuser, to parrotgeek1 for superSUFixer.zip, and to spiked_mistborn for reminding me about it. And, of course, huge thanks to squid2 and Alberto97 for the killer Lineage ROM. It is far better than stock or the last Nougat CM. If I forgot anyone, or made any mistakes here, somebody please point them out. Have fun!
1. Preparation (if the links don't work, search on xdaDevelopers or with Google)
a. Backup entire phone to the extent you are able, either with a dedicated tool and/or to Google via the Android backup feature
b. Download and install Motorola Device Manager on your computer from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 so as to make sure you have the proper drivers
c. Download adb and fastboot tools onto your computer from
http://forum.xda-developers.com/showthread.php?t=2588979 or
http://forum.xda-developers.com/showthread.php?t=2317790d. Download TWRP for Moto G4 Play to same folder as adb and fastboot tools from http://forum.xda-developers.com/devdb/project/?id=16870#downloads
e. Depending upon whether you want to flash Lineage or stay with the stock ROM, download to the same directory on your computer either:
i. Lineage and the Lineage SU addon (if you want root) from https://forum.xda-developers.com/g4-play/development/rom-lineageos-14-1-moto-g4-play-t3544646 and Google apps (arm 7.1 micro) from http://opengapps.org/; or,
ii. superSUFixer.zip from http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396 and superusersu.zip from http://www.supersu.com/download
Note: I did not find superSUFixer.zip necessary when I intially rooted, but after later installing squid's kernel it was indispensable to reinstallation of superusersu.zip.g. Attach phone to computer with USB cable, enable file transfer on phone and either copy the Lineage zip and Lineage SU addon zip and gapps.zip to your phone, OR copy superSUFixer.zip and superusersu.zip to the phone (you don't need to copy twrp)
2. Unlock bootloader
a. Enable developer options (Settings/About Phone/tap Build Number 7x)
b. Enable USB debugging on phone (Settings/Developer Options)
c. Enable OEM unlock on phone (same)
d. Open command window and change to the directory where you put adb, fastboot, and twrp
e. > adb devices (to check that you are connected - you should get a response with a device id)
f. > adb reboot bootloader
g. >fastboot oem get_unlock_data
h. On computer, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (you need to proceed through the login and to the second page)
i. Copy data returned by phone in the command window (make sure you copy all of it!)
ii. Paste that data into the Data Scrub Tool on the web page
iii. Copy scrubbed data, paste it into the box on the web page at step 6, and click the button; if it says you can't unlock your device, either you didn't copy and paste all the data, or your phone can't be unlocked and you're done; otherwise,i. Copy unlock key from email
j. > fastboot oem unlock <unique unlock key>
3. Flash TWRP
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
4. Flash Lineage and root, or just root -- when the phone has rebooted into recovery (you'll be in TWRP now)
a. follow prompts to make TWRP permanent or not
b. DO A FULL BACKUP OF EVERYTHING with TWRP
c. make sure you performed step b (or you may wish you had later, if something goes wrong!)
d. To flash another ROM, in TWRP
i. Wipe Data, Cache, and Dalvik. (Yes, you have to do this.)
ii. For Lineage - Install the Lineage zip file, the Lineage SU addon zip file, and the gapps zip file, one after the other, in that order, WITHOUT REBOOTING in between. TWRP will let you add all three to its queue to flash in order;
iii. For other ROMs - see instructions for those ROMs, but in general, install the ROM zip file, and then the gapps zip file, one after the other without rebooting in between. For root access, depending on the ROM, you may need superSUFixer, supersu.zip, or both; again, see the instructions for the ROM you are flashing.OR
e. To stick with the stock ROM but get root access, DO NOT WIPE, just flash superSUFixer and then supersu.zip
5. If TWRP does not automatically reboot your phone (if you unchecked the "reboot when done" box), then reboot to the System; if you left the box checked, then your device will reboot by itself once the zip files have been flashed.
6. Follow the prompts to set up your new ROM or stock Android.
7. Reboot into recovery (TWRP) and make another backup!
8. Want to get rid of the "Unlocked Bootloader!" warning screen? Flashing this file from TWRP worked for me (all the others I tried did not work):
https://forum.xda-developers.com/attachment.php?attachmentid=4065906&d=1488923356
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
fireball0093 said:
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
Click to expand...
Click to collapse
Any word yet on that unlock code?
loociddreemr said:
Any word yet on that unlock code?
Click to expand...
Click to collapse
After talking to their customer support, I never got an email. The next day however I decided to go online to their boot loader page and put my code in, then it worked! The data scrub tool or whatever it may be called that they have I recommend using it too.
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Thanks a ton for the guide
haher2 said:
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Click to expand...
Click to collapse
They are in a subdirectory of the TWRP directory. With the proper drivers installed on your PC you can transfer them via File Explorer. Or, 20 pounds/euros/dollars will get you a 64gb SD card.
3. Flash twrp
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
Click to expand...
Click to collapse
I tried to fastboot boot recovery from the bootoader but it didn't work. I rebooted the phone first and did it with: "adb reboot recovery" in windows.
Overall nice guide, works like a charm, i also flashed the unlocked bootloader warning with a custom logo.bin, no issues here and works like a charm (I flashed it with the stock logo you see when you first bought the phone with a locked bootloader)
Thank you!
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
loonix said:
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
Click to expand...
Click to collapse
Yes and, adding to what you said, you need to re-enable the "Allow bootloader unlocking" and "USB Debugging" in Developer Settings if you failed to flash your recovery as the device expects to be flashed. Else, you'll get a "unable to load kernel" error in the bootloader log and being rebooted again to the bootloader menu.
Great tutorial indeed, thanks a lot. Nandroid backup doesn't worked for me but i'm going on.
Edit - worked after disable sd as internal memory
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
hamelg said:
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
Click to expand...
Click to collapse
In concept, I don't see any reason why you couldn't use TWRP to flash the stock ROM and then fastboot to flash the stock recovery ... or fastboot to flash both (be easier and quicker). The Moto website may have instructions for re-locking.
mkollersms said:
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
Click to expand...
Click to collapse
In a command window use the cd command to change directories. For example:
C:> CD \mytopdirectory\mysubdirectory
Another link to consider about OTA update if you stick with the stock ROM :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
Thanks again.
If your phone is from Verizon Prepaid, Moto will say the device is not eligible to be unlocked. Knowing Verizon, it's not likely to be unlocked later along down the line either. Hopefully someone comes up with a good way to bypass this restriction and install some ROMs.
Does this method work on the Verizon prepaid model, or does it have to be from moto/amazon?
Moto g play twrp IMG file not IMG it's **** IMG file please develop it
Does this works with LATAM version? XT1601?
Thanks :good:
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
dave457 said:
(snipped)
Click to expand...
Click to collapse
Couple thoughts:
1) Please replace every reference of "bootloader" with "boot." Bootloader is entirely different from the boot (kernel). Know the difference if you're going to provide instructions. Using these words interchangeably will cause new users to brick their device because they flashed the bootloader.img when they rarely need to install this. You only flash an image to its similarly named partition on the phone, bootloader does not equal boot.
2) You do not need a custom kernel to get root on Oreo. Your post is misleading. Magisk roots the stock boot image just fine.
3) TWRP will persist between reboots with just the stock boot image rooted with Magisk.
4) TWRP works when you are encrypted. I am unsure why you have a hangup with TWRP and encryption. Are you referring to File Based Encryption which can only be enabled through Developer Options?
5) Why are you making people install a 4 core version of TWRP? If they do not have the BLOD, why force people to use a version of TWRP they do not need?
Sent from my Nexus 5X using Tapatalk
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.[/QUOTE]
Nice thanks man
---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------
jam_09 said:
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
Hey jam_09
I will help you Install 8.1 oreo
First tell me which career are you using? Is your current rom a career specific or a global one check and tell me .. and I'll instruct on what to do further
Click to expand...
Click to collapse
dave457 said:
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
Click to expand...
Click to collapse
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
storo1975 said:
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
Click to expand...
Click to collapse
Yes because later in the process you are going to wipe the data partion to get rid of the encryption this will erase everything on your phone it is like doing a factory rest.
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
I don't know alot about the newer versions of Android like 6 7 8 but I know I read that if you don't root the first time you install twrp then the stock recovery will over write twrp when you reboot. And I also read that magisk modifies the system img in order to hid root. so you can still use gpay and Netflix and pass the safety net check. So I think installing the custom kernel is an extra step that is not nessesary but on the other hand you get certian perks with a custom kernel. Again I don't know much about the newer modding community so o don't know how stable elementalx is. Without installing it I won't know. I have tried dozens of kernels some were spectacular like those from faux others not so much. Also keep in mind to ur technically not on stock rooted version of Android if you have a custom kernel. It no longer is stock software.
Thank you so much for this thread. I was actually about to make one asking how to get back to stock. I used to love flashing the phone all the time, but it got to the point where I never did anything with customization and got bored of it, so I'd rather just be on stock these days.
hi sorry but how to flash the ziP? through TWRP?
INSTALL CUSTOM ROMS USING BELOW INSTRUCTIONS
Note -1. Before Doing These Steps Your device bootloader should be unlocked. otherwise you may brick your device.
2. Install Adb drivers on windows if you are using windows or if you are using linux install adb drivers in linux
INSTALLATION PROCEDURE
1. Download Custom Roms i will provide the links by the end
2. download TWRP
3. Example iam On Stock rom
4. Now i want to Flash Any one of custom rom but how?
> Be ready with Any custom Roms from below example i wilL Flash Pixel Experience Rom
> Be ready with twrp-3.3.0-0
>Turn of your phone and switch to download Mode & Connect phone to pc
4. Now flash twrp using cmd command "fastboot flash boot twrp.img"
5. now your phone boots to twrp
6. now copy the custom rom to phone using twrp dont worry mtp working
7. flash the rom and wait or 5 min for installing
8. now check your slot example iam on Slot A
9. now tap on reboot to recovery now you will again boot in to twrp
10. now change the slot from A to B by tapping reboot ,slot B
11. now you are on slot B now flash gapps for all the roms except Pixel Experience and flash magisk for root if you want using magisk manager zip file
12. now click on wipe & advance wipe now wipe all except system & vendor and tap on reboot system
13. now you people will see pixel experience Boot animation wait for 7 min to boot up and the rom is yours and same method for all custom roms installation
Click here For Custom Roms Links Please Hit Thanks Button If You Understand My Guide. Keep Going...!!!
Thank you
Thanks a lot for spending time on these guides! Made the process simple for even new comers!
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1
FIRST Downgrade to Android 11!
*WARNING*
PAY ATTENTION TO YOUR MODEL TYPE BEFORE READING THE MESSAGE BELOW.
You can follow the guide here for the DE2117: "https://forum.xda-developers.com/t/...android-11-before-installing-lineage.4488485/" and come back.
If you are the on the DE2118 model, you will need to follow this guide instead to convert to the DE2117 firmware and downgrade to Android 11: "https://forum.xda-developers.com/t/...astboot-enhance-gui-tool-for-dummies.4485763/".
Introduction to LMODroid:
Are you somebody who doesn't want people tracking you every day of the week? Are you wanting to be moved away from the Google ecosystem? If your answer is "Yes" then LMODroid is your solution. LMODroid is an FOSS alternative distribution of Android. And based on my usage (as well as a few others' usage) it is stable enough to use as a daily driver on the OnePlus Nord n200!
In this step-by-step guide, I am going to explain as simply as possible how to install LMODroid, while also trying to temper expectations on the application ecosystem, as by design, LMODroid is not the same thing as proprietary Android. Although, with MicroG, some of those proprietary applications can work (but that will not be covered in this guide).
Download:
*In the scenario of the links below being out of date, go to "https://get.libremobileos.com/dre" and grab the latest release and boot image.*
The first step you are going to want to take is to download the boot image named "LMODroid-X-X-XXXXXXXX-RELEASE-recovery-dre.img" with the X's being the version and date of the build respectively.
Second, you will want to download the LMODroid skin itself by downloading "LMODroid-X-X-XXXXXXXX-RELEASE-dre.zip".
Installation Process with warnings:
*! You MUST have your bootloader unlocked, or you will not be able to install LMODroid to your device! If you have not unlocked your bootloader, a Google search will pop up guides. Understand that I will not give support to those who do not listen to this warning. !*
Enable USB Debugging
Phone Configuration of USB Debugging
1. Go to Settings and find "About". Next go within the submenus and find the build number. Tap that build number 7 times. It should say something along the lines of "You are now a developer".
2. Go back to the primary System settings. Select "system" or the closest menu to it. Tap "Developer Options" and go scroll until you find "USB Debugging".
Computer configuration for USB Debugging
1. Download the SDK Platform Tools from here: https://developer.android.com/studio/releases/platform-tools . Afterwards, extract the designated sdk platform tools folder for your platform.
2. Open the extract folder until you see the adb and fastboot binaries respectively.
3. Open a terminal by right clicking in the file manager in linux (or cd'ing to it via terminal) or type "cmd" in the path bar within windows. This will open a cmd prompt.
Reboot to Fastboot and install LMODroid
1. type "./adb devices" and accept the prompt on your phone.
2. type "./adb reboot bootloader" and watch your device reboot into the bootloader.
3. type "./fastboot flash boot "drag the recovery image that you downloaded above here". (If you are in linux... try sudo or SU as default permissions don't let you use fastboot with the downloaded binaries)
4. type "./fastboot reboot recovery (again.. using sudo or SU)
*wait for your device to reboot into the recovery, it will be custom*
5. scroll down to the bottom (and select "Advanced) and then with the volume down screen to "enable ADB" and select the power button briefly to select the option.
6. Scroll back up to "apply update" and select "Apply from adb"
7. Go back into the terminal/command prompt and type "./adb sideload (drag the lmodroid skin file from above [which is lmodroid])."
8. Select "return/enter".
9. Watch your device and the terminal until the process is complete. You will see scrolling text on your device .Nothing to worry about. This is normal. You will also see your computer feeding the file to your device in the terminal. It will look like it is stuck at 47%, but it is not. Do NOT cancel the process. Wait until it says "complete" on your device and returns you to the recovery.
10. Next go to "Factory Reset", select it with the power button, and then select "Format data/factory reset". Let the reset occur.
11. Select "Reboot system now" and watch your device reboot into LMODroid. Congrats! You are all done! Now you simply need to do the set up process.
Have fun with your device!
At the request of another XDA Member, I decided to give you different recommendations of what gapps to use.
My primary choices are usually:
MindtheGapps - The Lineage page has a mirror.
Google apps | LineageOS Wiki
wiki.lineageos.org
Nikgapps
Downloads - NikGApps
NikGapps Website
nikgapps.com
FlameGapps
Downloads | FlameGApps
*Note*
LMODroid is meant to be a Libre version of Android, so why are you installing Google Apps? LMODroid is a slightly modified version of LineageOS. Please take a look at Lineage with Microg if you want the microg variant.
For those who want root, I recommend using Magisk from here: "https://github.com/topjohnwu/Magisk/releases/tag/v25.2". The latest version is indeed 25.2.
~Sprunglicious
You should mention the need to downgrade to android 11 first.
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
I understand LMODroid is based on LineageOS (or forked from it), correct?
should also mention that if they want gapps what ones to use and to flash before first boot
MindTheGapps is recommended with LineageOS. And since LMODroid seems to be based on Lineage that's probably a good bet.
wiki.lineageos.org/gapps And select the download for Lineage 19
Sprunglicious said:
Introduction to LMODroid:
Are you somebody who doesn't want people tracking you every day of the week? Are you wanting to be moved away from the Google ecosystem? If your answer is "Yes" then LMODroid is your solution. LMODroid is an FOSS alternative distribution of Android. And based on my usage (as well as a few others' usage) it is stable enough to use as a daily driver on the OnePlus Nord n200!
In this step-by-step guide, I am going to explain as simply as possible how to install LMODroid, while also trying to temper expectations on the application ecosystem, as by design, LMODroid is not the same thing as proprietary Android. Although, with MicroG, some of those proprietary applications can work (but that will not be covered in this guide).
Download:
*In the scenario of the links below being out of date, go to "https://get.libremobileos.com/dre" and grab the latest release and boot image.*
The first step you are going to want to take is to download the boot image named "LMODroid-X-X-XXXXXXXX-RELEASE-recovery-dre.img" with the X's being the version and date of the build respectively.
Second, you will want to download the LMODroid skin itself by downloading "LMODroid-X-X-XXXXXXXX-RELEASE-dre.zip".
Installation Process with warnings:
*! You MUST have your bootloader unlocked, or you will not be able to install LMODroid to your device! If you have not unlocked your bootloader, a Google search will pop up guides. Understand that I will not give support to those who do not listen to this warning. !*
Enable USB Debugging
Phone Configuration of USB Debugging
1. Go to Settings and find "About". Next go within the submenus and find the build number. Tap that build number 7 times. It should say something along the lines of "You are now a developer".
2. Go back to the primary System settings. Select "system" or the closest menu to it. Tap "Developer Options" and go scroll until you find "USB Debugging".
Computer configuration for USB Debugging
1. Download the SDK Platform Tools from here: https://developer.android.com/studio/releases/platform-tools . Afterwards, extract the designated sdk platform tools folder for your platform.
2. Open the extract folder until you see the adb and fastboot binaries respectively.
3. Open a terminal by right clicking in the file manager in linux (or cd'ing to it via terminal) or type "cmd" in the path bar within windows. This will open a cmd prompt.
Reboot to Fastboot and install LMODroid
1. type "./adb devices" and accept the prompt on your phone.
2. type "./adb reboot bootloader" and watch your device reboot into the bootloader.
3. type "./fastboot flash boot "drag the recovery image that you downloaded above here". (If you are in linux... try sudo or SU as default permissions don't let you use fastboot with the downloaded binaries)
4. type "./fastboot reboot recovery (again.. using sudo or SU)
*wait for your device to reboot into the recovery, it will be custom*
5. scroll down to the bottom (and select "Advanced) and then with the volume down screen to "enable ADB" and select the power button briefly to select the option.
6. Scroll back up to "apply update" and select "Apply from adb"
7. Go back into the terminal/command prompt and type "./adb sideload (drag the lmodroid skin file from above [which is lmodroid])."
8. Select "return/enter".
9. Watch your device and the terminal until the process is complete. You will see scrolling text on your device .Nothing to worry about. This is normal. You will also see your computer feeding the file to your device in the terminal. It will look like it is stuck at 47%, but it is not. Do NOT cancel the process. Wait until it says "complete" on your device and returns you to the recovery.
10. Next go to "Factory Reset", select it with the power button, and then select "Format data/factory reset". Let the reset occur.
11. Select "Reboot system now" and watch your device reboot into LMODroid. Congrats! You are all done! Now you simply need to do the set up process.
Have fun with your device!
~Sprunglicious
Click to expand...
Click to collapse
Nice... I would have simply said "Just do it exactly as you would with LineageOS seeing as it's basically the same"
blueberry.sky said:
You should mention the need to downgrade to android 11 first.
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
I understand LMODroid is based on LineageOS (or forked from it), correct?
Click to expand...
Click to collapse
You are absolutely right. Updated. Thanks!
michaelwaycraig67 said:
should also mention that if they want gapps what ones to use and to flash before first boot
Click to expand...
Click to collapse
Gapp links are now provided! Thank you for your comment!
Does it black screen intermitendly?
if you want to flash for root
chepe263 said:
Does it black screen intermitendly?
Click to expand...
Click to collapse
LMODroid works as well as LineageOS does on this device. It is based on the Lineage builds. So no blackscreening.
michaelwaycraig67 said:
if you want to flash for root
Click to expand...
Click to collapse
Thank you for the link! Would you like me to throw the GitHub link in the post? I can!
Sprunglicious said:
LMODroid works as well as LineageOS does on this device. It is based on the Lineage builds. So no blackscreening.
Click to expand...
Click to collapse
Screen goes black for a few seconds, every few other seconds. Just like LineageOS did.
chepe263 said:
Screen goes black for a few seconds, every few other seconds. Just like LineageOS did.
Click to expand...
Click to collapse
Would you happen to be able to give more detail? Are you aware you must be on the Android 11 firmware before you flash?
Sprunglicious said:
Would you happen to be able to give more detail? Are you aware you must be on the Android 11 firmware before you flash?
Click to expand...
Click to collapse
Yes, I'm aware.
The intermitend black screen issue also happens on LineageOS
chepe263 said:
Yes, I'm aware.
The intermitend black screen issue also happens on LineageOS
Click to expand...
Click to collapse
What steps have you taken to attempt to fix the issue? Or have you only asked questions here?
Sprunglicious said:
What steps have you taken to attempt to fix the issue? Or have you only asked questions here?
Click to expand...
Click to collapse
I read in these forums, to fix issue, LineageOS 20 is needed.
I have a DE2117 with bootloader unlocked.
Using Linux Debian Bullseye
Instructions seem straight forward enough, but want to make sure of a few things before I waste a 1/2 day to only end up where I started (history with past phones and roms)
1. None of the skins on the LMO dre page have a recovery file. You seem to suggest that the boot.img is a recovery image, is that right?
2. There are currently only 4 versions on the LMO dre page. There where several more when I checked a couple of weeks ago.
How can I find out which version of Lineage the LMO version is based on. I came across a reddit tread where people who had upgraded to Lineage 20 a few days ago where having major issues with phone and text. I searched libremobileos.com for an easy to find change log or some reference to Lineage version with no luck.
roy10007 said:
I have a DE2117 with bootloader unlocked.
Using Linux Debian Bullseye
Instructions seem straight forward enough, but want to make sure of a few things before I waste a 1/2 day to only end up where I started (history with past phones and roms)
1. None of the skins on the LMO dre page have a recovery file. You seem to suggest that the boot.img is a recovery image, is that right?
2. There are currently only 4 versions on the LMO dre page. There where several more when I checked a couple of weeks ago.
How can I find out which version of Lineage the LMO version is based on. I came across a reddit tread where people who had upgraded to Lineage 20 a few days ago where having major issues with phone and text. I searched libremobileos.com for an easy to find change log or some reference to Lineage version with no luck.
Click to expand...
Click to collapse
The recovery partitions are inside of the boot.img with A/B partition schemeing.
In terms of the LMODroid dre stuff, I am beginning to notice the same thing. Almost like our device is not being give much of a priority.