Related
Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
pikudroid said:
Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
Click to expand...
Click to collapse
Gotta wipe everything, including internal storage, factory reset. Also the vendor and bootloader for 6.0
madbat99 said:
Also the vendor and bootloader for 6.0
Click to expand...
Click to collapse
Can you elaborate on that? What exactly do you mean?
pikudroid said:
Can you elaborate on that? What exactly do you mean?
Click to expand...
Click to collapse
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
madbat99 said:
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
Click to expand...
Click to collapse
Thanks a lot. Flashing vendor.img worked for me.
pikudroid said:
Thanks a lot. Flashing vendor.img worked for me.
Click to expand...
Click to collapse
Glad it helped. Hope I didn't over-explain, lol
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).
Loaded twrp with odin, then loaded aicp custom rom.
A year later loaded pixel pie custom rom
On power off the fone wouldn't restart in pixel, or twrp
I tried taking the Battery out and waiting 5 mis, 1hr, 3 hrs the fone still wont start.
BUT if the fone is left with the battery out for 3days it starts in both pixel and twrp no problem !!!
I also tried cleaning all partitions on twrp except sd card and loading my image of aicp which used to work, .. no change.
Anyone have an idea what this might be?
The phone is a samsung note 4 snapdragon originally on marshmallow android.
Im thinking of asking samsung to put marshmallow on again then reloading twrp and aicp
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
ze7zez said:
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
Click to expand...
Click to collapse
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
If you are installing a new/different custom rom, it's best to do a full wipe with internal memory included.
For many phone models, twrp 3.6.x performs worse than 3.5.2.x.
Since the twrp kernel is good for shutting down the phone, change the ROM to one that also shuts down the phone well.
Read the first post of the thread very carefully and understandingly:
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS...
forum.xda-developers.com
and install LineageOS 18.1 by @ripee.
gwm121 said:
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
Click to expand...
Click to collapse
Thankyou ze for succinct helpful info.
I am reading very carefully as you suggest
In this section im unsure about ..........."type fastboot reboot" ...
Recovery is to get to twrp right? vol up pwr home with note 4, that would bring up menus on twrp, .there is a menu box for reboot.. Have I undersood this please?
I can follow ypour suggestion tomload an earlier version of twrp
is it possible a later twrp has anything to do with the loading kernal of the rom
"""Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."""