==================LONG NOOB WARNING============================
Hi!
Recently I've just installed Lineage OS 18.1 on my phone
Phone: LG G2 (international[D802])
Current build is: lineage_d802_userdebug 11 RQ2A.210405 cd6fb8d05d ( lienage os 18.1 2021.04.29 Nightly )
So first I've switched from the original os (Android 5.0.2) the steps I've done:
1.: Rooted my phone via LG One-click Root what I found on the internet (https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0)
2.: installed TWRP recovery with TWRP manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en), (https://www.gregtwallace.com/lg-g2/g2-twrp/?version=3.3.1-0#download-section)
3: downloaded Lineage Os build 18.1 20210422 and BitGapps
4: Installed both of 'em.
After these, I used my phone and I was happy, (i switched the recovery to lineage as it came on screen I didn't know I'll need twrp in the future) but just as soon as the newer (my current) build came out it notified me, and I started downloading it through the built-in updater (settings-system-updater)
First, it appeared to installed normally, so I basically left it to do its thing, but it turned out it won't boot (Couldn't load android), so I tried to install it again with ADB via built-in lineage recovery, it said it was successful, however, it didn't load so I formated the data within the recovery, and it immediately booted into the system. Now comes the part which i need help in (i wrote all this down to get a better view of the problem), so after i booted into LOS i noticed, that the gapps are gone.
I thought ok, it is how it is, then let's try and install them. So i downloaded the minimal ADB and fastboot program which as far as i know is enough to do simple installs. So i fired it up, went into lineage recovery and clicked install update with ADB (or however it is called, can't remember that ), and i wrote in the console ' adb sideload <bitgappsxversioncan'tremember>.zip' and it started to install but got me with:
"finding update package...
verifying update package..
update package verification took 2.7 s (result 0) .
Installing update...
***********
BiTGapps R25 Installer
************
-installing toolbox
-mounting /system
!cannot mount. Aborting----
-unmountig partitions
! installation failed
E: Error in /sideload/package.zip (status 7)
"
I took my time to make sure it's the right version (it is arm as my device run by arm, and it is R as Android 11 so i think it is for my os)
I'Ve thought ok, then maybe i'M doing something wrong, so why not just wipe all and restart again?
I noticed i have no root permission, so i have to get one, now as i know (correct me please if i'm wrong) LG oneclick root is for Kitkat and lollipop and stock firmware (?), so i looked up the internet and saw that lineage has removed the super user (root) option from the developer and have to install and addon (su package) to readd it. i thought, aight' let's do it then, i downloaded it and tried again via sideload on adb and from internal storage too (addonsu-16.0-arm-signed.zip), but the result was similar to my previous attack with gapps except it said
"
installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symbolic links encountered
E: Error in /sideload/package.zip (status 7)
"
Apart from these Lineage runs great, except hbo go wont work for some reason (chromecast library cant be reached or so), but I'm okay with that, and a huge thank you to the developer for the os!!
so my questions are:
Either way:
-can I root it somehow to be able to install TWRP, and start everything over and get Gapps?
- Can I install Gapps somehow without reinstalling recovery?
-in the official TWRP app there's no d802, which one should i download, or even should I download any different model (like American or d800,d803, etc.)
Apart from the previous question is there a way to upgrade lineage without losing data? (i read somewhere that sideload should be my choice is it true?)
Thank you if you've read this far, if you know any solution for me please share with me, I'd be really grateful!
have a nice day!
Related
Hello friends, I am trying to install Magisk on a Galaxy s4 gt-i9515, non-rooted, with TWRP recovery device.
I tried both methods described in the official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both tries failed. I will now explain in more detail what I've done.
Before, note that I have a TWRP recovery of the state before flashing any zips/boot.img s, so I am constantly going back to the previous state which passes safetynet.
First try:
I simply took the magisk-v14.zip file and installed through TWRP. The installation had no errors and in the end TWRP claimed "success". TWRP asked me to reboot now.
I clicked on "Reboot", and then TWRP told that "My device is currently not rooted" and asked if I want to install root or reboot anyways. I rebooted anyways (I didn't let TWRP install his own root).
When the device boot up, I got into magisk manager, but sadly it was written that I am not rooted, and I don't have a magisk installed. Now, it also failed to pass safetynet.
At this point I used my Backup and got back to the state which I could pass safetynet (I've checked it again to make sure).
Second try:
I got the boot.img of the stock firmware I am currently using (I recently flashed this firmware, so it has to be the right boot.img).
I got into Magisk Manager and patched the boot.img. Magisk patched it into a file called "patched_boot.img.tar".
I got into download mode on my device, and flashed the .tar file via ODIN (AP option, ODIN version 3.12.3).
The device rebooted after the installation was "complete" according to ODIN: <OSM> All threads completed. (succeed 1 / failed 0).
When the device booted up, I entered the Magisk manager, and still, no root + no magisk installed. This time tho, it passed SN.
I used my backup again.
Now I am stuck. I really don't know what can I try anymore. Please suggest me ideas.
Up. I still need answers.
i have mnanaged to install latest stable version of magisk using latest twrp 3.1.1.0, and root management is in function. however, i cannot install any magisk module, tested xposed api21 but it does not install, also greenify4magisk still nothing to be noticed, unfortunately as there is yet no response i suppose its a lost cause, well lets just root manually supersu or things like that.
hi, Samsung S4 i 9505 I have not solved with Magisk and I don't even try "patched_boot.img.tar" the problem in it is apk and not the file it TWRP starts I remember apk EdXposed 2 years ago there were failures I thought about installing stock firmware/Rom with Frja Tool we talk about android 10/11 is android 5.0.1 I think there is only one way is SuperSu this root does not pose problems there is a saying: the more cooks around a dish, the more they ruin it"
I was able to install Magisk v24.3 today on my Galaxy S4 Mini LTE (GT-I9195) using partially the "Patching Images" method and TWRP 3.2.3. I had Magisk v23 installed but since a couple of weeks ago it kept crashing. So, I did the big mistake of uninstalling it to update to the latest version. It costed me half a day around this.
I could not flash zips in TWRP recovery (it always failed with Updater process ended with ERROR:1)
1 - Get a copy of the boot.img (for this step I had to find the installation file of my ROM. I did not know for sure which was it since it was installed 2 years ago. I have an AOPK based ROM and all the files from their website are not available anymore. All I could find was an older one on androidfilehost "aokp_serranoltexx_pie_unofficial_2020-01-18_1053.zip". Uncompress this zip to get the boot.img file.
2 - Copy the boot.img to your device filesystem.
3 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash boot.img, reboot
4 - Download and install the latest Magisk v24.3 apk
5 - Press the Install button in Magisk app (this means pressing the second “Install”, the one on front of App.)
6 - It should ask you to choose “Select and Patch a File”. Search and select the boot.img
7 - If all goes well, it should create a file named magisk_patched_[random_strings].img
8 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash magisk_patched_[random_strings].img, reboot
9 - Reboot and confirm in Magisk app if it says “Installed 24.3 (24300)“.
Now I get a warning "Your device needs additional setup for magisk to work properly... reboot" when entering Magisk, but it seems to work fine.
I have a bottle of champagne saved for the day when windows laptops are miniaturized and android is discontinued from the market. Bootloaders, recoveries, ramdisk, getting root, knox, odin, oem unlockings, CSCs, APs, customs kernels, adb, vbmeta, adoptable storage, se policies, fastboot modes, download modes... damn. They couldn't make it more complex if they tried.
When I install an update from the Lineageos system this reminds Magisk and the TWRP, and if I install from TWRP you always have error "signature mismatch" even if I downloaded the same update or other updates.
Install update via lineage updater, then boot TWRP Flash magisk and twrp
an expert computer friend of mine said that there should be a configurable device setting, perhaps in the developer settings, to remove the twrp installation which should consequently also not remove magisk. does anyone know the method? even if it is difficult I can do it, or even a method to install via twrp the system that should not give problems whatsoever.
Could someone please help me to put a custom rom on my Lg G3 D855TR, 2 gb ram / 32 storage?
My version is: Android 5, v20n-global-si
Kernel stock: 3.4.0
What guide do I have to read to do that?
Thanks
Olofaiolo said:
Could someone please help me to put a custom rom on my Lg G3 D855TR, 2 gb ram / 32 storage?
My version is: Android 5, v20n-global-si
Kernel stock: 3.4.0
What guide do I have to read to do that?
Thanks
Click to expand...
Click to collapse
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Zymomonas said:
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Click to expand...
Click to collapse
Thank you very much, I will try this.
Initially, I've installed TWRP without the official TWRP App and I managed to install LineageOS 16 as CustomROM. But as I installed the official TWRP App later, strange things happened: Suddenly, I wasn't able any more to boot the system, and only the start of the CustomROM showed up, but then the phone automatically rebooted into recovery (TWRP).
So maybe, it will be safer not to install the TWRP App on the d855TR. TWRP without the "Official TWRP App" is doing fine (after re-installation).
Zymomonas said:
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Click to expand...
Click to collapse
I can confirm this works with no problems. Already updated to 3.5.1
I've checked the .xml file and the lines which is described in the guides to fix this error does not exist, there is not kgagent.
I've installed a custom rom and opengapps, magisk, microg, supersu, all these flashed through twrp.
https://forum.xda-developers.com/android/general/phone-locked-payment-service-uninstalled-t4018177
SM-J530F D/S
Tartarus v.2 rom android 9.0
3.3 Twrp
Whilst waiting for help I'm going to try installing a samsung pay.apk through adb sideload. Going to try on different pc as here I get the closed error as I try to push or do adb usb, adb root or whatever.
As a side note I've noticed that I'm having issues with installing magisk, which seemingly requires to be reinstalled if installing multiple things like microg, patcher, which throws error about android pie not being supported, etc. It says that the boot image incompatible or something. Also had issue with supersu saying that the binaries are or occupied by something else whilst inside the os. Trying to copy files in file manager (twrp) throws error 1.
Edit: no success.
ClownWorld said:
I've checked the .xml file and the lines which is described in the guides to fix this error does not exist, there is not kgagent.
I've installed a custom rom and opengapps, magisk, microg, supersu, all these flashed through twrp.
https://forum.xda-developers.com/android/general/phone-locked-payment-service-uninstalled-t4018177
SM-J530F D/S
Tartarus v.2 rom android 9.0
3.3 Twrp
Whilst waiting for help I'm going to try installing a samsung pay.apk through adb sideload. Going to try on different pc as here I get the closed error as I try to push or do adb usb, adb root or whatever.
As a side note I've noticed that I'm having issues with installing magisk, which seemingly requires to be reinstalled if installing multiple things like microg, patcher, which throws error about android pie not being supported, etc. It says that the boot image incompatible or something. Also had issue with supersu saying that the binaries are or occupied by something else whilst inside the os. Trying to copy files in file manager (twrp) throws error 1.
Edit: no success.
Click to expand...
Click to collapse
1. Samsung apps wont work on AOSP.
2. Try flashing the base ROM with a base firmware that doesnt have any carrier like vodafone etc.
NecromancerViper said:
1. Samsung apps wont work on AOSP.
2. Try flashing the base ROM with a base firmware that doesnt have any carrier like vodafone etc.
Click to expand...
Click to collapse
Are you saying that tartarus v.2 is a carrier dependant rom? Any suggestions of stable / bugless rom?
I've tried several, some sound issues, others soft brick/crash, and others thread topic.
Context
It's been a year since I last updated (from the last update of lineageos 18) because each time I ran into problems setting up magisk, although I admit that the main culprit was the one between the screen and the chair. Overall, the year of use was smooth, but it was getting worse so I updated and fortunately I didn't lose any data.
Now my problem is the installation of Magisk and I prefer to have a guideline without the need to reset my phone like every time because I made a stupid mistake.
-----------------------------------
I am root but I don't have Magisk installed only the application.
According to my memories, I went to the Magisk app being still on my phone and patched "boot.img" from the same version as my Lineageos build and then did "fastboot flash boot (path of patched file)" from my pc (I put the file there).
After, I restart but I get a loop with the Lineageos logo which after several seconds of animations restarts the phone to start again in loop.
Fortunately, if I sideload my current version of Lineageos the loop stops, but I still don't have magisk installed.
From this point on I'm a bit stuck as to what to do, at least being sure I'm not making a mistake. (I obviously tried a second time but the same thing happened).
I think I remember TWRP but a year ago I installed the wrong version and had to reset my phone to factory state. If I need this, please tell me exactly which version I need. (from here ? TWRP for OnePlus 6 & 6T if so do I only have to flash boot the image or am I missing a step?)
Could someone please tell me what I should do? I searched but couldn't find an answer.
Nevermind. I corrupted my data but the answer was a sideload installation (rename magisk.apk to magisk.zip, then adb sideload pathtomagisk.zip )
I did something in addition (I don't know why) which added a new problem then etc.