LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
/ * Your warranty is now void. Knox 0x1.
/* We are not responsible for bricked devices, dead SD cards, lost data due to failed backups, etc, etc. flash at your own risk
*/
How to flash this ROM:
1. Download the zip file.
2. Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on tablet).
3. If you want Google Play functionality, download OpenGApps (link below). (optional)
4. Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
5. Make a backup (optional).
6. Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
7. Flash the ROM you just downloaded.
8. Flash OpenGApps ARM for Android 9.0 if you want Google services (optional).
9. If you want root, flash Magisk.
10. Reboot and proceed normally with installation.
11. ????
12. Profit!
Download links:
SM-T350
OpenGApps ARM 9.0 (I use pico)
Source code:
LineageOS
iesous-kurios (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Galaxy MSM-8916
Credits:
The LineageOS Team (and specifically haggertk )
elginsk8r
VirsysElectron
Nubianprince
And awesome tester : retiredtab (saved me sooo much time and has been huge asset in getting bugs fixed)
And of course the Galaxy MSM-8916 team for all of their hard work on our device specific code.
Version Information:
ROM OS Version: Android 9.0 Pie
Known Bugs:
Static while playing mp3s with stock music player (download vlc player to play mp3 files)
Overwhelming sense to brag that your old tablet has newer version of Android on it than a lot of people's expensive phones.
All other functions seem to be working fine. Please report bugs with logcat. I am just starting out on being able to troubleshoot bugs and make edits to code to fix problems, so a majority of bugs will be fixed by the official devs and maintainers of Lineage but I'm trying to learn how to help out too and you have to start somewhere, right?
1st
2nd
3rd
Looking forward to this, thank you!
Thanks for the nice ROM, older bugs are gone! Runs very smoothly with frequent lock-ups.
Issues:
Some apps from Google Play Store are not available saying "not compatible" when you can install their APKs (i.e. Instagram...etc.)
Lockups are annoying
Jfuginay,
Thanks for compiling this ROM. Your work is appreciated.
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
I will check tomorrow to see if there is a newer TWRP that can work with the updater script. I saw in another thread that the SM-T550 updater script is failing because TWRP can't report the model number.
I do need external audio working. I see that SM-T550 which is the bigger version of this A tablet does have audio working as per
https://forum.xda-developers.com/showpost.php?p=78720468&postcount=22
Perhaps there is something in that SM-T550 code that we can use to help with the SM-T350.
retiredtab said:
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
Click to expand...
Click to collapse
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
retiredtab said:
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
Click to expand...
Click to collapse
Glad you got it to boot.
I noticed that missing config folder too, so I just added that to my build directory and am compiling that now to test it out. I didn't add the camera files, since it is only bluetooth and speaker I'm trying to troubleshoot. Don't think the camera is having problems, but honestly haven't tried it out yet.
I noticed the missing config folder when checking out the device.mk file for each device. I added the links to the config folder in the device.mk file and added the bluetooth and sound folders from config file to my build directory, so I'm hoping once that compiles it will fix our problems.
Will do a dirty flash first, then if it still isn't working, I'll do full wipe and test it out. If it boots up and fixes anything I'll upload it for people do download, if the same problems persist I won't bother uploading the new build.
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
retiredtab said:
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
Click to expand...
Click to collapse
I'm hoping it's those config files. I did a build with them in but I'm not sure they were included because of my ccache being enabled. I'm not 100 percent convinced that ccache can tell the difference between slightly modified files well enough to know to include the changed files in new build, so I cleared out my ccache files and ran make clobber and am building fresh right now with those config files in there.
Will do full wipe and flash this and report back if it made any difference.
Adding those config files didn't fix anything. Found several differences in some proprietary.mk files so attempting to see if any of those do the trick. New build compiling now. Will probably need to disable ccache and do make clobber to clear directory so I'll probably let it build over night while I sleep.
Let's hope I wake up to a fixed ROM !
Jfuginay said:
Adding those config files didn't fix anything.
Click to expand...
Click to collapse
Darn, I was hoping the config would fix it.
I left a message in the SM-T550 thread asking virsys what was done to fix the external audio because it's not obvious to me where the commit is that fixed it.
In this post
https://forum.xda-developers.com/showpost.php?p=78170903&postcount=9
dated Nov 15, 2018 virsys says "Audio is working now".
At github
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi/commits/lineage-16.0
there is a commit for Nov 16, 2018 entitled
Cleanup for OSS-audio and improved lineage-16.0 compatibility
I wonder if this commit fixed the external audio?
Just out of curiousity, how are you building this ROM? Locally or on some clould computer?
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
retiredtab said:
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
Click to expand...
Click to collapse
I'll check out a working 14.1 ROM and see if it has specific proprietary files there which differ from what we are using now.
Virsys responded back on how he/she got the SM-T550 external audio working. See
https://forum.xda-developers.com/showpost.php?p=78978788&postcount=74
"I've fixed the whole audio framework by editing and importing my own mixer_paths.xml to /system/etc"
I wonder if we can download his SM-T550 ROM image, extract that mixer_paths.xml file to see what changed?
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
retiredtab said:
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
Click to expand...
Click to collapse
Thanks for all the ground work, gives me a good place to look into tonight when I get home from a meeting and have some time to tinker with the code.
K, I looked through a lot of proprietary code for both the gt58 and 511, and hopefully found all the discrepancies. Added over 20 files and lines of code to gt58 proprietary folders and renamed one file to match the dependency in another file.
Compiling now, so cross your fingers that it fixes our sound!
Are your changes up on github?
https://github.com/jfuginay
I'm newish to github and just learning how to navigate and look around.
What I find confusing is the seemingly incredible amount of layers of abstraction in defining the speakers. That is, A->B, B->C, C->D, D->E, E->F, F->G. Anything missing is enough to break it.
I understand why the layers are required, but without a flow chart or visualization of how these things work, it's difficult to follow all the necessary definitions and files needed.
I also have noticed some of the people using github have no documentation on why the code change was required. The changes are there, but why? Was it because something was broken? Was it because it wasn't defined properly in the first place? Was it because there was a potential security problem?
If you have any URL resources that would help explain some of this, I would appreciate some pointers.
Related
Hi, after several days seeking for cifs.ko/slow-work.ko finally i found the attached file the which loads fine and i can mount my network file share and explore it, but when i try copy or open video file the file load/transfer starts but after few seconds my photon reboot.
The rom is stock, kernel is 2.6.32.9 [[email protected] #2], rooted.
Is possible make some fix to those modules or at least know with log/debut what is failing?
thanks.
Edit: Go here for a working cifs.ko: http://forum.xda-developers.com/showthread.php?t=1895983
My best guess would be that you found a kernel module that "loads", but isn't compiled for your exact kernel. Once loaded it establishes the connection and you are able to browse files/folders. Once you start a transfer you utilize a different part of the module that doesn't jive 100%. That causes a memory leak/buffer overflow/kernel panic. Kernel panic = phone vomit -> phone warm reboot. Really need to have a module that was made for your specific kernel.
Could also be the app. Easiest way to tell if the app is the culprit is to mount the share manually in a terminal window. Then do a cp command from your mounted share to a local folder and see if it works that way.
Manually mounting a share in a terminal window will take a little *nix know-how, but shouldn't be that hard. I know how to do it, but I don't think I can teach you in a short timeframe if that makes sense.
---------- Post added at 01:34 AM ---------- Previous post was at 01:21 AM ----------
Did a 'strings' of the module and it looks like it is compiled for 2.6.32.9-00005-g2440aba *edit* that kernel is for the DX2. Looks close, but not for your exact kernel. Also the version of cifs.ko is 1.61 if that matters, compiled for arm7 platform.
I really don't think it will work right without compiling it against your current kernel source.
atroph said:
My best guess would be that you found a kernel module that "loads", but isn't compiled for your exact kernel. Once loaded it establishes the connection and you are able to browse files/folders. Once you start a transfer you utilize a different part of the module that doesn't jive 100%. That causes a memory leak/buffer overflow/kernel panic. Kernel panic = phone vomit -> phone warm reboot. Really need to have a module that was made for your specific kernel.
Could also be the app. Easiest way to tell if the app is the culprit is to mount the share manually in a terminal window. Then do a cp command from your mounted share to a local folder and see if it works that way.
Manually mounting a share in a terminal window will take a little *nix know-how, but shouldn't be that hard. I know how to do it, but I don't think I can teach you in a short timeframe if that makes sense.
---------- Post added at 01:34 AM ---------- Previous post was at 01:21 AM ----------
Did a 'strings' of the module and it looks like it is compiled for 2.6.32.9-00005-g2440aba *edit* that kernel is for the DX2. Looks close, but not for your exact kernel. Also the version of cifs.ko is 1.61 if that matters, compiled for arm7 platform.
I really don't think it will work right without compiling it against your current kernel source.
Click to expand...
Click to collapse
Is true... but i guess is not necessary test to mount something in command line because i tried two different apps and gave me same result.
If matters i check module with modprobe/hex editor and compare layout_info with any integrated module in my phone and it match.
Hi guys
I just got a Redmi Note 2 a few days ago. I'm already tired of MIUI again so I decided to install TWRP and flash a custom ROM. I downloaded three roms:
AICP Unofficial Port: http://forum.xda-developers.com/red...nt/rom-android-ice-cold-project-10-0-t3288971
CM 12.1 Nightly Unofficial Port: http://forum.xda-developers.com/redmi-note-2/development/rom-unofficial-t3310551
MoKee CM 12.1 Unofficial Port: http://forum.xda-developers.com/red...nt/rom-cm-12-1-mokee-bule-mokee-blue-t3328382
Unfortunately I discovered I was only able to install the AICP roms. With the other ROMS when I attempted to install I received a message of the form:
"This rom is for device hermes. You device is."
If I hadn't been able to install AICP I would have been left with a very new brick
I want to know if anyone else has encountered this issue before. If so, what was the cause and were you able to solve it?
There is something in /system/build.prop that is not identifying the device as "hermes".
Either edit the build.prop, so that:
ro.product.device=hermes
ro.build.product=hermes
Or edit the updater-script files in the ROM packages, to comment out the line that looks for ro.product.device or ro.build.product being "hermes".
I see. Does build.prop persist if I perform a wipe of system?
If you wipe system, then nothing should persist (ie, nothing should be there at all). How the scripts that look for "hermes" in build.prop will then react to that situation is anyone's guess. I would imagine that they would still fail, because the variables that they are querying would not exist, and an undefined value might be returned (unless they are searching for it elsewhere - eg, in TWRP itself). The best solution, in my opinion is to edit the updater-scripts in the zip install packages to comment out the line that searches for "hermes".
---------- Post added at 12:34 PM ---------- Previous post was at 12:01 PM ----------
I have just examined the ramdisk of the latest TWRP from jajk, (see http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492) and the embedded default.prop has an "ro.product.device=hermes" entry. So it seems that the updater scripts might be querying TWRP rather than /system/build.prop.
You might want to install jajk's TWRP. This should solve your problem without your needing to do anything drastic.
Yeap, DarthJabba9 is right.
Also, I would like to add that, most updater-scripts run the format /system command, so you could just wipe the other partitions and let the script format your system partition.
Ah, that's good to know.
This is a beta test for MIUI 8 MM base for the Nexus 6P.
This version is based off patchrom, and is an unofficial build.
Up to date tutorial of how to build using patchrom - Here
WARNING: Your warranty is now void. I take no responsibility in the well-being of your device. Follow the instructions, and post detailed information if you face any issues.
Full install instructions can be found - Here
It is a long process, unfortunately
Ok, this should be the current install method that people are following. As of Oct/13/16
Download the necessary apk files and place them on your sdcard/emulated storage. (Keyboard of choice, rom manager/smanager, titanium backup, and working theme manager)
Wipe Dalvik, system, data, and cache
Flash fullota, vendor, gapps, superuser
Allow the rom to boot. Takes roughly 10 minutes for the first boot. You will experience some force closes
Pull the notification shade down, hit the gear icon to get into options. Go to about phone. Tap MIUI version until you have developer options.
Go back to settings, then find additional options. Scroll down to "Allow USB debugging". Check the box next to this option
Open permissions, application found on your homescreen select bottom option for root. Check the box and accept the prompt
It will say that it failed
Go to the homescreen and delete the supersu application (drag the icon to the top of the screen)
Open the file manager application and install Titanium backup. (This will help you determine if you're rooted)
Open script manger(browse as root). Navigate to /data/local/ and run userinit.sh as root.
Your gapps should now be functioning without force closing.
Now delete the themes application. (use a root file explorer, I use solid explorer. Theme manager is located in /system/apps/)(Must restart your phone after deleting the apk)
Install the theme manager from your sdcard
(You can download themes from Here (place them in the /miui/theme/ folder
Finally, fix file sharing issues by enabling Documents in the installed apps settings. (It is disabled by default. You'll have to enable it after every reboot)
To download off of Wi-Fi, go to downloads app, settings, change limit to your liking.
To keep documents enabled after reboots, follow theses instructions:
Enable Documents in "installed apps" settings
Go to developer options
Disable MIUI optimizations
Accept and reboot
Download links:
MIUI ROM - FullOta
Vendor - Vendor
GAPPS - GAPPS
GAPPS Mirror - GAPPS
Apps to place on sdcard - APPS
Superuser - SU Warning Won't prompt for super user permissions
Tested and working:
Data
Wi-Fi
Touch
Camera
Gyroscope
Fingerprint reader
NFC
Bluetooth
Gapps
Su
Themes
File sharing
BUGS/TODO:
Package everything into an all in one package/less packages
Enable themes by default
Enable "Documents" by default
Find a better solution for gapps
Add su handling application
Add fully English keyboard to initial package
Old install method, courtesy of @Andromjb
Changelog:
Oct - 7 - 2016
Fixed MIUI kernel (no longer need to flash franco kernel)
Thanks where they are deserved!
mcming1989 on github for supporting Patchrom for angler
@thoiloidainhan for being super helpful with a TON of things
The fans for keeping me motivated
MIUI devs and port team for info
Superr for his tools
Google for the ease of access to info
Those of you who have donated. You rock!
@MidnightDevil for writing a helpful How-To
@skw5115 for figuring out the "share" bug
@Andromjb for the great installation video
@pacods61 for getting themes situated
@pacods61 for finding the download limit setting
XDA:DevDB Information
MIUI 8, ROM for the Huawei Nexus 6P
Contributors
tr4nqui1i7y
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP, Patchrom, MIUI 8
Version Information
Status: Testing
Created 2016-08-18
Last Updated 2016-10-04
I'm in, standing by to flash..
mbl1979 said:
I'm in, standing by to flash..
Click to expand...
Click to collapse
eta 6 min
Be aware. Not sure if this will boot. Or soft/hard brick a device.
By flashing, you agree that you are at fault if any errors occur.
I will help as much as possible in the process.
Please upload your logcats to pastebin. This way I can view them, as long as others.
OK, do you have a 6p as well? Or are you building blind?
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Also what do we need to flash with it? 1st time flashing MIUI ROM.
mbl1979 said:
OK, do you have a 6p as well? Or are you building blind?
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Also what do we need to flash with it? 1st time flashing MIUI ROM.
Click to expand...
Click to collapse
I have a 6p as well. OP updated with download link.
Good deal.
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Flash super su ?
Can i flash It by Twrp? Does It need gapps?
Enviado desde mi Nexus 6P mediante Tapatalk
OP updated with further instructions
Downloading ?
Backup updated, flashing now.
xXPegashusXx said:
Can i flash It by Twrp? Does It need gapps?
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
Flash through latest TWRP. No gapps or additions for now.
1st attempt, error 7 failed to install in TWRP.
mbl1979 said:
1st attempt, error 7 failed to install in TWRP.
Click to expand...
Click to collapse
Me too, it says same error
error 7 faild in the first attempt
mbl1979 said:
1st attempt, error 7 failed to install in TWRP.
Click to expand...
Click to collapse
Got it. Updating asserts then I'll repost. Flashing will not succeed until I post an update. Sit tight everyone.
Sounds good bud.
mbl1979 said:
Sounds good bud.
Click to expand...
Click to collapse
ETA 8 minutes
Downloading new version
OP updated with test 2
Will be back tonight with more builds...
Again. ONLY FLASH IF YOU ARE COMFORTABLE WITH FASTBOOT/SOFT BRICK/HARD BRICK
Just got this email: "You f****** loser, you test it first. Stupid noob. You want us to brick first? You test it first mother f*****"
Robert Tromp [email protected]
If you don't want to test, don't. This is a development community, let's act like it. This build was never claimed to be safe/stable/usable/bootable.
Code:
/* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TREBLE
* SUPPORT before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install Instruction:
Flash this TWRP with treble support (thx to @CodeZero)
Format /system, /data and /cache
Install this Lineage treble build from Google Drive or from Transfer.sh
Install Android P DP5 sGSI
Mount vendor on TWRP
Install the POST-sGSI zips in the order from Here
Install POST-sGSI-v1.1-cedric from Here
Reboot
Install Google Play Services using either your pc ($ adb install -r .apk), or your phone.
Reboot again
Enjoy
Known issues:
Same as lineage treble and:
MotoActions crash
Only DP3 boots Fixed by @J0SH1X on POST-sGSI-v1.1-cedric
You tell me
How to report bugs:
REGISTER IT ON GITHUB WITH LOGS, OTHERWISE IT WILL BE IGNORED AND CLOSED.
The GitHub for registering the issues is This
Steps to do it:
Check if it was already posted (duplicates will be closed)
Logs should be attached (posted on gist, otherwise the issue will be closed)
The title format should be: LineageTrebleBuildDate: Android-P DP3: issue you are having
The description should be the full log on gist (https://gist.github.com), and steps to reproduce the issue.
Each issue should be posted individually
DONT TAG ME HERE, OR ON TELEGRAM. I use github bot which sends me notifications when someone posts or replies to an issue
IF YOU DIRTYFLASHED, MENTION IT
Requirements for taking logs:
A PC with adb and the drivers installed
A phone
How to take logs:
Connect your phone to the PC
Enable Android debug bridge on the developer settings
Run $
Code:
adb devices
on your PC shell, and if it shows your device proceed, otherwise tag an admin to help you
Run $
Code:
adb reboot
this will reboot your phone
While it's still on the Motorola logo, run $
Code:
adb logcat > log
Once the device boots, replicate the issue
After the issue is replicated, press the CTRL and C keys simultaneously
Once this is done the file log will appear in the folder you ran adb.
This file contains the log.
More info:
Original P thread
Wiki/FAQ
Cedric Wiki/FAQ
Thanks @erfanoabdi for his work on this unbelieveable acomplishment
reserved
ı am ınstall dp5 not boot
AsusZenFone3Deluxe said:
ı am ınstall dp5 not boot
Click to expand...
Click to collapse
I understand that only DP3 works
I try DP4 and DP5; doesn't boot in that Versions
AsusZenFone3Deluxe said:
ı am ınstall dp5 not boot
Click to expand...
Click to collapse
"Issues
only DP3 boots"
read op next time
yes I managed to install on my device, working fine, but camera on record more on others is good, so far ....
---------- Post added at 02:06 AM ---------- Previous post was at 01:19 AM ----------
https://github.com/erfanoabdi/P_semiGSI/wiki/Moto-G5
They just put that you can now install DP4 and DP5, more than correction and need to install?
---------- Post added at 02:56 AM ---------- Previous post was at 02:06 AM ----------
I installed the hevc + sm mod in the magisk, and the Asus camera version 5.0 and now I am able to make video.
Shadowsleeper said:
yes I managed to install on my device, working fine, but camera on record more on others is good, so far ....
---------- Post added at 02:06 AM ---------- Previous post was at 01:19 AM ----------
https://github.com/erfanoabdi/P_semiGSI/wiki/Moto-G5
They just put that you can now install DP4 and DP5, more than correction and need to install?
---------- Post added at 02:56 AM ---------- Previous post was at 02:06 AM ----------
I installed the hevc + sm mod in the magisk, and the Asus camera version 5.0 and now I am able to make video.
Click to expand...
Click to collapse
I updated the thread
If I want to go back to my oreo rom after installing this GSI, do I have to also backup /vendor and then restore it after installing android P? I just don't want to mess up anything since I'm kinda downgrading and I'm assuming these post GSIs somehow patch the vendor partition...
Android p dp5 booted. THANKS
Screenshots
https://androidfilehost.com/?w=files&flid=280192
please update op.released android p stable version
How to install update?
İnstall the image with twrp(system image)
Led flash not working and dont take a video
LTE not working
vimicius said:
LTE not working
Click to expand...
Click to collapse
working my device
AsusZenFone3Deluxe said:
Led flash not working and dont take a video
Click to expand...
Click to collapse
You can just enable camera2api and disable it again and flashlight will work again
Need to explain that you have to extract Android P DP5 sGSI and install as system image, because it lacked that information I stayed vary hours trying to install as zip
Hi,
I want to try out Android Pie with Treble Support - is it possible and uncomplicated to switch back to an Android 8.1 ROM after you flashed the alternative TWRP with Treble-Support + POST-sGSI zips?
ciao, Sören
Deleted.
AsusZenFone3Deluxe said:
working my device
Click to expand...
Click to collapse
friend, how do I run lte?
Anyone who can help me? Xposed stopped working all of a sudden eventhough it says everything is on and working fine.. (have already deleted and re-installed xposed but it wouldn't help..)
I am getting this message but don't know what to do with it..
(It's some kind of download failure.)
Downloading dl.xposed info /repo /partial/ 15855 .xml. gz failure: 302 (Moved Temporarily)
That's the message i'm getting, not sure if this has got something to do with it but i think it is.
S8+ android 8.0.0
version 90-beta3
Thanks!!
Xposed Framework is working, only the repo download doesn't work. I think we must wait. Doesn't find any further information now.
https://forum.xda-developers.com/showpost.php?p=77758701&postcount=732
.. some more comments about this repo glitch.
Sent with much love & Android. OnePlus 5T
I get the exact same error.
Update
Think it resolved itself..
Everything working again
https://forum.xda-developers.com/xposed/discussion-xposed-oreo-t3732816/post77770036
Reset data of Xposed Installer and all fine now.
Sent with much love & Android. OnePlus 5T
Wiping Xposed installer data worked for me too.
Thanks!
Wiping data & cache didn't work for me.
Still Xposed can't download module list.
Do you have a second device to crosstest ?
Adblocker on device ? modified host files ? Firewall ?
-Rye- said:
Do you have a second device to crosstest ?
Adblocker on device ? modified host files ? Firewall ?
Click to expand...
Click to collapse
I have the same Problem on Samsung Galaxy s5mini @ stock Kitkat root, no Download list of modules. Code 302
Data wipe did change nothing,
New installation of Xposed installer did cange nothing
Crosschecked with Samsung Galaxy Tab 4 @ Kitkat root, works! Same version of installer sme WiFi.
I have no Adblockers / Firewalls installed on device. Perhaps there is one installed by default by Samsung?
Crosscheck shows no Firewall-blocking on Network.
It did work when I installed it.
I think it stopped working when I started to deoxidise the system. I de-installed some updates and deactivated Samsung and Google stuff with titanium Backup... All other things are working normally...
Does xposed need some of these things?
---------- Post added at 10:36 AM ---------- Previous post was at 10:25 AM ----------
However when it still worked I installed the following xposed modules:
Permission Master
BootManager
Does one of these restrict downoad permissions of xposed by default?
Same problem.
"Downloading h t t p : / / dl.exposed.info/repo.xml.gz failed: 302 (Moved Temporarily)"
(Added spaces)
Version:
...v32_de4f0d.apk
Workaround for now: download and install modules manually.
Please see the following thread post from myself that has an AFH link to an Unofficial version of the XposedInstaller app with the fixes that address the Repo Error 301/302.
https://forum.xda-developers.com/showthread.php?p=77923681
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
Instead of wiping installer app's data, one workaround that worked for me is to remove/rename the no_backup folder in xposed installer's data dir.
n0j0e said:
https://forum.xda-developers.com/xposed/discussion-xposed-oreo-t3732816/post77770036
Reset data of Xposed Installer and all fine now.
thx that fixed it
Click to expand...
Click to collapse
kennethho said:
Instead of wiping installer app's data, one workaround that worked for me is to remove/rename the no_backup folder in xposed installer's data dir.
Click to expand...
Click to collapse
where is the folder ?
---------- Post added at 12:36 PM ---------- Previous post was at 12:09 PM ----------
Ibuprophen said:
Just an FYI for those who are experiencing some issues regarding an error message 301/302 for the Repo within the Installer app.
rovo89 had enforced an HTTPS redirect on the Repo server, but the HttpURLConnection class used by the Xposed Installer has issues with following redirects from HTTP to HTTPS.
This redirect has been working for some but, not others.
I had created a pull request reflecting the corrections for the XPosed Installer within Rovo89's XPosed Installer on Github.
https://github.com/rovo89/XposedInstaller/pull/458
So far I'm still awaiting Rovo89's response.
This was all done yesterday. Let's give it some time. :thumbup:
In the meantime, i had created an Unofficial release with the URL fix for the Repo and its located on the following link.
https://www.androidfilehost.com/?w=files&flid=284172
I also kept the Signature in tact so when/if @rovo89 releases a fixed Installer app, updating the Unofficial version to the Official one won't be a problem.
Enjoy!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
cant install it on android 4.4
Code:
Running "adb -d install -r "D:\USB_HDD\701\Android\apps\system\Exposed\without error repo 302\Xposed.Installer.ver.2.6.1.build.32.URL-Fix.apk""
[100%] /data/local/tmp/Xposed.Installer.ver.2.6.1.build.32.URL-Fix.apk
pkg: /data/local/tmp/Xposed.Installer.ver.2.6.1.build.32.URL-Fix.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Code:
Running "adb -d install -r "D:\USB_HDD\701\Android\apps\system\Exposed\without error repo 302\Xposed.Installer.ver.2.6.0.build.31.URL-Fix.apk""
[100%] /data/local/tmp/Xposed.Installer.ver.2.6.0.build.31.URL-Fix.apk
pkg: /data/local/tmp/Xposed.Installer.ver.2.6.0.build.31.URL-Fix.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
And virustotal.com says there are 2 viruses/
https://www.virustotal.com/gui/file...e960e719318d208839f408463f29cb9ecec/detection
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
Repo error is gone after I have used XposedInstaller_86framework.apk which used to install exposed on Meizu phones.
Now there is no repo error.