So i installed TWRP, SUPER SU, custom ROM (linageOs), now i need GApps but here i have a problem. I placed a zip folder that i need to install while android was turned ON, i went to TWRP and i can`t find this zip file.
I don`t have access to files while in TWRP recovery (pc says that device stopped working or has been plugged out).
TWRP says that internal storage is 0MB, but there are folders like acct, boot, cache etc...
payer0 said:
So i installed TWRP, SUPER SU, custom ROM (linageOs), now i need GApps but here i have a problem. I placed a zip folder that i need to install while android was turned ON, i went to TWRP and i can`t find this zip file.
I don`t have access to files while in TWRP recovery (pc says that device stopped working or has been plugged out).
TWRP says that internal storage is 0MB, but there are folders like acct, boot, cache etc...
Click to expand...
Click to collapse
Update your recovery. You are using an old version of TWRP. Use the one in the opening post of LineageOS thread or latest OrangeFox and you will be able to see your internal storage.
SuperSU is also outdated. Use Magisk instead (latest official version should be 17.1).
Flash ROM, flash GApps, flash Magisk and reboot your phone
Noter2017 said:
Update your recovery. You are using an old version of TWRP. Use the one in the opening post of LineageOS thread or latest OrangeFox and you will be able to see your internal storage.
SuperSU is also outdated. Use Magisk instead (latest official version should be 17.1).
Flash ROM, flash GApps, flash Magisk and reboot your phone
Click to expand...
Click to collapse
Worked, thanks
Thanks man you saved time and energy
Related
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.
I installed the sdcard version of CM11 from iamafanof website , including the sd card version of Gapps but I don't see the playstore. It looks like Gapps are flashed okay in TWRP...I get no errors, but I get nothing when I boot into Android.
Help appreciated.
chimpknowskungfu said:
I installed the sdcard version of CM11 from iamafanof website , including the sd card version of Gapps but I don't see the playstore. It looks like Gapps are flashed okay in TWRP...I get no errors, but I get nothing when I boot into Android.
Help appreciated.
Click to expand...
Click to collapse
The Playstore should be there if Gapps package was installed.
Check to make sure that you used the sdcard (and not the emmc) version: gapps-kk-20131208-no_set_metadata_sdc.zip or pa_gapps-modular-mini-4.4.2-20131230-signed_sdc.zip.
Also, iamafanof's guide says you should install and boot CM11, then go back to recovery to install Gapps.
Which version of TWRP recovery did you use? Note that CM11 requires TWRP 2.6.3.0 or later.
digixmax said:
The Playstore should be there if Gapps package was installed.
Check to make sure that you used the sdcard (and not the emmc) version: gapps-kk-20131208-no_set_metadata_sdc.zip or pa_gapps-modular-mini-4.4.2-20131230-signed_sdc.zip.
Also, iamafanof's guide says you should install and boot CM11, then go back to recovery to install Gapps.
Which version of TWRP recovery did you use? Note that CM11 requires TWRP 2.6.3.0 or later.
Click to expand...
Click to collapse
2.6.3.1. I installed the mini version ...and made sure it was the sdc. It boots fine into Android. I even get a dialog box saying x of 9 apps updating after I flash the pa_gapps sdc.zip file. But when it boots up, I don't see the playstore . I can surf then net on wifi and everything else looks okay.
i would like to try cwmbut i cant find the latest sd bootable version.
Do the apps show up in Settings->Apps menu?
If so, did you look for these apps on the App Drawer (hit the circle with 6-dots on the navigational bar at the bottom of the screen)?
digixmax said:
Do the apps show up in Settings->Apps menu?
If so, did you look for these apps on the App Drawer (hit the circle with 6-dots on the navigational bar at the bottom of the screen)?
Click to expand...
Click to collapse
Nope..settings app doesn't show Google Play Services either.
I would like to try CWM instead of TWRP. WOuld you know if there's a way to boot the latest CWM from the SDcard like TWRP? All I did for the latest TWRP was rename the sdcard version from their site to recovery.img and coped it over to the main directory of the sdcard.
chimpknowskungfu said:
Nope..settings app doesn't show Google Play Services either.
I would like to try CWM instead of TWRP. WOuld you know if there's a way to boot the latest CWM from the SDcard like TWRP? All I did for the latest TWRP was rename the sdcard version from their site to recovery.img and coped it over to the main directory of the sdcard.
Click to expand...
Click to collapse
I don't know of an SD-based version for CWM v6.0.4.3 or later (which is required for CM11).
Try using the recovery.img that is included in cm_acclaim_11.0_14JAN2014_HD_SDC.zip (open the zip file and extract recovery using 7-zip), or get the SD version of TWRP 2.6.3.1 from http://techerrata.com/browse/twrp2/acclaim (rename it to recovery.img before copying it to your SDcard).
digixmax said:
I don't know of an SD-based version for CWM v6.0.4.3 or later (which is required for CM11).
Try using the recovery.img that is included in cm_acclaim_11.0_14JAN2014_HD_SDC.zip (open the zip file and extract recovery using 7-zip), or get the SD version of TWRP 2.6.3.1 from http://techerrata.com/browse/twrp2/acclaim (rename it to recovery.img before copying it to your SDcard).
Click to expand...
Click to collapse
I got it fixed by burning the sdcard image and then expanding the partitions accordingly.
Thanks for your help anyway.
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Djoul33 said:
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Click to expand...
Click to collapse
In TWRP, go to mount and see if data is mounted.
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Djoul33 said:
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Click to expand...
Click to collapse
I have flashed things that did not properly unmount a partition afterwards so I could not mount it in twrp. Try flashing something that mounts data, if not mounted, then unmounts data properly.
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
2016...
Djoul33 said:
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
Click to expand...
Click to collapse
Try that first.
Hi,
My TWRP was too old, deprecated. It is OK now.
Thanks.
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
1.) Can I go from 14.1 to 16.0, or is there a reason 15.1 should be flashed first?
2.) Will any version ≥ TWRP 3.2.x.x official or unofficial work for both Oreo and Pie?
3.) Is this a correct order of operations:
a.) Boot into FOTA recovery
b.) Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage (also, is there a difference between Format Data and Advanced Wipe > Internal Storage?)
c.) Install .zip for LoS from external SD card (or should I sideload via adb?)
4.) Installing gapps is listed as optional, so I can skip installing an opengapps .zip?
5.) Installing addonsu .zip can be done later?
Thank you!
remi_kamahl said:
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
Click to expand...
Click to collapse
Hello!
1. Yes, you can.
2. For Oreo and Pie 3.2.x.x and 3.3.x.x are optimal.
3a. Check FOTA recovery version, if <3.2.x.x i suggest updating first.
3b. The difference is, that formatting data doesn't wipe internal storage (as far as i remember).
3c. External SD is better (though it's your choice).
4. If you don't GAPPS you can skip it.
5. Yes it can be done later, but i see no reason to not installing it in 3c.
Also think of root management solution, suitable best for you. Will it be internal root manager of LOS (with the help of addonsu binary) or you will use Magisk, which is more complex and has it's benefits too.
Good luck with flashing!
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
This is specifically what I did:
1. Pushed lineage-16.0-20200511-UNOFFICIAL-pollux.zip & twrp-3.3.1-0-pollux.img to external_sd via adb root
2. adb reboot recovery; verified md5sums via terminal
3. In terminal: # dd if=/external_sd/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
4. Reboot into FOTA recovery; made sure the version = 3.3.1-0
5. Wipe: Format Data
6. Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage
7. Install the lineage .zip
8. Wipe Cache/Dalvik and reboot system
After the "Sony Xperia" logo pops up, the Lineage boot animation runs for about 2.5 minutes, then the tablet drops into TWRP (RescueParty).
I can restore a 14.1 backup I made before flashing, and the tablet will boot again successfully.
Not sure where to go from here/not sure which specific log file would be necessary—or even available—to diagnose the problem (dmesg, logcat, Console-ramoops).
remi_kamahl said:
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
Click to expand...
Click to collapse
This happens sometimes. Try to wipe everything ones again and flash LOS via TWRP.
FYI lineage-16.0-20200609-UNOFFICIAL-pollux.zip build is available.