Hello,
I would like to install Lineage on my OnePlus5T, as the OxygenOS system does not seem to have an option for the Albanian language. Lineage does.
However, since Wednesday July 28, I have been trying and failing. Here are the steps:
1. Unlock bootloader (worked perfectly.)
2. Flash TWRP (No issue there either.)
3. Wipe Data, System, Dalvik, Cache (All okay so far...)
4. Flash Lineage and Gapps (both worked fine). I'm flashing lineage 18, with the pico gapps package for android 11.
5. Wipe dalvik and cache again, then reboot. But I got stuck on the spinning wheel. I had backed up all the data with TWRP, but apparently restoring it won't put me backk on OxygenOS. The backup must've been corrupted when copying to a computer.
I also erased system and vendor with fastboot, which wiped all else from the phone and then I tried again, still no luck.
I have tried flashing OxygenOS again, and that now gives me "zip trebble compatibility error, invalid zip file format".
But all partitions were empty, before flashing the system. What have I done wrong? Or what should/can I try to get the system installed?
Many thanks for any help... Sorry for the long message.
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
dedq said:
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
Click to expand...
Click to collapse
I feel that could work. However, just before I do, I should ask, does Lineage have the core google apps already installed? Google play, etc? If so, I'll give that a try at my earliest convenience.
Many thanks for the help.
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
dedq said:
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
Click to expand...
Click to collapse
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
First see if it works at all after flashing system and we will see after it.
Tobias101 said:
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
Click to expand...
Click to collapse
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
KeinePanik said:
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
Click to expand...
Click to collapse
Thank you so much, I'm going to give that a try when I can.
Hello,
The system booted without gapps, but didn't boot with it. So I downloaded the nano package, which was the only other available one for android 11, and it now works flawlessly.
Many thanks for all the help!
Related
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.
I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
try wiping the dalvik cache and data and everything else and clean install the ROM
Tried wipe
anup807 said:
try wiping the dalvik cache and data and everything else and clean install the ROM
Click to expand...
Click to collapse
I wiped everything but the internal storage. I am quite new, what is clean install?
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Darrentay said:
I wiped everything but the internal storage. I am quite new, what is clean install?
Click to expand...
Click to collapse
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Thanks
jon52491 said:
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Click to expand...
Click to collapse
Well in that case, I have clean flash multiple times with different ROM, but I'm still stuck at the logo once I try to reboot. I also tried to flash Os 3.2.7 and Cm 14.1 again but i got no results. Attempting to reformat I guess? I have no data since its a new phone, so I don't mind losing stuff.
Okay sounds good! Before you reformat through fastboot, try booting into twrp and reformatting the partitions through there. TWRP>wipe>advance wipe>cache>change file system>ext4
Repeat the steps for the data and system partitions as well. Then from there transfer a 6.0 ROM and flash it over with the correct Gapps.
Sent from my ONEPLUS A3000 using Tapatalk
Darrentay said:
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
anup807 said:
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
Click to expand...
Click to collapse
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Darrentay said:
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Click to expand...
Click to collapse
Really Strange. I think its the problem with the system partition format and encryption.
Anyway best solution now is to contact Oneplus tech support.
They'll hard reset your phone and restore it with stock firmware.
Partitions are probably corrupt or on f2fs. Check each partition and make sure it's set to ext4. If it won't allow you to do that in twrp, use the command "fastboot format:ext4 nameofpartition". After that you should be able to flash over a marshmallow ROM.
Sent from my ONEPLUS A3000 using Tapatalk
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
v.konvict said:
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
Click to expand...
Click to collapse
I can't solve the problem so I contacted Oneplus. They use remote access to help wipe everything and reinstall drivers. Thanks for the help though.
Package installer crashes and i cant install .apk files, i tried other installers, but they crash too. Also, when I want to give location permission to app, it crashes saying package installer crashed. What could be the cause? (i know i can install apps through adb, but i dont always have access to computer)
You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.
redpoint73 said:
You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.
Click to expand...
Click to collapse
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.
DarkKnightComes said:
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.
Click to expand...
Click to collapse
Try flashing another Lineage build, is probably the easiest way.
redpoint73 said:
Try flashing another Lineage build, is probably the easiest way.
Click to expand...
Click to collapse
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now
DarkKnightComes said:
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now
Click to expand...
Click to collapse
Ah yes, that pesky gapps. Very easy to forget!
Lineage 16 on the M8, is it a smooth experience?
Cheers