Related
hi I'm really interested in doing this
http://forum.xda-developers.com/showthread.php?t=1191141
but i was hoping if anyone can point me over to a very detailed step by step instructions or a youtube video.
he gives you a step by step on how to do it in the thread you linked to....did you not read it?
You have to:
- root
- install a nvflashable rom like Prime
- backup your data (cause the installation will wipe everything)
- download ubuntu rootfs
1) select whether you want to dual boot, and which OS you want as
your default.
2) make absolutely sure that you have backed up your data, everything
past this point is going to destroy your data.
3) run the appropriate sh for the choice you have made in step 1
flash-purelinux.sh for a pure ubuntu setup, this is no android
recovery is ubuntu single user mode.
flash-linux-android.sh for installing android and linux dual boot
with android as the default OS. To boot into linux hold power+vol-down
until prompted on screen to press vol-up.
flash-linux.sh for installing android and linux in dual boot with
android and linux, linux is the default OS, to boot into android
hold power+vol-down until prompted on screen to press vol-up.
flash-android.sh for installing android only, no linux, use this to restore
back to a android only state, this will retain the blobs-be-gone enhancement.
restore-default.sh for reverting to a factory state, this restores the emmc
layout back to how it was before running any of the scripts in this pack.
4) Boot into linux, oem-config will run giving you initial setup. For this
you will need either the keyoard dock, or to use adb.
5) To use the onscreen keyboard you need to attach the usb cable to your
computer and wait for it to boot to the language selection screen.
Make sure not to disconnect the cable from your transformer while you are
using the keyboard during initial setup.
Connect to the device with adb shell. once connected execute "DISPLAY=:0 onboard"
The onscreen keyboard will appear.
6) Enjoy the new life you have with ubuntu on your transformer.
7) Once on the internet you may like to add the tegra ppa
Click to expand...
Click to collapse
I've not installed it yet..but it seems that the passages are well described..
I've read that with ubuntu installation you will lose recovery..
if something goes wrong with the installation which method I have to use to restore my transformer?..
With the help of the ever awesome Team Win, and specifically a developer named Dees Troy we now have a working recovery for the I9505G.
[Update 8/22/2013]: Thanks to ClockworkMod developer gweedo767, the official CWM Recovery for I9505/jfltexx/International GS4 is now fully compatible with I9505G/jgedlte/GS4 GPe. Download either the regular or Touch version here (scroll down to "Samsung Galaxy S4 (i9505)"). Also, official CM 10.x and CM 11 nightlies for I9505/jfltexx are now fully compatible with I9505G/jgedlte, without any modifications.
Here is the guide to get both the recovery and CM 10.x/11 onto the GS4 GPe GT-I9505G:
Assuming you are on a Windows machine.
First we need to install the USB drivers:
Download and install Android SDK tools from here.
Run "SDK Manager.exe" from wherever you installed Android SDK in previous step.
Under "Tools" section select "Android SDK Tools" and "Android SDK Platform-tools". Under "Extras" section select "Google USB Driver."
Click the "Install" button and wait for installation to complete.
Exit the SDK Manager program.
Now unlock the bootloader (according to some people this step may not be necessary):
Boot up device normally, skip setup or do minimal setup - NOTE: you will wipe your phone during this process, so don't go nuts yet on config/installing apps.
Go to Settings --> About Phone
Tap Build Number 7 times, go back to Main Settings Menu and under now shown Developer Options enable USB debugging.
Plug into PC and ensure the phone is recognized.
On the phone accept the footprint signature popup - if it DOESN'T appear unplug/replug USB cable.
Under Command Prompt or Terminal on PC type in "adb devices" and press Enter. Ensure it shows the device and doesn't show "Offline" - if it does repeat steps 4-5.
Under Command Prompt or Terminal type in:
Code:
adb reboot bootloader
and press Enter.
Once in bootloader, on your PC Command Prompt type in:
Code:
fastboot oem unlock
and press Enter. Note that in Linux you will need to run fastboot with elevated privileges, i.e.
Code:
sudo fastboot oem unlock
.
Accept unlock using Volume key, and confirm with Power button - device will reboot possibly a few times, once rebooted and in device you can sign into accounts - REPEAT step 2-3 to re-enable USB debugging.
Now we can get down to flashing a custom recovery:
Un-install all existing Samsung drivers from your PC. This includes Kies program. I can't stress enough how important this step is for avoiding issues with flashing images via Heimdall or Odin.
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download either the latest TWRP recovery from here, or latest official ClockworkMod Recovery for I9505 here and place the .IMG file into the Heimdall folder.
Shut down your phone, disconnect it from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. *NOTE: It is very important to get into the Download mode from a switched off phone. If you are coming from a different custom ROM, do not simply reboot into download mode (via advanced reboot option, or via "adb reboot bootloader" command) as that will cause issues with Heimdall and Odin.
Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" sub-directory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSMnnnn" - basically the S4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY file-name-of-recovery-image-here.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into the recovery.
Now we can flash the i9505's CM nightly:
Once in Recovery mode, connect your phone to USB. You may need to once again install the USB drivers. Just point it to \extras\google\usb_driver\ folder and select "Samsung USB Composite Device".
Perform a backup if you wish (highly recommended!)
Back on the computer, download the CM nightly build (10.x or 11) for the i9505/jflte from here.
Download the latest GApps package appropriate for the CM version you downloaded in previous step from here. (CM 11 compatible gapps, especially those working with new ART VM are currently in flux, but someone put together images of most used ones here).
Back on the phone in Recovery mode perform a full wipe (system, data, cache, and dalvik-cache.)
Flash the files in the following order: 1) CM nightly 2) GApps zip 3) Any other ZIPs you usually flash.
Reboot.
At this point your phone should be booting CyanogenMod. Should something go wrong, follow instructions in donovanbrock's thread to flash back to the stock GE firmware.
Older CM 10.1 ROMs for jfltexx used an outdated syntax for MOUNT command that required an edit to the updater-script, as described here. However, latest CM 10.x and all CM 11 nightlies converted to using a new mount syntax that does not need any modifications.
Working:
Root (superuser) without having to flash or install other packages.
Wi-Fi
Cell data (with LTE)
GPS
Bluetooth
NFC
Vibration
A/C and USB charging
Voice calls
Notification lights
All sensors
Both cameras
Physical and capacitive buttons
Google Apps (Gmail, Play Store, etc.)
Wi-Fi Tethering.
Not Working:
IR Blaster - CM doesn't have official support for it yet. Only apps that access IR modules via root methods will work (e.g. IR Universal Remote.) The functionality has changed from Android 4.3 to 4.4, so it will take some time for CM team to get it working properly. It should make it into CM eventually.
Sometimes when you simply reboot the phone, it gets stuck on the Google logo and doesn't proceed to boot into CM. This seems to be a known issue for the GS4 models and CM, which might have been introduced with SELinux commits. Experts think this is due to a race condition during initial boot-up phases, and are working on a fix. For now the work-around is manually ejecting the SD Card, and immediately putting it back in.
Untested:
Wireless display.
HDMI-out
Thanks and acknowledgements:
Team Win for TWRP recovery, especially Dees_Troy for making it work on I9505G.
CloclworkMod team for the CWM recovery, especially gweedo767 for getting it to work on I9505G.
CM Team for the ROM.
@donovanbrock for the flashing back to stock guide.
@NPS_CA for the bootloader unlock instructions.
Google for Android, and JBQ for AOSP.
WinZip
I claim no credit or ownership of any of the above. The pieces were already out there, I just put them together.
All the linked files are here.
Android SDK tools
Project page: http://developer.android.com/sdk/index.html
Direct download (Windows): installer_r23-windows.exe
Heimdall 1.40
Project page: http://www.glassechidna.com.au/products/heimdall/
Direct download (Windows): heimdall-suite-1.4.0-win32.zip
Support files: Microsoft Visual C++ 2012 redistributables.
Official TWRP recovery for I9505G/jgedlte
Project page: http://teamw.in/project/twrp2/192
Direct download: jgedlte.img
Official CWM recovery for I9505/jfltexx (fully compatible with I9505G/jgedlte)
Project page: http://www.clockworkmod.com/rommanager
Direct download Regular version: recovery-clockwork-6.0.4.7-jfltexx.img
Direct download Touch version: recovery-clockwork-touch-6.0.4.7-jfltexx.img
CM 10.x or 11 for the i9505 (jflte)
Download page: jflte nightlies
Latest GApps package for 4.2.x or 4.3.x (CM 10.x)
Project page: http://goo.im/gapps
Direct download for 4.2.x/CM 10.1: gapps-jb-20130812-signed.zip
Direct download for 4.3/CM 10.2: gapps-jb-20130813-signed.zip
Latest GApps images for 4.4.x (CM 11)
XDA-developers link: http://forum.xda-developers.com/showthread.php?t=2012857
Bonus: 4.3 Camera with Gallery that preserves Picasa Albums sync
Downloads: jb-43-camera-gallery-picasa.zip and jb-43-camera-gallery-picasa_lib.zip
Instructions: Flash both these files in Recovery AFTER flashing the ROM and GApps packages.
Excellent tutorial, thank you. Really happy to see some progress on custom ROMs for the 9505G. Hopefully we will have some custom kernels soon too!
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
donovanbrock said:
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
Click to expand...
Click to collapse
Well, it's not final until it shows up on http://teamw.in/project/twrp2 but it's close enough.
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Has anybody done a successful restore and backup using TWRP? Also silly questions but will the touchwiz roms work on this phone? I was going to do a backup and attempt flashing different ROMs for 9505 or should I hold off?
Thanks all and very nice work
donovanbrock said:
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Click to expand...
Click to collapse
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Chahk said:
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Click to expand...
Click to collapse
Yah buddy.. update your OP. The new files worked flawlessly. :highfive:
Worked for me as well. Very happy to see CM on our GE S4's.
I would like to add this, though: I've performed every step successfully without ever performing a "fastboot oem unlock". In other words, I'm currently running TWRP + CM10.1 without unlocking my bootloader. May be worth noting. Either way, good work everyone.
Thanks for this! Subscribed.
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Not for nothing guys, But why would anyone buy the GE Galaxy S4 when you can just buy the i9505 or the T Mobile variant which is literally what the GE is with a different bootloader. Its also $100 cheaper than the GE. with the GE you are **** out of luck with running touchwiz roms for now and you have to struggle to get CM 10.1 working when its already here and flawless on other variants..
drdingo21 said:
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Click to expand...
Click to collapse
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Chahk said:
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Click to expand...
Click to collapse
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
drdingo21 said:
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
Click to expand...
Click to collapse
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
I heard the LTE bands are different for the phone because of the locked radio and modem. Only the GE edition can operate on both US carriers.
Sent from my GT-I9505G using xda premium
Chahk said:
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
Click to expand...
Click to collapse
Alright. New computer with windows JUST installed.
When I flash the recovery and reboot it doesn't boot into recovery right away. It sits on the Teamwin splash (which it did before) but a reboot gets me into recovery. I still get the password prompt. I re downloaded everything in the OP. Is there somewhere else I should try grabbing the recovery?
---------- Post added at 09:46 PM ---------- Previous post was at 09:16 PM ----------
So I fixed my problems.
I've had my phone since they day they were shipped. I just tried the how to above with out any kind of wipe before hand.
I reflashed the stock recovery then did a full wipe and then wiped the cache again to be sure. Reflashed the attached recovery and all is well! I assume there was something making twrp think there was a password.
thanks for the tutorial!
Can your tweaked installer be used in the same way to make other 9505 ROMs and kernels work on the 9505G?
i had to change zadigto libusb0 (v1.2.5.0) from the default WinUSB (v6.1.7600.16385)
then everyting worked
i know have twrp on my i9505G.
btw if you boot the file using fastboot the touchscreen dose not work but once you flash it it works.
Disclaimer: This guide and the tools included are provided as-is. Testing has been limited and nothing is guaranteed to work. I take no responsibility for lost data, bricked devices, etc. Continue at your own risk, and please read carefully. THIS GUIDE WAS WRITTEN FOR PHONES ON ANDROID 8.1 - MAY NOT WORK ON DEVICES WITH THE PIE UPDATE.
Note that Magisk and TWRP can interfere with downloading and installing OTA updates. At this time the only updates are security patches, so it would be best to make sure all OTAs are installed before starting.
Mounting and decrypting the data partition is still hit-or-miss. If you haven't set up a passcode or password, TWRP should be able to mount it, and you still might be able to even if you have. Magisk will corrupt encrypted partitions and force a factory reset, and TWRP will not be able to help you back things up if Magisk has been installed before disabling encryption. You've been warned.
Guide: Installing TWRP and Magisk on the Visible R2
Tools:
prog_emmc_firehose_8917.mbn - firehose for flashing system partitions
Latest available TWRP zip - contains TWRP recovery image and the necessary files for flashing
fstab.qcom - for removing forced encryption
Patched boot image - for installing versions of Magisk newer than v16.7
Stock firmware - optional, but handy to have in case something goes wrong.
Windows users: QPST/QFIL and the QDLoad drivers (possibly the first set of ZTE drivers as well, but likely not necessary). Installing drivers in compatibility mode for XP or Windows 7 might help resolve issues.
Install adb if you don't already have it set up.
Linux users: qdl source code; the guide will cover compiling and installing it. You'll also want to install adb from your distro's repositories. There is a snap package for qdl, but it doesn't work for the purposes of this guide, so please don't use it.
Part 1: Installing TWRP
TWRP is an easy-to-use, touch-based custom recovery for Android devices, designed to make backups and installs simple and painless. Unfortunately, the installation of TWRP on the R2 is going to be a little less simple and painless; the device's bootloader isn't locked down, but it doesn't support fastboot commands, meaning we'll need to get our hands dirty to flash partitions.
Before starting, it's also worth noting that the current TWRP build cannot always decrypt encrypted data partitions, and the device is encrypted by default. This means that TWRP may not be able to mount or back up your data partition unless it's formatted and forced encryption is removed (see part 2).
To flash TWRP, we need to put the device into EDL mode and forcibly overwrite the existing partitions using an EDL tool and the firehose linked above, which unfortunately requires a PC of some sort. Enable USB debugging on your phone, then follow the steps for your operating system below.
For Windows:
1. Install the Qualcomm driver package. Before continuing, you will need to make sure Driver Signature Enforcement is disabled on your PC; QFIL may have issues communicating with the device if Windows blocks the driver.
2. Install the QPST package, then open QFIL from the Start menu.
3. Select 'Flat Build' under Select Build Type.
4. Extract the TWRP zip to an accessible directory (something like C:\TWRP works fine). Place the firehose.mbn in the same directory.
5. Press 'Browse' under Select Programmer, then navigate to the TWRP directory and select the firehose file.
6. Press 'Load XML'. Select rawprogram_recovery.xml, then patch0.xml
7. Connect the phone to your PC and make sure USB debugging is enabled. Make sure your PC is trusted by the phone for ADB commands, then send 'adb reboot edl'.
8. If everything went well, the phone should have rebooted with a blank screen, and QFIL should be asking you to select a port. Press Select Port, and then choose (hopefully) the only item available).
9. The 'Select a port' message should now read something like Qualcomm HS-USB QDLoader 9008 (COM#). IF it does, simply press download.
10. There should be some output in the status window, ending a few seconds later with a blue Download Succeeded message. If so, you're done, and can restart your phone. If there's a red error message, or the status window seems to be stuck on sending, double-check that your device is registered properly in Device Manager.
11. Once you're done flashing, you can reboot into TWRP by holding down the Vol Up button as the phone reboots.
For Linux:
1. Unzip the qdl zip into its own directory, then enter the directory.
2. Compiling qdl requires libraries that may not be installed. For Ubuntu users, you simply need to run ' sudo apt install libudev-dev libxml2-dev' to install them; people with other distros should know how to use their package manager and may have to find the packages under a similar name. If any other packages are required (errors compiling, etc.), let me know so I can update this.
3. Actually compiling should be as simple as opening a terminal in the working directory and running 'make && sudo make install'. If you get no errors, qdl should be installed and able to run from any location, and the compile process shouldn't take much time at all.
4. Before running qdl, ModemManager needs to be disabled, as it can interfere with accessing the phone in EDL mode. In Ubuntu (and most systemd-based distros) you can ensure that it's stopped by running ' sudo systemctl stop ModemMangager'. If you need the ModemManager service, make sure to restart it when you're done.
5. Extract the TWRP zip to an easily-accessed folder, like ~/twrp, and place the firehose mbn in the same folder.
6. Navigate to the TWRP folder and open a terminal there. Now would be a good time to plug in your phone and enter EDL with 'adb reboot edl'.
6a. If your phone was already connected in EDL mode before stopping ModemManager, you might need to reboot it and enter EDL again.
7. If you're in the same directory as the TWRP files, you should be able to start flashing by running 'sudo qdl prog_emmc_firehose_8917.mbn rawprogram_recovery.xml patch0.xml'.
8. If everything's good, you should see some output on your screen, and the phone should reboot momentarily. If the command finishes without output, ModemManager or something similar may have interfered. Make sure ModemManager is stopped, reboot your phone into EDL mode again, and try again. If it hangs at Waiting for EDL device, you're not running the program with admin privileges or your phone isn't in EDL mode.
9. Once the process has finished and your phone has rebooted, you should have TWRP installed. Boot into it by holding Vol Up while rebooting.
That's it! Verify that TWRP is working as expected by doing some test backups and restores, etc. Note that TWRP builds for this device are still sort of experimental; decrypting the data partition may not work for some users, and keeping data encrypted while trying to flash Magisk will not work - you will need to wipe and decrypt the device. If you're satisfied just with TWRP, there's not much else you need to do. If you want to run Magisk or decrypt your device for other reasons, keep reading.
Part 2: Removing Forced Encryption
By default, the device encrypts the data partition without input from the user. This is not ideal, and even if TWRP can decrypt and mount your data partition, from my experience Magisk's init process apparently gets things wrong and tries to write to data before its decrypted - whether that's actually the case or not, the fact of the matter is that Magisk has corrupted my data partition every time I've tried to install it while data was encrypted.
DO NOT flash any zip that removes dm-verity and force encryption - these modify the boot and recovery partitions, and the stock kernel doesn't like the way they do it. If you've flashed the patched boot.img first then you'll at least be able to boot to your system partition afterwards, but it'll still nuke recovery even with a custom kernel installed on it. If you're still using the stock boot.img, you'll get boot loops and won't be able to access recovery; your only choice is to enter diagnostic mode, and reflashing anything from that point is a gigantic pain in the ass, so please, just don't. If you feel the need to do it regardless, please please please reflash your boot and recovery images before rebooting.
Counter-intuitively, the quickest and most painless way to stop the device from force-encrypting itself is to modify the fstab on the vendor partition - the boot partition has no fstab files, and the ones in the TWRP recovery image are already set to make encryption optional. Place the fstab.qcom on the phone's microSD card (internal storage will work if you don't have one, as long as TWRP can access your internal storage; if not, use adb push/pull rather than the below commands), boot into TWRP, and adb shell into your device by USB; if done while in TWRP, you should have root permissions. If your PC doesn't see your phone as an ADB-ready device, go to Mount settings in TWRP and tap on the option to disable MTP; after confirming that ADB works, feel free to re-enable MTP. Once ADB is working, run the following commands:
Code:
mount /vendor
cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak
cp /external_sd/fstab.qcom /vendor/etc/fstab.qcom
chmod 644 /vendor/etc/fstab.qcom
umount vendor
.
That's the simple part - you've replaced the fstab on the vendor partition with one that tells the device that encryption is optional, and backed up the original to your microSD as fstab.qcom.bak, just in case. Now you need to actually remove the existing encryption, which will wipe all the user data from the device. If that hasn't scared you out of continuing, read on.
While we're still in TWRP, we need to go to the Wipe menu. From there, we need to Format Data. It'll give you warnings in a scarier color than I did, but you'll have to type yes and continue regardless. Once that's done, hit the back button a couple times before rebooting. Do a standard factory reset, then reboot.
From there, it may take a couple tries for the device to boot normally as it reformats and repopulates the data partition. If you find yourself stuck on a black screen, reboot again, and if it keeps happening, boot into TWRP and then reboot to System from the reboot menu. Eventually, you should be able to get back to the device setup screen, and depending on your security settings beforehand, you may be prompted to enter your PIN, password, or Google account information.
From here, you should be able to mount, backup, and restore your data partition in TWRP without any issues. If you want to go further and root your device, keep reading for the Magisk guide.
Part 3: Any Magisk You'd Like
Note: Magisk and encrypted data partitions do not play nicely together. Follow through Part 2 first, or you'll have headaches.
ZTE's kernel has a custom SELinux plugin called policyproc, which in short doesn't play nice with a lot of things that modify what happens during the kernel's startup sequence. Unfortunately, modifying the startup sequence is what Magisk does best, and versions of Magisk past v16.7 don't play well with the stock kernel.
If you're fine with v16.7, you can download the zip from its Github release page and flash it through TWRP. However, it doesn't support current versions of Magisk Manager or the uninstaller zip, and naturally it doesn't have all the features of newer versions.
This is where the patched boot image comes in. Basically, it's the stock kernel, rebuilt with policyproc disabled, stuffed into the stock boot.img and replacing the original kernel. It's not entirely perfect as ZTE deliberately left out bits of the source, but even working around that, the kernel seems to run fine after nearly a week of testing on my own device. Still, if you run into any issues that don't show up with the stock kernel, please let me know.
So. you can take that patched boot image and install newer versions of Magisk whichever way you'd like. The default method would be to use TWRP to flash the patched boot image, then flash the latest Magisk zip (v20.1 at the time of writing). Alternatively, you could put the patched boot.img on your microSD or internal storage, install the Magisk Manager app, use it to patch Magisk into the patched boot image, then use TWRP to flash the patched-patched-image to the boot partition. Either way should work fine, and honestly I'm hoping if you've made it this far you don't need further instruction on how to get Magisk installed.
Note that on the first reboot after installing Magisk, the phone may reboot again before loading the system normally. I assume this is standard practice for initializing Magisk, but honestly I have no idea.
With that, you've done just about everything you came here to do. If you still feel like tweaking and possibly bricking your phone, however, scroll on down to Part 4.
Part 3.5: Updating Your Magisk Install
When a Magisk update is available, the Magisk Manager app will generally push a notification to you. Letting the manager handle the upgrade is a good way to get bootloops, unfortunately; upgrading requires re-patching and re-flashing the boot image, and most apps running in system mode seem to handle the task poorly on the R2. If you want to update to a newer version of Magisk, it'd be best to reboot into TWRP, flash the 'clean' Magisk-ready boot image, then install the zip for the version of Magisk you want to update to. You don't need to uninstall previous versions of Magisk to do this, and it should be doable even if a previous Magisk upgrade left you stuck in a boot loop. Note that if you previously told the Manager to 'hide' itself, you may end up with two Manager apps after the update; it should be safe to remove either of them, although the one with the Magisk Manager name will need to be re-hidden if you choose to keep it.
Part 4: Going Even Further Beyond - Project Treble and You
Google requires that all Android phones releasing with Android Oreo or newer must support the Treble framework: generally speaking, anything that's 'stock' Android lives on the system partition, and anything manufacturer or carrier specific exists on the vendor partition. This has allowed for developers to create generic system images, or GSI, consisting of particular Android system partitions that should run on a variety of Treble-enabled devices. And wouldn't you know it, the R2 launched with Oreo, and you've got a couple handy methods of writing system images to your device, through TWRP and EDL flashers.
So, does that mean the R2 supports these GSIs? Not really! Honestly, it's more that it's up to curious people to find out. I've been able to get phhussons's Oreo image working, but that's a bit boring on a device that supports Oreo out of the box. A couple more highly modified Pie builds failed to boot properly, either hanging on their splash screen or crashing the display manager before getting through setup.
There's also the fact that they're generally only distributed as sparse system.img files, something I had trouble flashing with QFIL, and up until about 18 hours before this guide went live, the only TWRP build I had for the R2 could only write images to the boot and recovery partitions, not system, so writing them meant I had to decompress them to a standard EXT4 image and then flash them with QFIL, which wasn't a lot of fun to mess with. In short, testing's been pretty limited, but this build of TWRP should make it much easier for anyone to flash whatever image they'd like. If you feel like being a guinea pig, we'd all love to hear the results! If you want to test, you should look for A-only, ARM64 images.
Questions and Issues
My phone is bootlooping after leaving recovery!
If you haven't messed with system partitions in a way that might cause a bootloop, reboot to recovery and try to boot to system from there. If it continues, reflash your boot image (and Magisk afterwards, if necessary, removing the extra Manager app that might pop up in your app tray if you've got Manager disguised in its settings).
I can't access ADB or MTP from recovery.
It happens sometimes, especially in Windows; just toggle MTP on/off from inside TWRP, or unplug and replug your USB cable.
My phone says I need a factory reset, but TWRP just reboots.
This generally happens if something messed with the encrypted data partition. Do not tap the factory reset button on your phone; instead, power off entirely and manually reboot into TWRP by hilding Vol Up while booting. Perform a factory reset (and format data if necessary) from there, then reboot.
(to be populated)
Credits
@deadman96385 - for uploading the tools that made this possible and the stock ROMs that saved my ass more than a few times
@famewolf - for feedback on what did/didn't work in the last guide
@asderdd - for his Axon 7 kernel work which I shamelessly copied to get Magisk working
Anyone who's contributed to Magisk or TWRP over the years, and the maintainers of the moto e5+ device tree for TWRP since I used most of their branch.
Sources
Kernel source, specifically the tree used for the Magisk patch
TWRP device tree
@FEGuy
Attempted to flash the new twrp via zip....acted like it worked but when I when to install section only boot and recovery were options....so I installed the twrp image itself to recovery....rebooted back into recovery and got a black screen. Additional attempts to go into recovery did same thing. I'll attempt to use the flashify app under factory rom to restore previous copy of twrp. It should work as I had magisk going...I think.
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
FEGuy said:
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
Click to expand...
Click to collapse
Always possible I hosed something....I grabbed the img of the previously good twrp and flashed it via flashify app...said it worked but when booted to recovery got same black screen. I'm about to experiment with the usb drivers you mentioned vs the ZTE USB ones in the op...they conflict with each other so uninstalling old ones.
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
FEGuy said:
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
Click to expand...
Click to collapse
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
---------- Post added at 02:01 AM ---------- Previous post was at 01:48 AM ----------
famewolf said:
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
Click to expand...
Click to collapse
I tried dd if=twrp-3.3.1-1-z5151v.img of=/dev/block/bootdevice/by-name/recovery and did same with new signed one. I still get black screen when recovery "loads". At this point I'm going to have to get something figured out with qdl or qfil.
Yeah, I wasn't sure if dd was going to work or not.
Try the QDLoad drivers again in Windows, make sure that the device is using them. If it's not showing up as a COM port in device manager, force it to use the proper Qualcomm driver, which on my system installed to C:\Windows\system32\qcusbcer.sys - I don't know if that installed with the QDLoad drivers or with QPST/QFIL itself.
As for qdl, I don't know; it's been hassle-free for me, for the most part. If you're sure you're in EDL mode and not diagnostics or something, an output from lsusb might help diagnose the issue. If the debug flag isn't providing useful info, might as well try it without. I don't know if there's services other than modemmanager that might interfere with qdl, it could depend on distro.
EDIT: I'll also preemptively warn against trying the TWRP app to flash; it'll do about as much good as flashify.
Will tackle it "later" in the morning. Thanks for the quick followup. I might see more clearly in morning when not so frustrated with it. I swear I haven't had this many issues with getting twrp installed in a long time.
*update* Ok so I lied....I completely recompiled qdl from https://github.com/andersson/qdl and it's working as expected..I used it to flash the original twrp. I then used that twrp to flash the twrp-signed.img and rebooted back into it with no issues.
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
The Treble pie loaded ok...I did do a factory reset so data would not conflict..it did do one reboot before loading normally. See screenshots.
The First 4 are from when it was initially installed. The later photo's I had added gapps, a few apps, snapped a picture to use as wallpaper and various other minor things. I found it to be faster under treble pie than it was with factory oreo. I haven't found anything that didn't work yet on it.
Launcher: Evie Launcher
famewolf said:
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
Click to expand...
Click to collapse
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I tried the current installer which failed. I didn't locate the 16.7 uninstaller.
*update* I did finally locate the 16.7 Magisk Uninstaller.
FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I also installed open gapps pico pie amd64 version on top of the pie rom without issue. I have magisk 16.7 working with treble without issue so maybe it was just the newer versions that had issues?
My 2nd R2 (You are a bad influence) arrived today. Anything you need tested on a stock model? Here's hoping qdl/qfil cooperates 1 last time.
When you were patching the kernel did you see anything that was keeping the phone in LTE only mode for calls? When I get a minute I'm going to put my t-mobile sim into the R2 and see what it will do under the pie rom but since it's still using same kernel I wondered if that would be an issue. We know on the stock rom all calls have to use VOLTE.
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
FEGuy said:
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
Click to expand...
Click to collapse
Had a couple of thoughts...a quick and dirty method to provide "flash and go" rom's might be to do a nandroid of just system or maybe system and boot for whatever rom and make that available for download. I also know there are methods to convert a nandroid into a flashable zip although I haven't done it before. This was more a thought for folks wanting to go to b12 that already had twrp...simple enough for an existing b12 user to back up system. I have verified swapping between nandroid pie vs stock oreo works ok (assuming you are restoring the right data for each). Also the fingerprint "images" continued to work fine after a restore.....on a previous device when we did a nandroid restore we would have to delete the file storing pin/fingerprints as they wouldn't let you into the phone until re-recorded. It also worked if you remember to turn those OFF before doing the backup....wasn't an issue with the R2. The phone is noticeably more responsive on pie than it was with stock oreo. I'm curious whether you found that to be the case with treble oreo?
Oh minor annoyance....I changed the device id to z5151 which is what it showed under stock but when doing an adb shell the command line is "phhgsi_arm64_a:/" Do you know how to change that? This will change it temporarily till next login: https://stackoverflow.com/questions/33069161/how-to-change-adb-shell-prompt-name-before-the-mark
You could try using setprop as root to set ro.build.product or ro.product.device back to Z5151, or manually edit the build.prop; beyond that, I don't know of a simpler way.
I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.
thanks!!!!!!!!
rangolizardy said:
I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.
Click to expand...
Click to collapse
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.
rangolizardy said:
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.
Click to expand...
Click to collapse
Posted for rangolizardy: http://mega.nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Any other important tweaks anyone has made to the treble pie image?
Factory Wallpapers are here: https://forum.xda-developers.com/showpost.php?p=79011562&postcount=2
I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0
Requirements​install ubuntu on your pc
Download This lineage image, if you want google apps download BVG if you dont want google apps download BVS Make sure to download arm64 not a64 note if you want a pre-rooted lineage OS choose lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
Download This GSI make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz or system-roar-arm64-ab-vndklite-vanilla.img.xz These are pre-rooted GSI'S
And Download This FILE We will need it later
==============================================================================================================================
BEFORE WE PROCEED IM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE
extract everything in the same folder right click open in terminal
reboot into download mode voulme up + power
Ok now we"ll need to install heimdall on your ubuntu machine by opening the termanil and typing sudo apt install heimdall-flash
type in the terminal heimdall flash --SYSTEM sysnull.img
system will reboot, go into download mode again
now write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img
or if you downloaded the one without GAPPS Write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-vanilla.img --VBMETA avbnull.img
Boot into stock recovery and do a factory reset
install Termux and download this TWRP image and rename it to r.img
open Termux and type su
Now Write dd if=/sdcard/Download/r.img of=/dev/block/bootdevice/by-name/recovery
if you saved the TWRP image to your internal storage type dd if=/storage/emulated/0/Download/r.img of=/dev/block/bootdevice/by-name/recovery
ok now reboot into TWRP (power + vol up)
wipe dalvik art, cache, system, data, cache
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click select storage (click on internal storage)
Click on install image
and now just flash LineageOS and make sure to choose system image
Thanks to @Hex_101 For the rooting tutorial !!
Edit: I Stopped Using The Phone and Switched To An Iphone 14 Pro Max
works fine
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Edit: Solved
I entered the wrong Download Mode (step #2), I thought the Download Mode was the one when I'm supposed to press Volume Up on the same recovery mode to unlock the bootloader (pressing volume up & down together and connecting the cable), turns out I'm supposed to enter Download Mode from the Stock Recovery (pressing volume up & power button)
And probably because I used Ubuntu on a VM
Wurd4Wurd said:
works fine
Click to expand...
Click to collapse
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
jfr07 said:
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
Click to expand...
Click to collapse
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
jfr07 said:
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Click to expand...
Click to collapse
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Wurd4Wurd said:
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Click to expand...
Click to collapse
Yes I've overcome this problem since my second post where my phone keeps rebooting
Wurd4Wurd said:
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
Click to expand...
Click to collapse
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Sinshro said:
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click to expand...
Click to collapse
jfr07 said:
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Click to expand...
Click to collapse
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Wurd4Wurd said:
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Click to expand...
Click to collapse
I thought I made mistakes throughout the process so I tried re-doing everything from the beginning and it finally works without storage issues. Thank you so much for your help, especially pointing out the correct OS image, such a lifesaver
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
jfr07 said:
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
Click to expand...
Click to collapse
Good to hear, I was so worried that it will also happen to my a20s.
Wurd4Wurd said:
Good to hear, I was so worried that it will also happen to my a20s.
Click to expand...
Click to collapse
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
jfr07 said:
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Click to expand...
Click to collapse
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
aerglass said:
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
Click to expand...
Click to collapse
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Wurd4Wurd said:
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Click to expand...
Click to collapse
sorry if itype bad (i am typing one handed because my right hand broke)
i installed it on to a broken (that has no wifi or bluetooth, idk why) samsung galaxy a20s from latin america (SM-A207M/DS) which seemed that it was going to no work but it worked perfectly, i have some problems with lineage though, i could fix the phone but i do not care so whatever. I have another samsung galaxy a20s that works fine.
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
minakriss said:
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
Click to expand...
Click to collapse
Did you flash the stock system.img via TWRP? I can't seem to do the same. If you have the zip that you flashed, can you upload it here? It means a lot to me. Thanks
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
minakriss said:
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
Click to expand...
Click to collapse
A207FXXU2BTH2 Binary 2, Android 10 and region is the Philippines SMA
i need the non-superuser lineage 19.0 and it does not exist on https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/