Related
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.
Does this have the Wifi fix in it? or has Google not published that yet?
Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm
Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?
ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3
Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.
Great work, thanks. Flashed about an hour ago, flawless so far!
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?
Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.
ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?
kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.
Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.
Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build IS EXPERIMENTAL! ALWAYS BACKUP!
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
PLEASE NOTE: You might need to change permissions for the Google SetupWizard in Settings! Go into Settings -> Apps -> SetupWizard and grant all permissions. OR else gapps might not work!
You need to be unified by flashing ColorOS 2.1.5 using Alexander Tashi's method.
Please use this recovery (UNIFIED TWRP 3.0.0: https://drive.google.com/open?id=0B0IQuS71Z8k2WmVnTGVrdFJTZVU)
Please use this script if UNIFY don't work: https://drive.google.com/open?id=0B0IQuS71Z8k2eXVXNlMtSU9wNGc
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Hi, this works perfect for me! Thank you man, and thanks also to Wuxianlin and Pojiku. You got it, works fine, everything. Only one bsod at first start, no more bugs.
I will try the rom for a week, if its stable sure i'll use it as daily rom.
Thanks again for your job
Cheers
I will try soon when I have time.
Hope this ROM keep update.
Thank you very much.
sugarsweetcandy said:
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build is stable for me, BUT IT IS EXPERIMENTAL! ALWAYS BACKUP! Battery life is good, no crashes after a modest amount of testing.
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Let me know if it works for you
Click to expand...
Click to collapse
Hi, I have tried flashing this and every now and then after locking the screen, it does not show up.
EDIT: It happens when you turn on Ambient Display
Many thanks.
I'm going to try this immediatly.
I hope you will continue to update and if no, it will be great if you can explain how did you do to make that possible like that we souhld continu the work.
Thanks again and hope you'll continue.
Have a nice day.
I don't know if i did something wrong . I m familiar with flashing etc... I flashed the rom(clean install. full wipe) 3 times and i always have the same issue. when i open the file explorer integrated in the rom, i can see my external sd and can open it but there is no internal storage listed. I tried with sd maid (explorer) and same, no inernal storage listed. when i go in system settings under storage, i see the internal storage (i'm on lvm) and i see 2 sd cards : one wich is corrupted and a second which is my external sd and i can open it. when i plug the phone to my pc, i see only my external sd card partition (iternal storage doesn't appear) and when i click on it my data are not visible. it seems to be empty but in reality no. In TWRP the phone plugged to the pc, i can see internal and external storage and all data are there.
I will try another time maybe i will find the problem.
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
ok i have some news.
I think lvm is not supported. Let me explain.
The 3 first times, i maked a full wipe, flashed lvm setup package, flashed the rom and open gapps (tried stock and nano) and after the reboot and setup, issues i've related appears.
I've decided to read a new time the op and my english is not very good. So i've read : "...already patched kernel for LVM...". I've decided to make a new clean install but this time without flashing the lvm setup. after a reboot and setup, all is good but i have the 2 partitions. once for install app (2.93go), and once for data. Clearly no lvm.
Please sugarsweetcandy, give us new build with complete lvm compatibility as quickly as you can.
Thanks for your work.
p.s : i read on oppo forum a comment saying that this build is not for x9076. is that right. I hope no because my find 7s is a x9076 model
---------- Post added at 03:50 AM ---------- Previous post was at 03:44 AM ----------
thecell_2007 said:
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
Click to expand...
Click to collapse
Thank you for your help thecell. I've already did this but it did'nt work for me. the internal storafe doen t appear if i flash lvm setup package.
For your problem, i figure that you've followed the installation instructions on op. Maybe i'm wrong but i think you flashed the rom and reboot then setup and reboot to recovery then flashed gapps....
when i did the this manipulation i had the same issue.
So what you have to do is in twrp : select all packages you want to flash (rom, gapps, supersu, hal mod, xposed....) and reboot then setup, reboot system and all will done
.
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
sugarsweetcandy said:
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
Click to expand...
Click to collapse
Thanks for your response.
I have exactly what you have when i flash "setuplvm_find7_FULL_WIPE_09012014.zip" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). but in the file explorer my sdcard 0 doesn't appear. I tried with flashing the wuxianlin lvm patch for cm 13 and then i have no the corrupted issue that we can see in your screen but my internal storage doesn't show 25go it shows 2.93go only and the 22go doesn't appear. i didn't sleep all the night testing many methods lol. I will try a last time flashing this "twrp_find7_lvm_09012014.img" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). Maybe there will be in this twrp versio some option for lvm.
Thanks for your invest. I and many find 7 owners i think are waiting for this since a long time. I really want to own this rom. Please bring us some great news. Of course you have a life and we will be patients.
thanks again
I'm on x9077 so it might be different for you, but my install pattern went like this:
1. Was using CM12 fine with old LCD.
2. Did full backup, unified with Chinese ColorOS install method (see CM thread on OPPO forum), and then restored data
2. Broke screen, installed new LCD, and then CM12 didn't work anymore.
3. Did a full backup, wiped everything, installed CM13 + pico apps
4. Booted and did setup.
NOTE: You might need to change permissions for the Google Setupwizard in Settings. Go into Settings -> Apps -> SetupWizard and grant all permissions
5. Some apps will need reinstalling because they will have wrong permissions.
Hope this helps!
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
zw963 said:
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
Click to expand...
Click to collapse
Yes, the new LCD is supported!
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
roi_xordo said:
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
Click to expand...
Click to collapse
Try the one that is mentioned in this thread, it works for me! The official ones are not supported.
Cm13 20160406 nightly
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Keukul said:
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Click to expand...
Click to collapse
Me too, X9077, when start up, panel is keep black, not work.
this hacked version is work fine for me for now.
I am in the process of redownloading sources and updating to ROM to latest. I lost everything!
Thanks for merging LVM into CM13, I switched today from Nameless and unified storage works for me, however I'm experiencing a lot of random reboots during the day. Is there any log I can catch, so you can help me identify the source? Thx (also posting this on OPPO forums).
I am an oppo find 7 user, if I flash this rom will vocc fast charge works in my oppo. Pls let me.know
I can flash back to stock via the SkipSoft Unified Android Toolkit, but not matter how far back I go, the only 3rd party ROM that will not get stuck on a never-ending bootscreen after install is CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte. Not even the CM nightlies that came immediately before or after would work once this was installed.
I would like to try something newer if there is a stable Lollipop, Marshmallow, or Nougat ROM you would recommend. I don't use as a phone anymore, so I don't even need cellular data to work.
Thank you very much to anyone that even takes a look at this.
More info...
Model Number
1HZGY
Android version
4.4.4
Baseband version
L710VPUDOH1
Kernel version
3.4.104-cyanogenmod-g3652409
[email protected] #1
Mon Aug 31 16:36:33 OCT 2015
Build number
cm_d2lte-userdebug 4.4.4 KTU84Q bdfbe2c9c2
test-keys
SELinux status
Enforcing
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
madbat99 said:
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
Click to expand...
Click to collapse
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
pravus87 said:
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
Click to expand...
Click to collapse
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
madbat99 said:
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
Click to expand...
Click to collapse
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
pravus87 said:
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
Click to expand...
Click to collapse
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
madbat99 said:
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
Click to expand...
Click to collapse
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
pravus87 said:
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
Click to expand...
Click to collapse
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
madbat99 said:
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
Click to expand...
Click to collapse
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
pravus87 said:
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
Click to expand...
Click to collapse
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
madbat99 said:
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
Click to expand...
Click to collapse
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
pravus87 said:
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
Click to expand...
Click to collapse
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
madbat99 said:
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
Click to expand...
Click to collapse
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
pravus87 said:
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
Click to expand...
Click to collapse
Happy to help
madbat99 said:
Happy to help
Click to expand...
Click to collapse
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
pravus87 said:
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
Click to expand...
Click to collapse
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
madbat99 said:
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
Click to expand...
Click to collapse
I did not try Lineage or Vanir again like I did Commotio and CarbonROM to verify the md5s. I will try them and some older builds of each.
I sincerely appreciate the offer. I would certainly be willing to download a large backup if you would be willing to take the time to clean install and upload. Let me try the remaining steps you listed first, though. Don't want you to have to spend time doing all that if we can get it working another way.
Thanks again. Will keep you posted!
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
pravus87 said:
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
Click to expand...
Click to collapse
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
madbat99 said:
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
Click to expand...
Click to collapse
Thank you. No rush - whenever you have time.
I don't get it either. I waited a long time to post about it because I assumed there was something simple I was overlooking that I would eventually figure out. Not sure this will work if nothing else has, but I can't wait to give it a shot.
Unofficial builds for Moto X Style (clark)....
Download: https://www.androidfilehost.com/?fid=10763459528675594482 - Version 2020-11-30
Lineage Recovery: https://www.androidfilehost.com/?fid=10763459528675582393 - Version 2020-11-12
TWRP (unofficial): https://www.androidfilehost.com/?fid=10763459528675598925 - Version 2020-12-06.II
What doesn't work (yet).
- Google camera
- Camera: QC reader sometimes doesn't auto-focus (sometimes rotating camera back and forth helps)
- Powerdrain when display on
- Powerdrain when display off could also be better
- You tell me
Sources:
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/rebase/lineage-17.1 [*]
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1 [**]
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1 [***]
Eng version: https://www.androidfilehost.com/?fid=8889791610682927582 - only to be used if the normal ROM crashes on startup
Requirements:
Clark with Nougat (N) bootloader
[*] The kernel sources have already been merged into official lineage repos, but add-ons might come first here. Gerrit contributions are thus open.
[**] Device tree is in gerrit.
[***] Will upload at some point to lineage muppet, but....
Older downloads: Download: https://www.androidfilehost.com/?fid=8889791610682878064
I need your help, bro. I was running the last Nougat update released for the device and did a full factory reset before flashing via TWRP your Lineage OS update and GApps. However, the device had not powered on yet. It simply stays on the Lineage booting phase. What do I do?
thanks soon i will install it
B4oE said:
I need your help, bro. I was running the last Nougat update released for the device and did a full factory reset before flashing via TWRP your Lineage OS update and GApps. However, the device had not powered on yet. It simply stays on the Lineage booting phase. What do I do?
Click to expand...
Click to collapse
I suppose logcat doesn't show anything?
Do you know how to flash boot.img with fastboot?
Chris
Hi @chrmhoffmann
thank you for putting so much work in our old devices,
this weekend i upgraded TWRP to 3.4.0-0 and dirty flashed your UNOFFICIAL_20200625 build over the latest LineageOS 14.1 build for Nougat BL.
It's my son "wifi only" youtube/games device so i cannot test cellular data but everything else it's working.
Photos are 21MP, with correct rotation and camera works if called from apps (tested with hangouts and ghost observer)
The only strange thing is that, while audio is generally working, most games are completely silent.
I first had the impression that was the landscape rotation but happens even on portrait ones.
My son found that even while games are silent, ADS has sounds..
If you need something (logcat, ecc.) let me know, i can also try wiping data if you want.
Thank you,
Fabio
Hello, flashed this rom today coming from stock 7.0.
It booted nice, setup no problems.
Everything is quite smooth, camera working fine.
The handwave gesture to wake up screen is a bit buggy. (Wakes up to late)
Anyway, verry happy to see our old moto running lineage 17.1
Thx for your efforts chrmhoffmann , you did a great job, keep up this great work!
Please provide me with the instructions on how to flash LineageOS 17.1. Apparently, I am doing something wrong. I was on originally on CLARK_RETUS_7.0_NPH25.200-22. Then I flashed TWRP 3.4.0-0. Afterwards, I flashed via TWRP the LineageOS 17.1 from this thread, along with GApps 10.0 micro (ARM64) and Magisk v20.4. Then I rebooted the device. Now the devices just stays on the Lineage loading stage. Please help.
B4oE said:
Please provide me with the instructions on how to flash LineageOS 17.1. Apparently, I am doing something wrong. I was on originally on CLARK_RETUS_7.0_NPH25.200-22. Then I flashed TWRP 3.4.0-0. Afterwards, I flashed via TWRP the LineageOS 17.1 from this thread, along with GApps 10.0 micro (ARM64) and Magisk v20.4. Then I rebooted the device. Now the devices just stays on the Lineage loading stage. Please help.
Click to expand...
Click to collapse
I flashed latest twrp 3.4.0-0 then booted in twrp did a factory reset then I flashed lineage/ gapps nano/ wipe cache/ reboot system. No magisk. Maybe first reboot into system and then try install magisk?
moviefirst said:
I flashed latest twrp 3.4.0-0 then booted in twrp did a factory reset then I flashed lineage/ gapps nano/ wipe cache/ reboot system. No magisk. Maybe first reboot into system and then try install magisk?
Click to expand...
Click to collapse
Should System be mounted on TWRP?
B4oE said:
Should System be mounted on TWRP?
Click to expand...
Click to collapse
I didn't touch system.
B4oE said:
Should System be mounted on TWRP?
Click to expand...
Click to collapse
After factory reset, do I immediately reboot and let it begin and THEN go back to TWRP to flash? Or do I just factory reset and flash LineageOS immediately after?
B4oE said:
After factory reset, do I immediately reboot and let it begin and THEN go back to TWRP to flash? Or do I just factory reset and flash LineageOS immediately after?
Click to expand...
Click to collapse
Install twrp
Reboot into twrp
Factory reset
Flash lineage and gapps nano
Wipe cache
Reboot system, in twrp uncheck install twrp then do not install
Fabiett83 said:
Hi @chrmhoffmann
thank you for putting so much work in our old devices,
this weekend i upgraded TWRP to 3.4.0-0 and dirty flashed your UNOFFICIAL_20200625 build over the latest LineageOS 14.1 build for Nougat BL.
It's my son "wifi only" youtube/games device so i cannot test cellular data but everything else it's working.
Photos are 21MP, with correct rotation and camera works if called from apps (tested with hangouts and ghost observer)
The only strange thing is that, while audio is generally working, most games are completely silent.
I first had the impression that was the landscape rotation but happens even on portrait ones.
My son found that even while games are silent, ADS has sounds..
If you need something (logcat, ecc.) let me know, i can also try wiping data if you want.
Thank you,
Fabio
Click to expand...
Click to collapse
Hi,
Which game for example? I tried candy crush and that has sound
Chris
moviefirst said:
Install twrp
Reboot into twrp
Factory reset
Flash lineage and gapps nano
Wipe cache
Reboot system, in twrp uncheck install twrp then do not install
Click to expand...
Click to collapse
Bro... THANK YOU SO MUCH!! It finally worked.
So far, I noticed that the stock camera app is not auto focusing.
B4oE said:
Bro... THANK YOU SO MUCH!! It finally worked.
So far, I noticed that the stock camera app is not auto focusing.
Click to expand...
Click to collapse
Glad you have succeeded, auto focusing isn't working smooth all the time, maybe the dev will figure it out.
It now seems that I cannot flash via TWRP Magisk v20.4. When I do, TWRP freezes and forces a reboot into my device. Any ideas?
UPDATE: Now it seems that anything I do via TWRP is forcing it to freeze and reboot. I just wiped my cache only and it happened.
chrmhoffmann said:
Hi,
Which game for example? I tried candy crush and that has sound
Chris
Click to expand...
Click to collapse
With this games i have no sound/music:
Archero, Art of war: Legions, Bottle flip 3d, Burrito Bison: Launcher, Cell 13, Crazy Shopping, Hunter assassin, Kick the Buddy, Toca Life World, and others i had no time to test.
Strangely Candy Crush Saga and Ghost Observer has working audio..
I did a backup in twrp-3.4.0-0 but every time i tried to wipe data it rebooted without wiping, thinking that was caused by the F2FS filesystem (same thing happened to my daughter's Serranoltexx from LOS16 to LOS17.1) i changed the internal storage to ext4, reconfigured my son's account and tested the games again, still no audio!
So i restored the twrp backup but since it was a F2FS backup restored in a ext4 partition some games are damaged, i will fix it somehow..
This evening i will save a logcat and see if i can find something useful.
Thank you
Fabio
Edit: Since you are working with the kernel, can you limit CPU freq/cores based on temperature? the phone get really hot, more than in 14.1, and during tests yesterday i lost all battery in like 1 hour.
i don't know how thermald/core control works on clark, but i know that SD810/808 are overheating easily, so it's not an easy task.
i know i's a totally different cpu but was thinking about this commits from Serrano:
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275733
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275736
Fabiett83 said:
With this games i have no sound/music:
Archero, Art of war: Legions, Bottle flip 3d, Burrito Bison: Launcher, Cell 13, Crazy Shopping, Hunter assassin, Kick the Buddy, Toca Life World, and others i had no time to test.
Strangely Candy Crush Saga and Ghost Observer has working audio..
I did a backup in twrp-3.4.0-0 but every time i tried to wipe data it rebooted without wiping, thinking that was caused by the F2FS filesystem (same thing happened to my daughter's Serranoltexx from LOS16 to LOS17.1) i changed the internal storage to ext4, reconfigured my son's account and tested the games again, still no audio!
So i restored the twrp backup but since it was a F2FS backup restored in a ext4 partition some games are damaged, i will fix it somehow..
This evening i will save a logcat and see if i can find something useful.
Thank you
Fabio
Edit: Since you are working with the kernel, can you limit CPU freq/cores based on temperature? the phone get really hot, more than in 14.1, and during tests yesterday i lost all battery in like 1 hour.
i don't know how thermald/core control works on clark, but i know that SD810/808 are overheating easily, so it's not an easy task.
i know i's a totally different cpu but was thinking about this commits from Serrano:
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275733
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275736
Click to expand...
Click to collapse
Try the new build.
Audio: should be audible now - but is not 100% great yet (cracking noises).
Heat: Well, maybe this works better if thermanager starts now
I also added the Lineage Recovery download link. I hope this can be used instead by people who experience issues with flashing the ROM with TWRP.
chrmhoffmann said:
Try the new build.
Audio: should be audible now - but is not 100% great yet (cracking noises).
Heat: Well, maybe this works better if thermanager starts now
I also added the Lineage Recovery download link. I hope this can be used instead by people who experience issues with flashing the ROM with TWRP.
Click to expand...
Click to collapse
Thank you, as you said audio now works in all games tested, the cracking/stuttering is sometimes present but i'ts not game breaking.
I don't know how removing thermanager service definition could fix the thermanager service but looks like it's working better, too early to see battery life, but at least the temperature seems to be under control.
Since i wanted to keep the good twrp backups i have not tested the new Lineage Recovery.
Fabio
Hello, just a feedback about this rom. I never expected to get Lineageos 17.1 on our old Moto x style. Even the moto actions are built in, the camera functions properly. It would be great if this build became official. I would like to thank the dev very much for his work and dedication so that we can use our reliable moto x style for a long time to come.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using pico/nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Work
almost all
Known Issues
- camera
- screenshots
- missed icons in trebuchet tauncher (install nova or microsoft launcher and other)
Links
LineageOS Builds
1. 20200821: init build: https://drive.google.com/file/d/19-rPOcmlYIhcoZleG4MKRROk9TXytEOe/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from: https://twrp.me/samsung/samsunggalaxynotepro122exynoswifi.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to LineageOS team
Thanks to exynos5420 team for the right kernel
Thx @Valera1978 that's great news.
Gonna test today.
Edit 6h later first impressions:
Coming from Lineage 14.1 Vanilla with TWRP 3.4.0-0.
Backed up everything, full wipe plus data format.
Installing purely the ROM with TWRP 3.4.0 led to "Error 7" 3.3.1 did the trick.
Made a reboot to check if it starts.
Noticed screen failures in form of small black bars/stripes which vanished after a few seconds when I let the screen settle.
(Appearing very often even now after full installation of everything I need.)
Rebooted to TWRP and installed BiTGapps (prefer them to opengapps as they are even smaller than pico) and Magisk.
After each flash wiped cache/dalvik of course.
Installed Nova prime (dark mode) and all my other apps.
Camera doesn't work with Lineage App (as said) but does with opencamera from f-droid.
Screenshots neither but using Quickboot is a workaround when activated in its settings.
When writing text and correcting failures the magnifier shows only a white field with now text in it even when dark mode is off.
Great work @Valera1978 will carry on testing.
Edit 18h later:
Firefox seems to have problems with it, doesn't often even open its add-on page or urls.
Lightning browser has no probs.
Only one sudden reboot until now.
Edit 24h later:
Tried to upload a pic with the screen problems but didn't work.
Mostly occuring when switching from portrait to landscape (reproducible).
Because of the Firefox problems I've tried the 79 version but starting it resulted directly in a reboot (reproducible).
I'm surprised there aren't more responses
Can confirm TWRP 3.3.1 is the latest recovery to work. Doesn't seem to work with 3.1.1
Can't change wallpaper. Not sure why. I have to go to live wallpaper to get the default one back
Ok Google needs to be installed manually
I get security flags from SELinux and Public trust certificates. Probably because the release is so early
Overall it's not bad for a Pre-Alpha release.
First of all: an awesome thank you to Valera1978 since I was expecting a newer version than 14.1 a long time
Have the same issue with the wallpaper change and some flickering in the display. Installed nova prime too but can`t close all apps in task manager only each manually single (wipe up)
I am eager for the next version and improvements :fingers-crossed: and willing to give further feedback.
THX a lot for your passion
the current version is rather a technical build for testing (public, the most stable, there were already about 40-50 internal builds for fixing bugs and checking various things).
In any way - lineage 17.1 coming soon (later today), release build done, on tests right now. And I like it much more, then technical 16.0 build.
I tried 16 and I like it. Looking forward to 17.1. Thanks for saving the P900 from an early grave you are and have been the best ?
i will try this process for the first time. Is there a video tutorial? thank you.
kayamece said:
i will try this process for the first time. Is there a video tutorial? thank you.
Click to expand...
Click to collapse
This ROM will probably not be in development any further as the brilliant dev @Valera1978 is already working on a 17.1.
About a video I don't know. Searching in YouTube might help finding out
Here is a very good description which I followed from @thompatry who's ROM is very stable, has a working camera (skype) and gets regularly updated.
[ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi)
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.* (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com
Download it to SD.
As he quoted install a TWRP first to exchange the stock recovery.
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
bmwdroid said:
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
Click to expand...
Click to collapse
Hi everyone, I hope you are all safe and well.
Just a quick question, do I use the latest version of TWRP for my P900 (note pro 12.2 wi-fi). There are versions on the website which are later than the 3.3.1 version in this post. At the moment my version is 1.22, so this is really old! This was obviously installed and I did the flash to 14.1.
Like I say, at the moment, I am using LineageOS 14.1 with an old security patch level (September 19) because I cannot seem to update it. I have tried the auto update, this fails and I have also tried to manually apply but this also does not work.
I was wondering whether it was time to upgrade to version 16 or 17.
I'm not an expert on this by any means and I recall I did struggle with some error message when trying to update to I think at the time line Lineage 15.
Any comments or suggestions would be much appreciated.
@mattgod69 auto updater I don't use/like at all.
My suggestion is download TWRP 2.8.7-0 as zip and flash this with your TWRP. It is the latest zip released.
From that on it can use img files and you can update further to 3.3.1 or higher.
For me 3.4.0 was needed to flash @Valera1978 LOS17.1.
3.3.1-0 for LOS14.1 by @thompatry which's Vanilla (version 20201215) I use for here camera is working instead of being on LOS17.1.
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
mattgod69 said:
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
Click to expand...
Click to collapse
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
bmwdroid said:
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
Click to expand...
Click to collapse
Thank you for the detailed response, very helpful.
I dont really use the camera with my tablet, but i might, so its probably best to wait til 17.1 is working. The tablet is really just a browsing device i use beside my bed, its not an everyday machine.. so i am willing to try new things and play about with it.... it also does not matter if it is wiped accidentally etc.
i have to say it has been overall much better with 14.1 installed, far better than the stock OS. It is faster and more responsive.
Presumably I need new google apps etc download any new OS? If i install the latest LOS 14.1 do i also need new gapps etc? Is this OS much better than the one i have?
I do not know what Bitgapps and Magisk are?
Many thanks for all your help.... this community is great because even though i have done this a couple of times on different devices, there are long time gaps between doing it and it is still quite scary because i dont want to brick the device!
Just looked at Magisk... is it not a good idea to have this in any event? it looks like this would be earier to install later OS like LOS17.12? Is this right?
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
bmwdroid said:
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
Click to expand...
Click to collapse
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
mattgod69 said:
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
Click to expand...
Click to collapse
But I hope you will be updating the ROM to be on the latest patch level.
bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
ok, i will update with the lastest 14.1 OS.... is there a step by step guide for this on here....?
bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
i think i am going to try 17.1... i think most issues have been sorted now?
i did have some questions before i do this which i have put in another post.....
Also, how do you do a dirty install... is this where the cache etc is not wiped?
would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?
Many thanks for your help and advice.
mattgod69 said:
.... would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?...
Click to expand...
Click to collapse
Updating TWRP can be done with itself.
Working up- and downwards.
Just select "install" switch to "image" choose the file and select "recovery".
Afterwards reboot directly into the new recovery.